@tekyzinc/gsd-t 2.16.2 → 2.16.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +9 -1
- package/README.md +310 -310
- package/commands/{gsd.md → gsd-t.md} +6 -6
- package/docs/GSD-T-README.md +292 -292
- package/package.json +1 -1
- package/templates/CLAUDE-global.md +5 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,10 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to GSD-T are documented here. Updated with each release.
|
|
4
4
|
|
|
5
|
+
## [2.16.3] - 2026-02-16
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
- Pre-Commit Gate now requires timestamped progress.md entry (`YYYY-MM-DD HH:MM`) after every completed task, not just architectural decisions
|
|
9
|
+
|
|
10
|
+
### Fixed
|
|
11
|
+
- Reverted smart router rename (`/gsd` back to `/gsd-t`) — `/gsd` didn't match when typing `/gsd-t`
|
|
12
|
+
|
|
5
13
|
## [2.16.2] - 2026-02-16
|
|
6
14
|
|
|
7
15
|
### Changed
|
|
8
|
-
- Smart router renamed from `/user:gsd-t` to `/user:gsd`
|
|
16
|
+
- Smart router renamed from `/user:gsd-t` to `/user:gsd` (reverted in 2.16.3)
|
|
9
17
|
|
|
10
18
|
## [2.16.1] - 2026-02-16
|
|
11
19
|
|
package/README.md
CHANGED
|
@@ -1,310 +1,310 @@
|
|
|
1
|
-
# GSD-T: Contract-Driven Development for Claude Code
|
|
2
|
-
|
|
3
|
-
A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
|
|
4
|
-
|
|
5
|
-
**Solves context rot** — the quality degradation that happens as Claude fills its context window.
|
|
6
|
-
**Enables parallel execution** — contract-driven domains can be worked on simultaneously.
|
|
7
|
-
**Maintains test coverage** — automatically keeps tests aligned with code changes.
|
|
8
|
-
**Catches downstream effects** — analyzes impact before changes break things.
|
|
9
|
-
**Protects existing work** — destructive action guard prevents schema drops, architecture replacements, and data loss without explicit approval.
|
|
10
|
-
|
|
11
|
-
---
|
|
12
|
-
|
|
13
|
-
## Quick Start
|
|
14
|
-
|
|
15
|
-
### Install with npm
|
|
16
|
-
|
|
17
|
-
```bash
|
|
18
|
-
npx @tekyzinc/gsd-t install
|
|
19
|
-
```
|
|
20
|
-
|
|
21
|
-
This installs 37 GSD-T commands + 3 utility commands to `~/.claude/commands/` and the global CLAUDE.md to `~/.claude/CLAUDE.md`. Works on Windows, Mac, and Linux.
|
|
22
|
-
|
|
23
|
-
### Start Using It
|
|
24
|
-
|
|
25
|
-
```bash
|
|
26
|
-
# 1. Start Claude Code in your project
|
|
27
|
-
cd my-project
|
|
28
|
-
claude
|
|
29
|
-
|
|
30
|
-
# 2. Full onboarding (git + init + scan + setup in one)
|
|
31
|
-
/user:gsd-t-init-scan-setup
|
|
32
|
-
|
|
33
|
-
# Or step by step:
|
|
34
|
-
/user:gsd-t-init my-project
|
|
35
|
-
|
|
36
|
-
# 4. Define what you're building
|
|
37
|
-
/user:gsd-t-milestone "User Authentication System"
|
|
38
|
-
|
|
39
|
-
# 5. Let it rip (auto-advances through all phases)
|
|
40
|
-
/user:gsd-t-wave
|
|
41
|
-
|
|
42
|
-
# Or go phase by phase for more control:
|
|
43
|
-
/user:gsd-t-partition
|
|
44
|
-
/user:gsd-t-discuss
|
|
45
|
-
/user:gsd-t-plan
|
|
46
|
-
/user:gsd-t-impact
|
|
47
|
-
/user:gsd-t-execute
|
|
48
|
-
/user:gsd-t-test-sync
|
|
49
|
-
/user:gsd-t-integrate
|
|
50
|
-
/user:gsd-t-verify
|
|
51
|
-
/user:gsd-t-complete-milestone
|
|
52
|
-
```
|
|
53
|
-
|
|
54
|
-
### Resuming After a Break
|
|
55
|
-
|
|
56
|
-
```bash
|
|
57
|
-
claude
|
|
58
|
-
/user:gsd-t-resume
|
|
59
|
-
```
|
|
60
|
-
|
|
61
|
-
GSD-T reads all state files and tells you exactly where you left off.
|
|
62
|
-
|
|
63
|
-
---
|
|
64
|
-
|
|
65
|
-
## CLI Commands
|
|
66
|
-
|
|
67
|
-
```bash
|
|
68
|
-
npx @tekyzinc/gsd-t install # Install commands + global CLAUDE.md
|
|
69
|
-
npx @tekyzinc/gsd-t update # Update global commands + CLAUDE.md
|
|
70
|
-
npx @tekyzinc/gsd-t update-all # Update globally + all registered project CLAUDE.md files
|
|
71
|
-
npx @tekyzinc/gsd-t init [name] # Scaffold GSD-T project (auto-registers)
|
|
72
|
-
npx @tekyzinc/gsd-t register # Register current directory as a GSD-T project
|
|
73
|
-
npx @tekyzinc/gsd-t status # Check installation + version
|
|
74
|
-
npx @tekyzinc/gsd-t doctor # Diagnose common issues
|
|
75
|
-
npx @tekyzinc/gsd-t changelog # Open changelog in the browser
|
|
76
|
-
npx @tekyzinc/gsd-t uninstall # Remove commands (keeps project files)
|
|
77
|
-
```
|
|
78
|
-
|
|
79
|
-
### Updating
|
|
80
|
-
|
|
81
|
-
When a new version is published:
|
|
82
|
-
```bash
|
|
83
|
-
npx @tekyzinc/gsd-t@latest update
|
|
84
|
-
```
|
|
85
|
-
|
|
86
|
-
This will replace changed command files, back up your CLAUDE.md if customized, and track the installed version.
|
|
87
|
-
|
|
88
|
-
---
|
|
89
|
-
|
|
90
|
-
## Commands Reference
|
|
91
|
-
|
|
92
|
-
### Smart Router
|
|
93
|
-
|
|
94
|
-
| Command | Purpose | Auto |
|
|
95
|
-
|---------|---------|------|
|
|
96
|
-
| `/user:gsd {request}` | Describe what you need → auto-routes to the right command | Manual |
|
|
97
|
-
|
|
98
|
-
### Help & Onboarding
|
|
99
|
-
|
|
100
|
-
| Command | Purpose | Auto |
|
|
101
|
-
|---------|---------|------|
|
|
102
|
-
| `/user:gsd-t-help` | List all commands with descriptions | Manual |
|
|
103
|
-
| `/user:gsd-t-help {cmd}` | Detailed help for specific command | Manual |
|
|
104
|
-
| `/user:gsd-t-prompt` | Help formulate your idea before committing | Manual |
|
|
105
|
-
| `/user:gsd-t-brainstorm` | Creative exploration and idea generation | Manual |
|
|
106
|
-
|
|
107
|
-
### Project Initialization
|
|
108
|
-
|
|
109
|
-
| Command | Purpose | Auto |
|
|
110
|
-
|---------|---------|------|
|
|
111
|
-
| `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md | Manual |
|
|
112
|
-
| `/user:gsd-t-init` | Initialize GSD-T structure in project | Manual |
|
|
113
|
-
| `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one | Manual |
|
|
114
|
-
| `/user:gsd-t-project` | Full project → milestone roadmap | Manual |
|
|
115
|
-
| `/user:gsd-t-feature` | Major feature → impact analysis + milestones | Manual |
|
|
116
|
-
| `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md | Manual |
|
|
117
|
-
| `/user:gsd-t-gap-analysis` | Requirements gap analysis — spec vs. existing code | Manual |
|
|
118
|
-
| `/user:gsd-t-promote-debt` | Convert techdebt items to milestones | Manual |
|
|
119
|
-
| `/user:gsd-t-populate` | Auto-populate docs from existing codebase | Manual |
|
|
120
|
-
|
|
121
|
-
### Milestone Workflow
|
|
122
|
-
|
|
123
|
-
| Command | Purpose | Auto |
|
|
124
|
-
|---------|---------|------|
|
|
125
|
-
| `/user:gsd-t-milestone` | Define new milestone | Manual |
|
|
126
|
-
| `/user:gsd-t-partition` | Decompose into domains + contracts | In wave |
|
|
127
|
-
| `/user:gsd-t-discuss` | Multi-perspective design exploration | In wave |
|
|
128
|
-
| `/user:gsd-t-plan` | Create atomic task lists per domain | In wave |
|
|
129
|
-
| `/user:gsd-t-impact` | Analyze downstream effects | In wave |
|
|
130
|
-
| `/user:gsd-t-execute` | Run tasks (solo or team) | In wave |
|
|
131
|
-
| `/user:gsd-t-test-sync` | Sync tests with code changes | In wave |
|
|
132
|
-
| `/user:gsd-t-integrate` | Wire domains together | In wave |
|
|
133
|
-
| `/user:gsd-t-verify` | Run quality gates | In wave |
|
|
134
|
-
| `/user:gsd-t-complete-milestone` | Archive + git tag | In wave |
|
|
135
|
-
|
|
136
|
-
### Automation & Utilities
|
|
137
|
-
|
|
138
|
-
| Command | Purpose | Auto |
|
|
139
|
-
|---------|---------|------|
|
|
140
|
-
| `/user:gsd-t-wave` | Full cycle, auto-advances all phases | Manual |
|
|
141
|
-
| `/user:gsd-t-status` | Cross-domain progress view | Manual |
|
|
142
|
-
| `/user:gsd-t-resume` | Restore context, continue | Manual |
|
|
143
|
-
| `/user:gsd-t-quick` | Fast task with GSD-T guarantees | Manual |
|
|
144
|
-
| `/user:gsd-t-debug` | Systematic debugging with state | Manual |
|
|
145
|
-
| `/user:gsd-t-version-update` | Update GSD-T to latest version | Manual |
|
|
146
|
-
| `/user:gsd-t-version-update-all` | Update GSD-T + all registered projects | Manual |
|
|
147
|
-
|
|
148
|
-
### Backlog Management
|
|
149
|
-
|
|
150
|
-
| Command | Purpose | Auto |
|
|
151
|
-
|---------|---------|------|
|
|
152
|
-
| `/user:gsd-t-backlog-add` | Capture item, auto-categorize, append to backlog | Manual |
|
|
153
|
-
| `/user:gsd-t-backlog-list` | Filtered, ordered view of backlog items | Manual |
|
|
154
|
-
| `/user:gsd-t-backlog-move` | Reorder items by position (priority) | Manual |
|
|
155
|
-
| `/user:gsd-t-backlog-edit` | Modify backlog entry fields | Manual |
|
|
156
|
-
| `/user:gsd-t-backlog-remove` | Drop item with optional reason | Manual |
|
|
157
|
-
| `/user:gsd-t-backlog-promote` | Refine, classify, launch GSD-T workflow | Manual |
|
|
158
|
-
| `/user:gsd-t-backlog-settings` | Manage types, apps, categories, defaults | Manual |
|
|
159
|
-
|
|
160
|
-
### Git Helpers
|
|
161
|
-
|
|
162
|
-
| Command | Purpose | Auto |
|
|
163
|
-
|---------|---------|------|
|
|
164
|
-
| `/user:branch` | Create and switch to a new git branch | Manual |
|
|
165
|
-
| `/user:checkin` | Auto-bump version, stage, commit, and push | Manual |
|
|
166
|
-
| `/user:Claude-md` | Reload CLAUDE.md directives mid-session | Manual |
|
|
167
|
-
|
|
168
|
-
---
|
|
169
|
-
|
|
170
|
-
## Workflow Phases
|
|
171
|
-
|
|
172
|
-
| Phase | Purpose | Solo/Team |
|
|
173
|
-
|-------|---------|-----------|
|
|
174
|
-
| **Prompt** | Formulate idea (pre-workflow) | Solo |
|
|
175
|
-
| **Project/Feature/Scan** | Initialize work | Solo (team for large scans) |
|
|
176
|
-
| **Milestone** | Define deliverable | Solo |
|
|
177
|
-
| **Partition** | Decompose into domains + contracts | Solo |
|
|
178
|
-
| **Discuss** | Explore design decisions | Both |
|
|
179
|
-
| **Plan** | Create atomic task lists | Solo (always) |
|
|
180
|
-
| **Impact** | Downstream effect analysis | Solo |
|
|
181
|
-
| **Execute** | Build it | Both |
|
|
182
|
-
| **Test-Sync** | Maintain test coverage | Solo |
|
|
183
|
-
| **Integrate** | Wire domains together | Solo (always) |
|
|
184
|
-
| **Verify** | Quality gates | Both |
|
|
185
|
-
| **Complete** | Archive + tag | Solo |
|
|
186
|
-
|
|
187
|
-
---
|
|
188
|
-
|
|
189
|
-
## Entry Points
|
|
190
|
-
|
|
191
|
-
- **"I have an idea"** → `gsd-t-project` → milestone roadmap → partition → execute
|
|
192
|
-
- **"I have a codebase and need to add something"** → `gsd-t-feature` → impact analysis → milestones
|
|
193
|
-
- **"I have a codebase and need to understand/fix it"** → `gsd-t-scan` → techdebt.md → promote to milestones
|
|
194
|
-
|
|
195
|
-
---
|
|
196
|
-
|
|
197
|
-
## Project Structure (What GSD-T Creates)
|
|
198
|
-
|
|
199
|
-
```
|
|
200
|
-
your-project/
|
|
201
|
-
├── CLAUDE.md
|
|
202
|
-
├── docs/
|
|
203
|
-
│ ├── requirements.md # Functional + technical requirements
|
|
204
|
-
│ ├── architecture.md # System design, components, data flow
|
|
205
|
-
│ ├── workflows.md # User journeys, technical processes
|
|
206
|
-
│ └── infrastructure.md # Dev setup, DB, cloud, deployment
|
|
207
|
-
├── .gsd-t/
|
|
208
|
-
│ ├── progress.md # Master state file
|
|
209
|
-
│ ├── backlog.md # Captured backlog items (priority ordered)
|
|
210
|
-
│ ├── backlog-settings.md # Types, apps, categories, defaults
|
|
211
|
-
│ ├── roadmap.md # Milestone roadmap
|
|
212
|
-
│ ├── techdebt.md # Technical debt register
|
|
213
|
-
│ ├── verify-report.md # Latest verification results
|
|
214
|
-
│ ├── impact-report.md # Downstream effect analysis
|
|
215
|
-
│ ├── test-coverage.md # Test sync report
|
|
216
|
-
│ ├── contracts/
|
|
217
|
-
│ │ ├── api-contract.md
|
|
218
|
-
│ │ ├── schema-contract.md
|
|
219
|
-
│ │ ├── component-contract.md
|
|
220
|
-
│ │ └── integration-points.md
|
|
221
|
-
│ ├── domains/
|
|
222
|
-
│ │ └── {domain-name}/
|
|
223
|
-
│ │ ├── scope.md
|
|
224
|
-
│ │ ├── tasks.md
|
|
225
|
-
│ │ └── constraints.md
|
|
226
|
-
│ ├── milestones/ # Archived completed milestones
|
|
227
|
-
│ │ └── {milestone-name}-{date}/
|
|
228
|
-
│ └── scan/ # Codebase analysis outputs
|
|
229
|
-
└── src/
|
|
230
|
-
```
|
|
231
|
-
|
|
232
|
-
---
|
|
233
|
-
|
|
234
|
-
## Key Principles
|
|
235
|
-
|
|
236
|
-
1. **Contracts are the source of truth.** Code implements contracts, not the other way around.
|
|
237
|
-
2. **Domains own files exclusively.** No two domains should modify the same file.
|
|
238
|
-
3. **Impact before execution.** Always analyze downstream effects before making changes.
|
|
239
|
-
4. **Tests stay synced.** Every code change triggers test analysis.
|
|
240
|
-
5. **State survives sessions.** Everything is in `.gsd-t/`.
|
|
241
|
-
6. **Plan is single-brain, execute is multi-brain.** Planning and integration always solo; execution and verification can parallelize.
|
|
242
|
-
7. **Every decision is logged.** The Decision Log captures why, not just what.
|
|
243
|
-
|
|
244
|
-
---
|
|
245
|
-
|
|
246
|
-
## Enabling Agent Teams
|
|
247
|
-
|
|
248
|
-
```json
|
|
249
|
-
{
|
|
250
|
-
"env": {
|
|
251
|
-
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
|
|
252
|
-
}
|
|
253
|
-
}
|
|
254
|
-
```
|
|
255
|
-
|
|
256
|
-
Teams are optional — all commands work in solo mode.
|
|
257
|
-
|
|
258
|
-
---
|
|
259
|
-
|
|
260
|
-
## Manual Installation (without npm)
|
|
261
|
-
|
|
262
|
-
```bash
|
|
263
|
-
# Windows
|
|
264
|
-
copy commands\*.md %USERPROFILE%\.claude\commands\
|
|
265
|
-
|
|
266
|
-
# Mac/Linux
|
|
267
|
-
cp commands/*.md ~/.claude/commands/
|
|
268
|
-
```
|
|
269
|
-
|
|
270
|
-
Verify with: `/user:gsd-t-help`
|
|
271
|
-
|
|
272
|
-
---
|
|
273
|
-
|
|
274
|
-
## Repo Contents
|
|
275
|
-
|
|
276
|
-
```
|
|
277
|
-
get-stuff-done-teams/
|
|
278
|
-
├── README.md
|
|
279
|
-
├── package.json
|
|
280
|
-
├── LICENSE
|
|
281
|
-
├── bin/
|
|
282
|
-
│ └── gsd-t.js # CLI installer
|
|
283
|
-
├── commands/ # 40 slash commands
|
|
284
|
-
│ ├── gsd-t-*.md # 37 GSD-T workflow commands
|
|
285
|
-
│ ├── branch.md # Git branch helper
|
|
286
|
-
│ ├── checkin.md # Auto-version + commit/push helper
|
|
287
|
-
│ └── Claude-md.md # Reload CLAUDE.md directives
|
|
288
|
-
├── templates/ # Document templates
|
|
289
|
-
│ ├── CLAUDE-global.md
|
|
290
|
-
│ ├── CLAUDE-project.md
|
|
291
|
-
│ ├── requirements.md
|
|
292
|
-
│ ├── architecture.md
|
|
293
|
-
│ ├── workflows.md
|
|
294
|
-
│ ├── infrastructure.md
|
|
295
|
-
│ ├── progress.md
|
|
296
|
-
│ ├── backlog.md
|
|
297
|
-
│ └── backlog-settings.md
|
|
298
|
-
├── examples/
|
|
299
|
-
│ ├── settings.json
|
|
300
|
-
│ └── .gsd-t/
|
|
301
|
-
├── docs/
|
|
302
|
-
│ ├── GSD-T-README.md # Detailed methodology + usage guide
|
|
303
|
-
│ └── methodology.md
|
|
304
|
-
```
|
|
305
|
-
|
|
306
|
-
---
|
|
307
|
-
|
|
308
|
-
## License
|
|
309
|
-
|
|
310
|
-
MIT
|
|
1
|
+
# GSD-T: Contract-Driven Development for Claude Code
|
|
2
|
+
|
|
3
|
+
A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
|
|
4
|
+
|
|
5
|
+
**Solves context rot** — the quality degradation that happens as Claude fills its context window.
|
|
6
|
+
**Enables parallel execution** — contract-driven domains can be worked on simultaneously.
|
|
7
|
+
**Maintains test coverage** — automatically keeps tests aligned with code changes.
|
|
8
|
+
**Catches downstream effects** — analyzes impact before changes break things.
|
|
9
|
+
**Protects existing work** — destructive action guard prevents schema drops, architecture replacements, and data loss without explicit approval.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Quick Start
|
|
14
|
+
|
|
15
|
+
### Install with npm
|
|
16
|
+
|
|
17
|
+
```bash
|
|
18
|
+
npx @tekyzinc/gsd-t install
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
This installs 37 GSD-T commands + 3 utility commands to `~/.claude/commands/` and the global CLAUDE.md to `~/.claude/CLAUDE.md`. Works on Windows, Mac, and Linux.
|
|
22
|
+
|
|
23
|
+
### Start Using It
|
|
24
|
+
|
|
25
|
+
```bash
|
|
26
|
+
# 1. Start Claude Code in your project
|
|
27
|
+
cd my-project
|
|
28
|
+
claude
|
|
29
|
+
|
|
30
|
+
# 2. Full onboarding (git + init + scan + setup in one)
|
|
31
|
+
/user:gsd-t-init-scan-setup
|
|
32
|
+
|
|
33
|
+
# Or step by step:
|
|
34
|
+
/user:gsd-t-init my-project
|
|
35
|
+
|
|
36
|
+
# 4. Define what you're building
|
|
37
|
+
/user:gsd-t-milestone "User Authentication System"
|
|
38
|
+
|
|
39
|
+
# 5. Let it rip (auto-advances through all phases)
|
|
40
|
+
/user:gsd-t-wave
|
|
41
|
+
|
|
42
|
+
# Or go phase by phase for more control:
|
|
43
|
+
/user:gsd-t-partition
|
|
44
|
+
/user:gsd-t-discuss
|
|
45
|
+
/user:gsd-t-plan
|
|
46
|
+
/user:gsd-t-impact
|
|
47
|
+
/user:gsd-t-execute
|
|
48
|
+
/user:gsd-t-test-sync
|
|
49
|
+
/user:gsd-t-integrate
|
|
50
|
+
/user:gsd-t-verify
|
|
51
|
+
/user:gsd-t-complete-milestone
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
### Resuming After a Break
|
|
55
|
+
|
|
56
|
+
```bash
|
|
57
|
+
claude
|
|
58
|
+
/user:gsd-t-resume
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
GSD-T reads all state files and tells you exactly where you left off.
|
|
62
|
+
|
|
63
|
+
---
|
|
64
|
+
|
|
65
|
+
## CLI Commands
|
|
66
|
+
|
|
67
|
+
```bash
|
|
68
|
+
npx @tekyzinc/gsd-t install # Install commands + global CLAUDE.md
|
|
69
|
+
npx @tekyzinc/gsd-t update # Update global commands + CLAUDE.md
|
|
70
|
+
npx @tekyzinc/gsd-t update-all # Update globally + all registered project CLAUDE.md files
|
|
71
|
+
npx @tekyzinc/gsd-t init [name] # Scaffold GSD-T project (auto-registers)
|
|
72
|
+
npx @tekyzinc/gsd-t register # Register current directory as a GSD-T project
|
|
73
|
+
npx @tekyzinc/gsd-t status # Check installation + version
|
|
74
|
+
npx @tekyzinc/gsd-t doctor # Diagnose common issues
|
|
75
|
+
npx @tekyzinc/gsd-t changelog # Open changelog in the browser
|
|
76
|
+
npx @tekyzinc/gsd-t uninstall # Remove commands (keeps project files)
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### Updating
|
|
80
|
+
|
|
81
|
+
When a new version is published:
|
|
82
|
+
```bash
|
|
83
|
+
npx @tekyzinc/gsd-t@latest update
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
This will replace changed command files, back up your CLAUDE.md if customized, and track the installed version.
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
## Commands Reference
|
|
91
|
+
|
|
92
|
+
### Smart Router
|
|
93
|
+
|
|
94
|
+
| Command | Purpose | Auto |
|
|
95
|
+
|---------|---------|------|
|
|
96
|
+
| `/user:gsd {request}` | Describe what you need → auto-routes to the right command | Manual |
|
|
97
|
+
|
|
98
|
+
### Help & Onboarding
|
|
99
|
+
|
|
100
|
+
| Command | Purpose | Auto |
|
|
101
|
+
|---------|---------|------|
|
|
102
|
+
| `/user:gsd-t-help` | List all commands with descriptions | Manual |
|
|
103
|
+
| `/user:gsd-t-help {cmd}` | Detailed help for specific command | Manual |
|
|
104
|
+
| `/user:gsd-t-prompt` | Help formulate your idea before committing | Manual |
|
|
105
|
+
| `/user:gsd-t-brainstorm` | Creative exploration and idea generation | Manual |
|
|
106
|
+
|
|
107
|
+
### Project Initialization
|
|
108
|
+
|
|
109
|
+
| Command | Purpose | Auto |
|
|
110
|
+
|---------|---------|------|
|
|
111
|
+
| `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md | Manual |
|
|
112
|
+
| `/user:gsd-t-init` | Initialize GSD-T structure in project | Manual |
|
|
113
|
+
| `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one | Manual |
|
|
114
|
+
| `/user:gsd-t-project` | Full project → milestone roadmap | Manual |
|
|
115
|
+
| `/user:gsd-t-feature` | Major feature → impact analysis + milestones | Manual |
|
|
116
|
+
| `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md | Manual |
|
|
117
|
+
| `/user:gsd-t-gap-analysis` | Requirements gap analysis — spec vs. existing code | Manual |
|
|
118
|
+
| `/user:gsd-t-promote-debt` | Convert techdebt items to milestones | Manual |
|
|
119
|
+
| `/user:gsd-t-populate` | Auto-populate docs from existing codebase | Manual |
|
|
120
|
+
|
|
121
|
+
### Milestone Workflow
|
|
122
|
+
|
|
123
|
+
| Command | Purpose | Auto |
|
|
124
|
+
|---------|---------|------|
|
|
125
|
+
| `/user:gsd-t-milestone` | Define new milestone | Manual |
|
|
126
|
+
| `/user:gsd-t-partition` | Decompose into domains + contracts | In wave |
|
|
127
|
+
| `/user:gsd-t-discuss` | Multi-perspective design exploration | In wave |
|
|
128
|
+
| `/user:gsd-t-plan` | Create atomic task lists per domain | In wave |
|
|
129
|
+
| `/user:gsd-t-impact` | Analyze downstream effects | In wave |
|
|
130
|
+
| `/user:gsd-t-execute` | Run tasks (solo or team) | In wave |
|
|
131
|
+
| `/user:gsd-t-test-sync` | Sync tests with code changes | In wave |
|
|
132
|
+
| `/user:gsd-t-integrate` | Wire domains together | In wave |
|
|
133
|
+
| `/user:gsd-t-verify` | Run quality gates | In wave |
|
|
134
|
+
| `/user:gsd-t-complete-milestone` | Archive + git tag | In wave |
|
|
135
|
+
|
|
136
|
+
### Automation & Utilities
|
|
137
|
+
|
|
138
|
+
| Command | Purpose | Auto |
|
|
139
|
+
|---------|---------|------|
|
|
140
|
+
| `/user:gsd-t-wave` | Full cycle, auto-advances all phases | Manual |
|
|
141
|
+
| `/user:gsd-t-status` | Cross-domain progress view | Manual |
|
|
142
|
+
| `/user:gsd-t-resume` | Restore context, continue | Manual |
|
|
143
|
+
| `/user:gsd-t-quick` | Fast task with GSD-T guarantees | Manual |
|
|
144
|
+
| `/user:gsd-t-debug` | Systematic debugging with state | Manual |
|
|
145
|
+
| `/user:gsd-t-version-update` | Update GSD-T to latest version | Manual |
|
|
146
|
+
| `/user:gsd-t-version-update-all` | Update GSD-T + all registered projects | Manual |
|
|
147
|
+
|
|
148
|
+
### Backlog Management
|
|
149
|
+
|
|
150
|
+
| Command | Purpose | Auto |
|
|
151
|
+
|---------|---------|------|
|
|
152
|
+
| `/user:gsd-t-backlog-add` | Capture item, auto-categorize, append to backlog | Manual |
|
|
153
|
+
| `/user:gsd-t-backlog-list` | Filtered, ordered view of backlog items | Manual |
|
|
154
|
+
| `/user:gsd-t-backlog-move` | Reorder items by position (priority) | Manual |
|
|
155
|
+
| `/user:gsd-t-backlog-edit` | Modify backlog entry fields | Manual |
|
|
156
|
+
| `/user:gsd-t-backlog-remove` | Drop item with optional reason | Manual |
|
|
157
|
+
| `/user:gsd-t-backlog-promote` | Refine, classify, launch GSD-T workflow | Manual |
|
|
158
|
+
| `/user:gsd-t-backlog-settings` | Manage types, apps, categories, defaults | Manual |
|
|
159
|
+
|
|
160
|
+
### Git Helpers
|
|
161
|
+
|
|
162
|
+
| Command | Purpose | Auto |
|
|
163
|
+
|---------|---------|------|
|
|
164
|
+
| `/user:branch` | Create and switch to a new git branch | Manual |
|
|
165
|
+
| `/user:checkin` | Auto-bump version, stage, commit, and push | Manual |
|
|
166
|
+
| `/user:Claude-md` | Reload CLAUDE.md directives mid-session | Manual |
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
170
|
+
## Workflow Phases
|
|
171
|
+
|
|
172
|
+
| Phase | Purpose | Solo/Team |
|
|
173
|
+
|-------|---------|-----------|
|
|
174
|
+
| **Prompt** | Formulate idea (pre-workflow) | Solo |
|
|
175
|
+
| **Project/Feature/Scan** | Initialize work | Solo (team for large scans) |
|
|
176
|
+
| **Milestone** | Define deliverable | Solo |
|
|
177
|
+
| **Partition** | Decompose into domains + contracts | Solo |
|
|
178
|
+
| **Discuss** | Explore design decisions | Both |
|
|
179
|
+
| **Plan** | Create atomic task lists | Solo (always) |
|
|
180
|
+
| **Impact** | Downstream effect analysis | Solo |
|
|
181
|
+
| **Execute** | Build it | Both |
|
|
182
|
+
| **Test-Sync** | Maintain test coverage | Solo |
|
|
183
|
+
| **Integrate** | Wire domains together | Solo (always) |
|
|
184
|
+
| **Verify** | Quality gates | Both |
|
|
185
|
+
| **Complete** | Archive + tag | Solo |
|
|
186
|
+
|
|
187
|
+
---
|
|
188
|
+
|
|
189
|
+
## Entry Points
|
|
190
|
+
|
|
191
|
+
- **"I have an idea"** → `gsd-t-project` → milestone roadmap → partition → execute
|
|
192
|
+
- **"I have a codebase and need to add something"** → `gsd-t-feature` → impact analysis → milestones
|
|
193
|
+
- **"I have a codebase and need to understand/fix it"** → `gsd-t-scan` → techdebt.md → promote to milestones
|
|
194
|
+
|
|
195
|
+
---
|
|
196
|
+
|
|
197
|
+
## Project Structure (What GSD-T Creates)
|
|
198
|
+
|
|
199
|
+
```
|
|
200
|
+
your-project/
|
|
201
|
+
├── CLAUDE.md
|
|
202
|
+
├── docs/
|
|
203
|
+
│ ├── requirements.md # Functional + technical requirements
|
|
204
|
+
│ ├── architecture.md # System design, components, data flow
|
|
205
|
+
│ ├── workflows.md # User journeys, technical processes
|
|
206
|
+
│ └── infrastructure.md # Dev setup, DB, cloud, deployment
|
|
207
|
+
├── .gsd-t/
|
|
208
|
+
│ ├── progress.md # Master state file
|
|
209
|
+
│ ├── backlog.md # Captured backlog items (priority ordered)
|
|
210
|
+
│ ├── backlog-settings.md # Types, apps, categories, defaults
|
|
211
|
+
│ ├── roadmap.md # Milestone roadmap
|
|
212
|
+
│ ├── techdebt.md # Technical debt register
|
|
213
|
+
│ ├── verify-report.md # Latest verification results
|
|
214
|
+
│ ├── impact-report.md # Downstream effect analysis
|
|
215
|
+
│ ├── test-coverage.md # Test sync report
|
|
216
|
+
│ ├── contracts/
|
|
217
|
+
│ │ ├── api-contract.md
|
|
218
|
+
│ │ ├── schema-contract.md
|
|
219
|
+
│ │ ├── component-contract.md
|
|
220
|
+
│ │ └── integration-points.md
|
|
221
|
+
│ ├── domains/
|
|
222
|
+
│ │ └── {domain-name}/
|
|
223
|
+
│ │ ├── scope.md
|
|
224
|
+
│ │ ├── tasks.md
|
|
225
|
+
│ │ └── constraints.md
|
|
226
|
+
│ ├── milestones/ # Archived completed milestones
|
|
227
|
+
│ │ └── {milestone-name}-{date}/
|
|
228
|
+
│ └── scan/ # Codebase analysis outputs
|
|
229
|
+
└── src/
|
|
230
|
+
```
|
|
231
|
+
|
|
232
|
+
---
|
|
233
|
+
|
|
234
|
+
## Key Principles
|
|
235
|
+
|
|
236
|
+
1. **Contracts are the source of truth.** Code implements contracts, not the other way around.
|
|
237
|
+
2. **Domains own files exclusively.** No two domains should modify the same file.
|
|
238
|
+
3. **Impact before execution.** Always analyze downstream effects before making changes.
|
|
239
|
+
4. **Tests stay synced.** Every code change triggers test analysis.
|
|
240
|
+
5. **State survives sessions.** Everything is in `.gsd-t/`.
|
|
241
|
+
6. **Plan is single-brain, execute is multi-brain.** Planning and integration always solo; execution and verification can parallelize.
|
|
242
|
+
7. **Every decision is logged.** The Decision Log captures why, not just what.
|
|
243
|
+
|
|
244
|
+
---
|
|
245
|
+
|
|
246
|
+
## Enabling Agent Teams
|
|
247
|
+
|
|
248
|
+
```json
|
|
249
|
+
{
|
|
250
|
+
"env": {
|
|
251
|
+
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
|
|
252
|
+
}
|
|
253
|
+
}
|
|
254
|
+
```
|
|
255
|
+
|
|
256
|
+
Teams are optional — all commands work in solo mode.
|
|
257
|
+
|
|
258
|
+
---
|
|
259
|
+
|
|
260
|
+
## Manual Installation (without npm)
|
|
261
|
+
|
|
262
|
+
```bash
|
|
263
|
+
# Windows
|
|
264
|
+
copy commands\*.md %USERPROFILE%\.claude\commands\
|
|
265
|
+
|
|
266
|
+
# Mac/Linux
|
|
267
|
+
cp commands/*.md ~/.claude/commands/
|
|
268
|
+
```
|
|
269
|
+
|
|
270
|
+
Verify with: `/user:gsd-t-help`
|
|
271
|
+
|
|
272
|
+
---
|
|
273
|
+
|
|
274
|
+
## Repo Contents
|
|
275
|
+
|
|
276
|
+
```
|
|
277
|
+
get-stuff-done-teams/
|
|
278
|
+
├── README.md
|
|
279
|
+
├── package.json
|
|
280
|
+
├── LICENSE
|
|
281
|
+
├── bin/
|
|
282
|
+
│ └── gsd-t.js # CLI installer
|
|
283
|
+
├── commands/ # 40 slash commands
|
|
284
|
+
│ ├── gsd-t-*.md # 37 GSD-T workflow commands
|
|
285
|
+
│ ├── branch.md # Git branch helper
|
|
286
|
+
│ ├── checkin.md # Auto-version + commit/push helper
|
|
287
|
+
│ └── Claude-md.md # Reload CLAUDE.md directives
|
|
288
|
+
├── templates/ # Document templates
|
|
289
|
+
│ ├── CLAUDE-global.md
|
|
290
|
+
│ ├── CLAUDE-project.md
|
|
291
|
+
│ ├── requirements.md
|
|
292
|
+
│ ├── architecture.md
|
|
293
|
+
│ ├── workflows.md
|
|
294
|
+
│ ├── infrastructure.md
|
|
295
|
+
│ ├── progress.md
|
|
296
|
+
│ ├── backlog.md
|
|
297
|
+
│ └── backlog-settings.md
|
|
298
|
+
├── examples/
|
|
299
|
+
│ ├── settings.json
|
|
300
|
+
│ └── .gsd-t/
|
|
301
|
+
├── docs/
|
|
302
|
+
│ ├── GSD-T-README.md # Detailed methodology + usage guide
|
|
303
|
+
│ └── methodology.md
|
|
304
|
+
```
|
|
305
|
+
|
|
306
|
+
---
|
|
307
|
+
|
|
308
|
+
## License
|
|
309
|
+
|
|
310
|
+
MIT
|
|
@@ -58,14 +58,14 @@ This MUST be the very first line of your response so the user sees which command
|
|
|
58
58
|
If called with no arguments, show:
|
|
59
59
|
|
|
60
60
|
```
|
|
61
|
-
Usage: /user:gsd {describe what you want}
|
|
61
|
+
Usage: /user:gsd-t {describe what you want}
|
|
62
62
|
|
|
63
63
|
Examples:
|
|
64
|
-
/user:gsd Fix the login timeout bug
|
|
65
|
-
/user:gsd Add dark mode support
|
|
66
|
-
/user:gsd Scan the codebase for tech debt
|
|
67
|
-
/user:gsd What's the current progress?
|
|
68
|
-
/user:gsd Compare this spec against our code
|
|
64
|
+
/user:gsd-t Fix the login timeout bug
|
|
65
|
+
/user:gsd-t Add dark mode support
|
|
66
|
+
/user:gsd-t Scan the codebase for tech debt
|
|
67
|
+
/user:gsd-t What's the current progress?
|
|
68
|
+
/user:gsd-t Compare this spec against our code
|
|
69
69
|
|
|
70
70
|
I'll route to the right GSD-T command automatically.
|
|
71
71
|
```
|
package/docs/GSD-T-README.md
CHANGED
|
@@ -1,292 +1,292 @@
|
|
|
1
|
-
# GSD-T: Contract-Driven Development for Claude Code
|
|
2
|
-
|
|
3
|
-
A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
|
|
4
|
-
|
|
5
|
-
## What It Does
|
|
6
|
-
|
|
7
|
-
**Solves context rot** — the quality degradation that happens as Claude fills its context window.
|
|
8
|
-
|
|
9
|
-
**Enables parallel execution** — contract-driven domains can be worked on simultaneously.
|
|
10
|
-
|
|
11
|
-
**Maintains test coverage** — automatically keeps tests aligned with code changes.
|
|
12
|
-
|
|
13
|
-
**Catches downstream effects** — analyzes impact before changes break things.
|
|
14
|
-
|
|
15
|
-
---
|
|
16
|
-
|
|
17
|
-
## Quick Start
|
|
18
|
-
|
|
19
|
-
```bash
|
|
20
|
-
# 1. Start Claude Code in your project
|
|
21
|
-
cd my-project
|
|
22
|
-
claude
|
|
23
|
-
|
|
24
|
-
# 2. Full onboarding (git + init + scan + setup in one)
|
|
25
|
-
/user:gsd-t-init-scan-setup
|
|
26
|
-
|
|
27
|
-
# Or step by step:
|
|
28
|
-
/user:gsd-t-init my-project
|
|
29
|
-
|
|
30
|
-
# 3. Define what you're building
|
|
31
|
-
/user:gsd-t-milestone "User Authentication System"
|
|
32
|
-
|
|
33
|
-
# 5. Let it rip (auto-advances through all phases)
|
|
34
|
-
/user:gsd-t-wave
|
|
35
|
-
|
|
36
|
-
# Or go phase by phase for more control:
|
|
37
|
-
/user:gsd-t-partition
|
|
38
|
-
/user:gsd-t-discuss
|
|
39
|
-
/user:gsd-t-plan
|
|
40
|
-
/user:gsd-t-impact
|
|
41
|
-
/user:gsd-t-execute
|
|
42
|
-
/user:gsd-t-test-sync
|
|
43
|
-
/user:gsd-t-integrate
|
|
44
|
-
/user:gsd-t-verify
|
|
45
|
-
/user:gsd-t-complete-milestone
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
## Resuming After a Break
|
|
49
|
-
|
|
50
|
-
```bash
|
|
51
|
-
claude
|
|
52
|
-
/user:gsd-t-resume
|
|
53
|
-
```
|
|
54
|
-
|
|
55
|
-
GSD-T reads all state files and tells you exactly where you left off.
|
|
56
|
-
|
|
57
|
-
---
|
|
58
|
-
|
|
59
|
-
## Commands Reference
|
|
60
|
-
|
|
61
|
-
### Smart Router
|
|
62
|
-
|
|
63
|
-
| Command | Purpose | Auto |
|
|
64
|
-
|---------|---------|------|
|
|
65
|
-
| `/user:gsd {request}` | Describe what you need → auto-routes to the right command | Manual |
|
|
66
|
-
|
|
67
|
-
### Help & Onboarding
|
|
68
|
-
|
|
69
|
-
| Command | Purpose | Auto |
|
|
70
|
-
|---------|---------|------|
|
|
71
|
-
| `/user:gsd-t-help` | List all commands with descriptions | Manual |
|
|
72
|
-
| `/user:gsd-t-help {cmd}` | Detailed help for specific command | Manual |
|
|
73
|
-
| `/user:gsd-t-prompt` | Help formulate your idea before committing | Manual |
|
|
74
|
-
| `/user:gsd-t-brainstorm` | Creative exploration and idea generation | Manual |
|
|
75
|
-
|
|
76
|
-
### Project Initialization
|
|
77
|
-
|
|
78
|
-
| Command | Purpose | Auto |
|
|
79
|
-
|---------|---------|------|
|
|
80
|
-
| `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md | Manual |
|
|
81
|
-
| `/user:gsd-t-init` | Initialize GSD-T structure in project | Manual |
|
|
82
|
-
| `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one | Manual |
|
|
83
|
-
| `/user:gsd-t-project` | Full project → milestone roadmap | Manual |
|
|
84
|
-
| `/user:gsd-t-feature` | Major feature → impact analysis + milestones | Manual |
|
|
85
|
-
| `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md | Manual |
|
|
86
|
-
| `/user:gsd-t-gap-analysis` | Requirements gap analysis — spec vs. existing code | Manual |
|
|
87
|
-
| `/user:gsd-t-promote-debt` | Convert techdebt items to milestones | Manual |
|
|
88
|
-
| `/user:gsd-t-populate` | Auto-populate docs from existing codebase | Manual |
|
|
89
|
-
|
|
90
|
-
### Milestone Workflow
|
|
91
|
-
|
|
92
|
-
| Command | Purpose | Auto |
|
|
93
|
-
|---------|---------|------|
|
|
94
|
-
| `/user:gsd-t-milestone` | Define new milestone | Manual |
|
|
95
|
-
| `/user:gsd-t-partition` | Decompose into domains + contracts | In wave |
|
|
96
|
-
| `/user:gsd-t-discuss` | Multi-perspective design exploration | In wave |
|
|
97
|
-
| `/user:gsd-t-plan` | Create atomic task lists per domain | In wave |
|
|
98
|
-
| `/user:gsd-t-impact` | Analyze downstream effects | In wave |
|
|
99
|
-
| `/user:gsd-t-execute` | Run tasks (solo or team) | In wave |
|
|
100
|
-
| `/user:gsd-t-test-sync` | Sync tests with code changes | In wave |
|
|
101
|
-
| `/user:gsd-t-integrate` | Wire domains together | In wave |
|
|
102
|
-
| `/user:gsd-t-verify` | Run quality gates | In wave |
|
|
103
|
-
| `/user:gsd-t-complete-milestone` | Archive + git tag | In wave |
|
|
104
|
-
|
|
105
|
-
### Automation & Utilities
|
|
106
|
-
|
|
107
|
-
| Command | Purpose | Auto |
|
|
108
|
-
|---------|---------|------|
|
|
109
|
-
| `/user:gsd-t-wave` | Full cycle, auto-advances all phases | Manual |
|
|
110
|
-
| `/user:gsd-t-status` | Cross-domain progress view | Manual |
|
|
111
|
-
| `/user:gsd-t-resume` | Restore context, continue | Manual |
|
|
112
|
-
| `/user:gsd-t-quick` | Fast task with GSD-T guarantees | Manual |
|
|
113
|
-
| `/user:gsd-t-debug` | Systematic debugging with state | Manual |
|
|
114
|
-
| `/user:gsd-t-version-update` | Update GSD-T to latest version | Manual |
|
|
115
|
-
| `/user:gsd-t-version-update-all` | Update GSD-T + all registered projects | Manual |
|
|
116
|
-
|
|
117
|
-
---
|
|
118
|
-
|
|
119
|
-
## Workflow Phases
|
|
120
|
-
|
|
121
|
-
```
|
|
122
|
-
┌─────────────────────────────────────────────────────────────────────────────┐
|
|
123
|
-
│ GSD-T Wave Flow │
|
|
124
|
-
├─────────────────────────────────────────────────────────────────────────────┤
|
|
125
|
-
│ │
|
|
126
|
-
│ milestone → partition → discuss → plan → impact → execute → test-sync │
|
|
127
|
-
│ │ │ │
|
|
128
|
-
│ │ └──────┐ │
|
|
129
|
-
│ │ ▼ │
|
|
130
|
-
│ │ ┌───────────────────┐ │
|
|
131
|
-
│ │ │ (runs after each │ │
|
|
132
|
-
│ │ │ task + at verify)│ │
|
|
133
|
-
│ │ └───────────────────┘ │
|
|
134
|
-
│ ▼ │
|
|
135
|
-
│ complete-milestone ◄── verify ◄── integrate ◄──────────────────────┘ │
|
|
136
|
-
│ │
|
|
137
|
-
└─────────────────────────────────────────────────────────────────────────────┘
|
|
138
|
-
```
|
|
139
|
-
|
|
140
|
-
| Phase | Purpose | Solo/Team |
|
|
141
|
-
|-------|---------|-----------|
|
|
142
|
-
| **Prompt** | Formulate idea (pre-workflow) | Solo |
|
|
143
|
-
| **Project/Feature/Scan** | Initialize work | Solo (team for large scans) |
|
|
144
|
-
| **Milestone** | Define deliverable | Solo |
|
|
145
|
-
| **Partition** | Decompose into domains + contracts | Solo |
|
|
146
|
-
| **Discuss** | Explore design decisions | Both |
|
|
147
|
-
| **Plan** | Create atomic task lists | Solo (always) |
|
|
148
|
-
| **Impact** | Downstream effect analysis | Solo |
|
|
149
|
-
| **Execute** | Build it | Both |
|
|
150
|
-
| **Test-Sync** | Maintain test coverage | Solo |
|
|
151
|
-
| **Integrate** | Wire domains together | Solo (always) |
|
|
152
|
-
| **Verify** | Quality gates | Both |
|
|
153
|
-
| **Complete** | Archive + tag | Solo |
|
|
154
|
-
|
|
155
|
-
---
|
|
156
|
-
|
|
157
|
-
## Project Structure
|
|
158
|
-
|
|
159
|
-
```
|
|
160
|
-
your-project/
|
|
161
|
-
├── CLAUDE.md # Project conventions + GSD-T reference
|
|
162
|
-
├── docs/
|
|
163
|
-
│ ├── requirements.md # Functional + technical requirements
|
|
164
|
-
│ ├── architecture.md # System design, components, data flow
|
|
165
|
-
│ ├── workflows.md # User journeys, technical processes
|
|
166
|
-
│ └── infrastructure.md # Dev setup, DB, cloud, deployment
|
|
167
|
-
├── .gsd-t/
|
|
168
|
-
│ ├── progress.md # Master state file
|
|
169
|
-
│ ├── roadmap.md # Milestone roadmap
|
|
170
|
-
│ ├── techdebt.md # Technical debt register
|
|
171
|
-
│ ├── verify-report.md # Latest verification results
|
|
172
|
-
│ ├── impact-report.md # Downstream effect analysis
|
|
173
|
-
│ ├── test-coverage.md # Test sync report
|
|
174
|
-
│ ├── contracts/
|
|
175
|
-
│ │ ├── api-contract.md # API endpoint specifications
|
|
176
|
-
│ │ ├── schema-contract.md # Database/data model specs
|
|
177
|
-
│ │ ├── component-contract.md # UI component interfaces
|
|
178
|
-
│ │ └── integration-points.md # Dependency graph + checkpoints
|
|
179
|
-
│ ├── domains/
|
|
180
|
-
│ │ └── {domain-name}/
|
|
181
|
-
│ │ ├── scope.md # What this domain owns
|
|
182
|
-
│ │ ├── tasks.md # Atomic task list
|
|
183
|
-
│ │ └── constraints.md # Rules and boundaries
|
|
184
|
-
│ ├── milestones/ # Archived completed milestones
|
|
185
|
-
│ │ └── {milestone-name}-{date}/
|
|
186
|
-
│ │ ├── summary.md
|
|
187
|
-
│ │ ├── progress.md
|
|
188
|
-
│ │ ├── verify-report.md
|
|
189
|
-
│ │ ├── contracts/
|
|
190
|
-
│ │ └── domains/
|
|
191
|
-
│ └── scan/ # Codebase analysis outputs
|
|
192
|
-
│ ├── architecture.md
|
|
193
|
-
│ ├── business-rules.md
|
|
194
|
-
│ ├── security.md
|
|
195
|
-
│ └── quality.md
|
|
196
|
-
└── src/
|
|
197
|
-
```
|
|
198
|
-
|
|
199
|
-
---
|
|
200
|
-
|
|
201
|
-
## Key Principles
|
|
202
|
-
|
|
203
|
-
1. **Contracts are the source of truth.** Code implements contracts, not the other way around. If code and contract disagree, fix one or the other — never leave them inconsistent.
|
|
204
|
-
|
|
205
|
-
2. **Domains own files exclusively.** No two domains should modify the same file. If they need shared state, that's a contract.
|
|
206
|
-
|
|
207
|
-
3. **Impact before execution.** Always analyze downstream effects before making changes. Surprises are expensive.
|
|
208
|
-
|
|
209
|
-
4. **Tests stay synced.** Every code change triggers test analysis. Gaps are caught immediately, not in production.
|
|
210
|
-
|
|
211
|
-
5. **State survives sessions.** Everything is in `.gsd-t/`. A fresh Claude Code session can resume from any point by reading the state files.
|
|
212
|
-
|
|
213
|
-
6. **Plan is single-brain, execute is multi-brain.** Planning, impact analysis, and integration require full context (always solo). Execution and verification can parallelize.
|
|
214
|
-
|
|
215
|
-
7. **Every decision is logged.** The Decision Log in progress.md captures why, not just what. Future sessions don't need to re-derive decisions.
|
|
216
|
-
|
|
217
|
-
---
|
|
218
|
-
|
|
219
|
-
## Enabling Agent Teams
|
|
220
|
-
|
|
221
|
-
Agent Teams is an experimental feature. Enable it:
|
|
222
|
-
|
|
223
|
-
```bash
|
|
224
|
-
# Environment variable
|
|
225
|
-
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
|
|
226
|
-
|
|
227
|
-
# Or in settings.json
|
|
228
|
-
{ "experimental": { "agentTeams": true } }
|
|
229
|
-
```
|
|
230
|
-
|
|
231
|
-
Teams are optional — all commands work in solo mode without teams enabled.
|
|
232
|
-
|
|
233
|
-
### When to Use Teams
|
|
234
|
-
|
|
235
|
-
- 3+ domains with independent starting work
|
|
236
|
-
- Codebase scanning and feature impact analysis
|
|
237
|
-
- Complex design questions with multiple viable approaches
|
|
238
|
-
- Verification of large milestones
|
|
239
|
-
- Debugging cross-domain issues
|
|
240
|
-
|
|
241
|
-
---
|
|
242
|
-
|
|
243
|
-
## Installation
|
|
244
|
-
|
|
245
|
-
Copy all `.md` files from this package to `~/.claude/commands/`:
|
|
246
|
-
|
|
247
|
-
```bash
|
|
248
|
-
# Windows
|
|
249
|
-
copy *.md %USERPROFILE%\.claude\commands\
|
|
250
|
-
|
|
251
|
-
# Mac/Linux
|
|
252
|
-
cp *.md ~/.claude/commands/
|
|
253
|
-
```
|
|
254
|
-
|
|
255
|
-
Verify with: `/user:gsd-t-help`
|
|
256
|
-
|
|
257
|
-
---
|
|
258
|
-
|
|
259
|
-
## Configuration
|
|
260
|
-
|
|
261
|
-
GSD-T respects your project's `CLAUDE.md` for conventions and autonomy level.
|
|
262
|
-
|
|
263
|
-
### Autonomy Levels
|
|
264
|
-
|
|
265
|
-
| Level | Phase Behavior |
|
|
266
|
-
|-------|---------------|
|
|
267
|
-
| **Level 1: Supervised** | Pauses at each phase for confirmation |
|
|
268
|
-
| **Level 2: Standard** | Pauses at milestones |
|
|
269
|
-
| **Level 3: Full Auto** (default) | Auto-advances through all phases. Only stops for: Destructive Action Guard, impact BLOCK verdicts, unrecoverable errors (after 2 fix attempts), and the Discuss phase |
|
|
270
|
-
|
|
271
|
-
Set in your project's `CLAUDE.md` under `## Autonomy Level`.
|
|
272
|
-
|
|
273
|
-
Recommended `.gsd-t/config.json`:
|
|
274
|
-
|
|
275
|
-
```json
|
|
276
|
-
{
|
|
277
|
-
"mode": "yolo",
|
|
278
|
-
"model_profile": "quality",
|
|
279
|
-
"workflow": {
|
|
280
|
-
"research": true,
|
|
281
|
-
"impact_check": true,
|
|
282
|
-
"test_sync": true,
|
|
283
|
-
"verifier": true
|
|
284
|
-
}
|
|
285
|
-
}
|
|
286
|
-
```
|
|
287
|
-
|
|
288
|
-
---
|
|
289
|
-
|
|
290
|
-
## License
|
|
291
|
-
|
|
292
|
-
MIT
|
|
1
|
+
# GSD-T: Contract-Driven Development for Claude Code
|
|
2
|
+
|
|
3
|
+
A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
|
|
4
|
+
|
|
5
|
+
## What It Does
|
|
6
|
+
|
|
7
|
+
**Solves context rot** — the quality degradation that happens as Claude fills its context window.
|
|
8
|
+
|
|
9
|
+
**Enables parallel execution** — contract-driven domains can be worked on simultaneously.
|
|
10
|
+
|
|
11
|
+
**Maintains test coverage** — automatically keeps tests aligned with code changes.
|
|
12
|
+
|
|
13
|
+
**Catches downstream effects** — analyzes impact before changes break things.
|
|
14
|
+
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## Quick Start
|
|
18
|
+
|
|
19
|
+
```bash
|
|
20
|
+
# 1. Start Claude Code in your project
|
|
21
|
+
cd my-project
|
|
22
|
+
claude
|
|
23
|
+
|
|
24
|
+
# 2. Full onboarding (git + init + scan + setup in one)
|
|
25
|
+
/user:gsd-t-init-scan-setup
|
|
26
|
+
|
|
27
|
+
# Or step by step:
|
|
28
|
+
/user:gsd-t-init my-project
|
|
29
|
+
|
|
30
|
+
# 3. Define what you're building
|
|
31
|
+
/user:gsd-t-milestone "User Authentication System"
|
|
32
|
+
|
|
33
|
+
# 5. Let it rip (auto-advances through all phases)
|
|
34
|
+
/user:gsd-t-wave
|
|
35
|
+
|
|
36
|
+
# Or go phase by phase for more control:
|
|
37
|
+
/user:gsd-t-partition
|
|
38
|
+
/user:gsd-t-discuss
|
|
39
|
+
/user:gsd-t-plan
|
|
40
|
+
/user:gsd-t-impact
|
|
41
|
+
/user:gsd-t-execute
|
|
42
|
+
/user:gsd-t-test-sync
|
|
43
|
+
/user:gsd-t-integrate
|
|
44
|
+
/user:gsd-t-verify
|
|
45
|
+
/user:gsd-t-complete-milestone
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## Resuming After a Break
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
claude
|
|
52
|
+
/user:gsd-t-resume
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
GSD-T reads all state files and tells you exactly where you left off.
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## Commands Reference
|
|
60
|
+
|
|
61
|
+
### Smart Router
|
|
62
|
+
|
|
63
|
+
| Command | Purpose | Auto |
|
|
64
|
+
|---------|---------|------|
|
|
65
|
+
| `/user:gsd {request}` | Describe what you need → auto-routes to the right command | Manual |
|
|
66
|
+
|
|
67
|
+
### Help & Onboarding
|
|
68
|
+
|
|
69
|
+
| Command | Purpose | Auto |
|
|
70
|
+
|---------|---------|------|
|
|
71
|
+
| `/user:gsd-t-help` | List all commands with descriptions | Manual |
|
|
72
|
+
| `/user:gsd-t-help {cmd}` | Detailed help for specific command | Manual |
|
|
73
|
+
| `/user:gsd-t-prompt` | Help formulate your idea before committing | Manual |
|
|
74
|
+
| `/user:gsd-t-brainstorm` | Creative exploration and idea generation | Manual |
|
|
75
|
+
|
|
76
|
+
### Project Initialization
|
|
77
|
+
|
|
78
|
+
| Command | Purpose | Auto |
|
|
79
|
+
|---------|---------|------|
|
|
80
|
+
| `/user:gsd-t-setup` | Generate or restructure project CLAUDE.md | Manual |
|
|
81
|
+
| `/user:gsd-t-init` | Initialize GSD-T structure in project | Manual |
|
|
82
|
+
| `/user:gsd-t-init-scan-setup` | Full onboarding: git + init + scan + setup in one | Manual |
|
|
83
|
+
| `/user:gsd-t-project` | Full project → milestone roadmap | Manual |
|
|
84
|
+
| `/user:gsd-t-feature` | Major feature → impact analysis + milestones | Manual |
|
|
85
|
+
| `/user:gsd-t-scan` | Deep codebase analysis → techdebt.md | Manual |
|
|
86
|
+
| `/user:gsd-t-gap-analysis` | Requirements gap analysis — spec vs. existing code | Manual |
|
|
87
|
+
| `/user:gsd-t-promote-debt` | Convert techdebt items to milestones | Manual |
|
|
88
|
+
| `/user:gsd-t-populate` | Auto-populate docs from existing codebase | Manual |
|
|
89
|
+
|
|
90
|
+
### Milestone Workflow
|
|
91
|
+
|
|
92
|
+
| Command | Purpose | Auto |
|
|
93
|
+
|---------|---------|------|
|
|
94
|
+
| `/user:gsd-t-milestone` | Define new milestone | Manual |
|
|
95
|
+
| `/user:gsd-t-partition` | Decompose into domains + contracts | In wave |
|
|
96
|
+
| `/user:gsd-t-discuss` | Multi-perspective design exploration | In wave |
|
|
97
|
+
| `/user:gsd-t-plan` | Create atomic task lists per domain | In wave |
|
|
98
|
+
| `/user:gsd-t-impact` | Analyze downstream effects | In wave |
|
|
99
|
+
| `/user:gsd-t-execute` | Run tasks (solo or team) | In wave |
|
|
100
|
+
| `/user:gsd-t-test-sync` | Sync tests with code changes | In wave |
|
|
101
|
+
| `/user:gsd-t-integrate` | Wire domains together | In wave |
|
|
102
|
+
| `/user:gsd-t-verify` | Run quality gates | In wave |
|
|
103
|
+
| `/user:gsd-t-complete-milestone` | Archive + git tag | In wave |
|
|
104
|
+
|
|
105
|
+
### Automation & Utilities
|
|
106
|
+
|
|
107
|
+
| Command | Purpose | Auto |
|
|
108
|
+
|---------|---------|------|
|
|
109
|
+
| `/user:gsd-t-wave` | Full cycle, auto-advances all phases | Manual |
|
|
110
|
+
| `/user:gsd-t-status` | Cross-domain progress view | Manual |
|
|
111
|
+
| `/user:gsd-t-resume` | Restore context, continue | Manual |
|
|
112
|
+
| `/user:gsd-t-quick` | Fast task with GSD-T guarantees | Manual |
|
|
113
|
+
| `/user:gsd-t-debug` | Systematic debugging with state | Manual |
|
|
114
|
+
| `/user:gsd-t-version-update` | Update GSD-T to latest version | Manual |
|
|
115
|
+
| `/user:gsd-t-version-update-all` | Update GSD-T + all registered projects | Manual |
|
|
116
|
+
|
|
117
|
+
---
|
|
118
|
+
|
|
119
|
+
## Workflow Phases
|
|
120
|
+
|
|
121
|
+
```
|
|
122
|
+
┌─────────────────────────────────────────────────────────────────────────────┐
|
|
123
|
+
│ GSD-T Wave Flow │
|
|
124
|
+
├─────────────────────────────────────────────────────────────────────────────┤
|
|
125
|
+
│ │
|
|
126
|
+
│ milestone → partition → discuss → plan → impact → execute → test-sync │
|
|
127
|
+
│ │ │ │
|
|
128
|
+
│ │ └──────┐ │
|
|
129
|
+
│ │ ▼ │
|
|
130
|
+
│ │ ┌───────────────────┐ │
|
|
131
|
+
│ │ │ (runs after each │ │
|
|
132
|
+
│ │ │ task + at verify)│ │
|
|
133
|
+
│ │ └───────────────────┘ │
|
|
134
|
+
│ ▼ │
|
|
135
|
+
│ complete-milestone ◄── verify ◄── integrate ◄──────────────────────┘ │
|
|
136
|
+
│ │
|
|
137
|
+
└─────────────────────────────────────────────────────────────────────────────┘
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
| Phase | Purpose | Solo/Team |
|
|
141
|
+
|-------|---------|-----------|
|
|
142
|
+
| **Prompt** | Formulate idea (pre-workflow) | Solo |
|
|
143
|
+
| **Project/Feature/Scan** | Initialize work | Solo (team for large scans) |
|
|
144
|
+
| **Milestone** | Define deliverable | Solo |
|
|
145
|
+
| **Partition** | Decompose into domains + contracts | Solo |
|
|
146
|
+
| **Discuss** | Explore design decisions | Both |
|
|
147
|
+
| **Plan** | Create atomic task lists | Solo (always) |
|
|
148
|
+
| **Impact** | Downstream effect analysis | Solo |
|
|
149
|
+
| **Execute** | Build it | Both |
|
|
150
|
+
| **Test-Sync** | Maintain test coverage | Solo |
|
|
151
|
+
| **Integrate** | Wire domains together | Solo (always) |
|
|
152
|
+
| **Verify** | Quality gates | Both |
|
|
153
|
+
| **Complete** | Archive + tag | Solo |
|
|
154
|
+
|
|
155
|
+
---
|
|
156
|
+
|
|
157
|
+
## Project Structure
|
|
158
|
+
|
|
159
|
+
```
|
|
160
|
+
your-project/
|
|
161
|
+
├── CLAUDE.md # Project conventions + GSD-T reference
|
|
162
|
+
├── docs/
|
|
163
|
+
│ ├── requirements.md # Functional + technical requirements
|
|
164
|
+
│ ├── architecture.md # System design, components, data flow
|
|
165
|
+
│ ├── workflows.md # User journeys, technical processes
|
|
166
|
+
│ └── infrastructure.md # Dev setup, DB, cloud, deployment
|
|
167
|
+
├── .gsd-t/
|
|
168
|
+
│ ├── progress.md # Master state file
|
|
169
|
+
│ ├── roadmap.md # Milestone roadmap
|
|
170
|
+
│ ├── techdebt.md # Technical debt register
|
|
171
|
+
│ ├── verify-report.md # Latest verification results
|
|
172
|
+
│ ├── impact-report.md # Downstream effect analysis
|
|
173
|
+
│ ├── test-coverage.md # Test sync report
|
|
174
|
+
│ ├── contracts/
|
|
175
|
+
│ │ ├── api-contract.md # API endpoint specifications
|
|
176
|
+
│ │ ├── schema-contract.md # Database/data model specs
|
|
177
|
+
│ │ ├── component-contract.md # UI component interfaces
|
|
178
|
+
│ │ └── integration-points.md # Dependency graph + checkpoints
|
|
179
|
+
│ ├── domains/
|
|
180
|
+
│ │ └── {domain-name}/
|
|
181
|
+
│ │ ├── scope.md # What this domain owns
|
|
182
|
+
│ │ ├── tasks.md # Atomic task list
|
|
183
|
+
│ │ └── constraints.md # Rules and boundaries
|
|
184
|
+
│ ├── milestones/ # Archived completed milestones
|
|
185
|
+
│ │ └── {milestone-name}-{date}/
|
|
186
|
+
│ │ ├── summary.md
|
|
187
|
+
│ │ ├── progress.md
|
|
188
|
+
│ │ ├── verify-report.md
|
|
189
|
+
│ │ ├── contracts/
|
|
190
|
+
│ │ └── domains/
|
|
191
|
+
│ └── scan/ # Codebase analysis outputs
|
|
192
|
+
│ ├── architecture.md
|
|
193
|
+
│ ├── business-rules.md
|
|
194
|
+
│ ├── security.md
|
|
195
|
+
│ └── quality.md
|
|
196
|
+
└── src/
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
---
|
|
200
|
+
|
|
201
|
+
## Key Principles
|
|
202
|
+
|
|
203
|
+
1. **Contracts are the source of truth.** Code implements contracts, not the other way around. If code and contract disagree, fix one or the other — never leave them inconsistent.
|
|
204
|
+
|
|
205
|
+
2. **Domains own files exclusively.** No two domains should modify the same file. If they need shared state, that's a contract.
|
|
206
|
+
|
|
207
|
+
3. **Impact before execution.** Always analyze downstream effects before making changes. Surprises are expensive.
|
|
208
|
+
|
|
209
|
+
4. **Tests stay synced.** Every code change triggers test analysis. Gaps are caught immediately, not in production.
|
|
210
|
+
|
|
211
|
+
5. **State survives sessions.** Everything is in `.gsd-t/`. A fresh Claude Code session can resume from any point by reading the state files.
|
|
212
|
+
|
|
213
|
+
6. **Plan is single-brain, execute is multi-brain.** Planning, impact analysis, and integration require full context (always solo). Execution and verification can parallelize.
|
|
214
|
+
|
|
215
|
+
7. **Every decision is logged.** The Decision Log in progress.md captures why, not just what. Future sessions don't need to re-derive decisions.
|
|
216
|
+
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
## Enabling Agent Teams
|
|
220
|
+
|
|
221
|
+
Agent Teams is an experimental feature. Enable it:
|
|
222
|
+
|
|
223
|
+
```bash
|
|
224
|
+
# Environment variable
|
|
225
|
+
export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
|
|
226
|
+
|
|
227
|
+
# Or in settings.json
|
|
228
|
+
{ "experimental": { "agentTeams": true } }
|
|
229
|
+
```
|
|
230
|
+
|
|
231
|
+
Teams are optional — all commands work in solo mode without teams enabled.
|
|
232
|
+
|
|
233
|
+
### When to Use Teams
|
|
234
|
+
|
|
235
|
+
- 3+ domains with independent starting work
|
|
236
|
+
- Codebase scanning and feature impact analysis
|
|
237
|
+
- Complex design questions with multiple viable approaches
|
|
238
|
+
- Verification of large milestones
|
|
239
|
+
- Debugging cross-domain issues
|
|
240
|
+
|
|
241
|
+
---
|
|
242
|
+
|
|
243
|
+
## Installation
|
|
244
|
+
|
|
245
|
+
Copy all `.md` files from this package to `~/.claude/commands/`:
|
|
246
|
+
|
|
247
|
+
```bash
|
|
248
|
+
# Windows
|
|
249
|
+
copy *.md %USERPROFILE%\.claude\commands\
|
|
250
|
+
|
|
251
|
+
# Mac/Linux
|
|
252
|
+
cp *.md ~/.claude/commands/
|
|
253
|
+
```
|
|
254
|
+
|
|
255
|
+
Verify with: `/user:gsd-t-help`
|
|
256
|
+
|
|
257
|
+
---
|
|
258
|
+
|
|
259
|
+
## Configuration
|
|
260
|
+
|
|
261
|
+
GSD-T respects your project's `CLAUDE.md` for conventions and autonomy level.
|
|
262
|
+
|
|
263
|
+
### Autonomy Levels
|
|
264
|
+
|
|
265
|
+
| Level | Phase Behavior |
|
|
266
|
+
|-------|---------------|
|
|
267
|
+
| **Level 1: Supervised** | Pauses at each phase for confirmation |
|
|
268
|
+
| **Level 2: Standard** | Pauses at milestones |
|
|
269
|
+
| **Level 3: Full Auto** (default) | Auto-advances through all phases. Only stops for: Destructive Action Guard, impact BLOCK verdicts, unrecoverable errors (after 2 fix attempts), and the Discuss phase |
|
|
270
|
+
|
|
271
|
+
Set in your project's `CLAUDE.md` under `## Autonomy Level`.
|
|
272
|
+
|
|
273
|
+
Recommended `.gsd-t/config.json`:
|
|
274
|
+
|
|
275
|
+
```json
|
|
276
|
+
{
|
|
277
|
+
"mode": "yolo",
|
|
278
|
+
"model_profile": "quality",
|
|
279
|
+
"workflow": {
|
|
280
|
+
"research": true,
|
|
281
|
+
"impact_check": true,
|
|
282
|
+
"test_sync": true,
|
|
283
|
+
"verifier": true
|
|
284
|
+
}
|
|
285
|
+
}
|
|
286
|
+
```
|
|
287
|
+
|
|
288
|
+
---
|
|
289
|
+
|
|
290
|
+
## License
|
|
291
|
+
|
|
292
|
+
MIT
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tekyzinc/gsd-t",
|
|
3
|
-
"version": "2.16.
|
|
3
|
+
"version": "2.16.3",
|
|
4
4
|
"description": "GSD-T: Contract-Driven Development for Claude Code — 40 slash commands with backlog management, impact analysis, test sync, and milestone archival",
|
|
5
5
|
"author": "Tekyz, Inc.",
|
|
6
6
|
"license": "MIT",
|
|
@@ -27,7 +27,7 @@ PROJECT or FEATURE or SCAN
|
|
|
27
27
|
|
|
28
28
|
| Command | Purpose |
|
|
29
29
|
|---------|---------|
|
|
30
|
-
| `/user:gsd` | Smart router — describe what you need, auto-routes to the right command |
|
|
30
|
+
| `/user:gsd-t` | Smart router — describe what you need, auto-routes to the right command |
|
|
31
31
|
| `/user:gsd-t-help` | List all commands or get detailed help |
|
|
32
32
|
| `/user:gsd-t-prompt` | Help formulate your idea before committing |
|
|
33
33
|
| `/user:gsd-t-brainstorm` | Creative exploration and idea generation |
|
|
@@ -205,8 +205,11 @@ BEFORE EVERY COMMIT:
|
|
|
205
205
|
│ YES → Update docs/requirements.md (mark complete or revise)
|
|
206
206
|
├── Did I add/change/remove a component or change data flow?
|
|
207
207
|
│ YES → Update docs/architecture.md
|
|
208
|
+
├── Did I complete a task or make a meaningful change?
|
|
209
|
+
│ YES → Add timestamped entry to .gsd-t/progress.md Decision Log
|
|
210
|
+
│ Format: `- YYYY-MM-DD HH:MM: {what was done} — {brief context or result}`
|
|
208
211
|
├── Did I make an architectural or design decision?
|
|
209
|
-
│ YES → Add to .gsd-t/progress.md Decision Log
|
|
212
|
+
│ YES → Add to .gsd-t/progress.md Decision Log (with decision rationale)
|
|
210
213
|
├── Did I discover or fix tech debt?
|
|
211
214
|
│ YES → Update .gsd-t/techdebt.md
|
|
212
215
|
├── Did I establish a pattern future work should follow?
|