gsd-ag 1.0.0
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/.agent/skills/codebase-mapper/SKILL.md +226 -0
- package/.agent/skills/context-compressor/SKILL.md +201 -0
- package/.agent/skills/context-fetch/SKILL.md +184 -0
- package/.agent/skills/context-health-monitor/SKILL.md +105 -0
- package/.agent/skills/debugger/SKILL.md +273 -0
- package/.agent/skills/empirical-validation/SKILL.md +97 -0
- package/.agent/skills/executor/SKILL.md +465 -0
- package/.agent/skills/plan-checker/SKILL.md +283 -0
- package/.agent/skills/planner/SKILL.md +485 -0
- package/.agent/skills/token-budget/SKILL.md +166 -0
- package/.agent/skills/verifier/SKILL.md +421 -0
- package/.agent/workflows/add-phase.md +96 -0
- package/.agent/workflows/add-todo.md +69 -0
- package/.agent/workflows/audit-milestone.md +107 -0
- package/.agent/workflows/check-todos.md +80 -0
- package/.agent/workflows/complete-milestone.md +135 -0
- package/.agent/workflows/debug.md +235 -0
- package/.agent/workflows/discuss-phase.md +103 -0
- package/.agent/workflows/execute.md +325 -0
- package/.agent/workflows/health.md +122 -0
- package/.agent/workflows/help.md +96 -0
- package/.agent/workflows/insert-phase.md +109 -0
- package/.agent/workflows/install.md +152 -0
- package/.agent/workflows/list-phase-assumptions.md +82 -0
- package/.agent/workflows/map.md +394 -0
- package/.agent/workflows/new-milestone.md +126 -0
- package/.agent/workflows/new-project.md +368 -0
- package/.agent/workflows/pause.md +176 -0
- package/.agent/workflows/plan-milestone-gaps.md +116 -0
- package/.agent/workflows/plan.md +380 -0
- package/.agent/workflows/progress.md +90 -0
- package/.agent/workflows/quick.md +128 -0
- package/.agent/workflows/remove-phase.md +139 -0
- package/.agent/workflows/research-phase.md +160 -0
- package/.agent/workflows/resume.md +131 -0
- package/.agent/workflows/update.md +203 -0
- package/.agent/workflows/verify.md +263 -0
- package/.agent/workflows/web-search.md +121 -0
- package/.agent/workflows/whats-new.md +80 -0
- package/.gemini/GEMINI.md +67 -0
- package/.gsd/GSD-STYLE.md +272 -0
- package/.gsd/PROJECT_RULES.md +256 -0
- package/.gsd/adapters/CLAUDE.md +77 -0
- package/.gsd/adapters/GEMINI.md +92 -0
- package/.gsd/adapters/GPT_OSS.md +130 -0
- package/.gsd/docs/model-selection-playbook.md +128 -0
- package/.gsd/docs/runbook.md +296 -0
- package/.gsd/docs/token-optimization-guide.md +207 -0
- package/.gsd/examples/cross-platform.md +99 -0
- package/.gsd/examples/multi-wave-workflow.md +256 -0
- package/.gsd/examples/quick-reference.md +73 -0
- package/.gsd/examples/workflow-example.md +139 -0
- package/.gsd/model_capabilities.yaml +108 -0
- package/.gsd/templates/DEBUG.md +123 -0
- package/.gsd/templates/PLAN.md +90 -0
- package/.gsd/templates/RESEARCH.md +75 -0
- package/.gsd/templates/SUMMARY.md +103 -0
- package/.gsd/templates/UAT.md +168 -0
- package/.gsd/templates/VERIFICATION.md +70 -0
- package/.gsd/templates/architecture.md +67 -0
- package/.gsd/templates/context.md +91 -0
- package/.gsd/templates/decisions.md +37 -0
- package/.gsd/templates/discovery.md +122 -0
- package/.gsd/templates/journal.md +46 -0
- package/.gsd/templates/milestone.md +91 -0
- package/.gsd/templates/phase-summary.md +52 -0
- package/.gsd/templates/project.md +124 -0
- package/.gsd/templates/requirements.md +92 -0
- package/.gsd/templates/roadmap.md +103 -0
- package/.gsd/templates/spec.md +51 -0
- package/.gsd/templates/sprint.md +57 -0
- package/.gsd/templates/stack.md +62 -0
- package/.gsd/templates/state.md +92 -0
- package/.gsd/templates/state_snapshot.md +132 -0
- package/.gsd/templates/todo.md +32 -0
- package/.gsd/templates/token_report.md +79 -0
- package/.gsd/templates/user-setup.md +116 -0
- package/LICENSE +21 -0
- package/README.md +523 -0
- package/bin/init.js +117 -0
- package/package.json +35 -0
|
@@ -0,0 +1,139 @@
|
|
|
1
|
+
# GSD Workflow Example
|
|
2
|
+
|
|
3
|
+
> A complete walkthrough of using GSD from start to finish.
|
|
4
|
+
|
|
5
|
+
## Scenario: Building a Simple Todo API
|
|
6
|
+
|
|
7
|
+
### Step 1: Define the Spec
|
|
8
|
+
|
|
9
|
+
First, fill out `.gsd/SPEC.md`:
|
|
10
|
+
|
|
11
|
+
```markdown
|
|
12
|
+
# SPEC.md
|
|
13
|
+
|
|
14
|
+
> **Status**: `FINALIZED`
|
|
15
|
+
|
|
16
|
+
## Vision
|
|
17
|
+
A simple RESTful API for managing todo items.
|
|
18
|
+
|
|
19
|
+
## Goals
|
|
20
|
+
1. CRUD operations for todos
|
|
21
|
+
2. Persistence to SQLite
|
|
22
|
+
3. Input validation
|
|
23
|
+
|
|
24
|
+
## Success Criteria
|
|
25
|
+
- [ ] POST /todos creates a todo
|
|
26
|
+
- [ ] GET /todos returns list
|
|
27
|
+
- [ ] DELETE /todos/:id removes item
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
### Step 2: Map the Codebase (if existing)
|
|
33
|
+
|
|
34
|
+
```
|
|
35
|
+
/map
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
This creates:
|
|
39
|
+
- `.gsd/ARCHITECTURE.md` — Current structure
|
|
40
|
+
- `.gsd/STACK.md` — Technologies in use
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
44
|
+
### Step 3: Plan the Phases
|
|
45
|
+
|
|
46
|
+
```
|
|
47
|
+
/plan 1
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
GSD analyzes the SPEC and creates `.gsd/phases/1/` with PLAN.md files:
|
|
51
|
+
|
|
52
|
+
```markdown
|
|
53
|
+
# Plan 1.1: Database Setup
|
|
54
|
+
|
|
55
|
+
## Objective
|
|
56
|
+
Create SQLite database with todos table.
|
|
57
|
+
|
|
58
|
+
## Tasks
|
|
59
|
+
|
|
60
|
+
<task type="auto">
|
|
61
|
+
<name>Initialize SQLite database</name>
|
|
62
|
+
<files>src/db.ts</files>
|
|
63
|
+
<action>
|
|
64
|
+
Create SQLite connection using better-sqlite3.
|
|
65
|
+
Create todos table with: id, title, completed, created_at.
|
|
66
|
+
</action>
|
|
67
|
+
<verify>node -e "require('./src/db')" exits without error</verify>
|
|
68
|
+
<done>Database file exists, table created</done>
|
|
69
|
+
</task>
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
---
|
|
73
|
+
|
|
74
|
+
### Step 4: Execute the Phase
|
|
75
|
+
|
|
76
|
+
```
|
|
77
|
+
/execute 1
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
GSD:
|
|
81
|
+
1. Loads Plan 1.1
|
|
82
|
+
2. Executes tasks in order
|
|
83
|
+
3. Runs verify commands
|
|
84
|
+
4. Creates atomic commits
|
|
85
|
+
5. Creates SUMMARY.md
|
|
86
|
+
6. Proceeds to Plan 1.2
|
|
87
|
+
7. Verifies phase goal
|
|
88
|
+
|
|
89
|
+
---
|
|
90
|
+
|
|
91
|
+
### Step 5: Verify the Work
|
|
92
|
+
|
|
93
|
+
```
|
|
94
|
+
/verify 1
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
GSD:
|
|
98
|
+
1. Extracts must-haves from phase
|
|
99
|
+
2. Runs verification commands
|
|
100
|
+
3. Captures evidence
|
|
101
|
+
4. Creates VERIFICATION.md
|
|
102
|
+
5. Reports pass/fail
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
### Step 6: Continue or Debug
|
|
107
|
+
|
|
108
|
+
**If verified:**
|
|
109
|
+
```
|
|
110
|
+
/plan 2 → Plan next phase
|
|
111
|
+
/execute 2 → Execute next phase
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
**If issues found:**
|
|
115
|
+
```
|
|
116
|
+
/execute 1 --gaps-only → Run fix plans
|
|
117
|
+
/debug "API returns 500" → Debug the issue
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
---
|
|
121
|
+
|
|
122
|
+
## Quick Commands Reference
|
|
123
|
+
|
|
124
|
+
| Command | When to Use |
|
|
125
|
+
|---------|-------------|
|
|
126
|
+
| `/map` | Analyze existing codebase |
|
|
127
|
+
| `/plan [N]` | Create plans for phase N |
|
|
128
|
+
| `/execute [N]` | Run all plans in phase N |
|
|
129
|
+
| `/verify [N]` | Confirm phase N works |
|
|
130
|
+
| `/debug [issue]` | Fix a problem |
|
|
131
|
+
| `/progress` | See current status |
|
|
132
|
+
| `/pause` | End session, save state |
|
|
133
|
+
| `/resume` | Start new session |
|
|
134
|
+
| `/add-todo` | Capture quick idea |
|
|
135
|
+
| `/check-todos` | See pending items |
|
|
136
|
+
|
|
137
|
+
---
|
|
138
|
+
|
|
139
|
+
*This example demonstrates the GSD methodology flow.*
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Model Capabilities Registry
|
|
2
|
+
#
|
|
3
|
+
# This file is OPTIONAL. GSD works without it.
|
|
4
|
+
# If present, it provides guidance for model selection.
|
|
5
|
+
#
|
|
6
|
+
# Usage: Reference this file when choosing models by capability.
|
|
7
|
+
# Do NOT make any workflow depend on this file existing.
|
|
8
|
+
|
|
9
|
+
# Capability definitions
|
|
10
|
+
capabilities:
|
|
11
|
+
thinking_mode:
|
|
12
|
+
description: "Extended reasoning with internal monologue"
|
|
13
|
+
benefits:
|
|
14
|
+
- Better for complex planning
|
|
15
|
+
- Improved debugging hypotheses
|
|
16
|
+
- More thorough architecture analysis
|
|
17
|
+
|
|
18
|
+
long_context:
|
|
19
|
+
description: "Context window > 100k tokens"
|
|
20
|
+
benefits:
|
|
21
|
+
- Can analyze multiple files at once
|
|
22
|
+
- Better for large refactors
|
|
23
|
+
- Full codebase reviews
|
|
24
|
+
|
|
25
|
+
tools:
|
|
26
|
+
description: "Function/tool calling support"
|
|
27
|
+
benefits:
|
|
28
|
+
- Execute verification commands
|
|
29
|
+
- Interact with external systems
|
|
30
|
+
- Structured outputs
|
|
31
|
+
|
|
32
|
+
speed_tier:
|
|
33
|
+
description: "Response latency tier"
|
|
34
|
+
values:
|
|
35
|
+
- fast: "< 2s average, good for iteration"
|
|
36
|
+
- standard: "2-5s average, balanced"
|
|
37
|
+
- reasoning: "> 5s average, deep analysis"
|
|
38
|
+
|
|
39
|
+
# Example model profiles (illustrative, not exhaustive)
|
|
40
|
+
# These show how to categorize models by capability type.
|
|
41
|
+
|
|
42
|
+
profiles:
|
|
43
|
+
# Fast iteration models
|
|
44
|
+
fast_coder:
|
|
45
|
+
speed_tier: fast
|
|
46
|
+
thinking_mode: false
|
|
47
|
+
long_context: false
|
|
48
|
+
tools: true
|
|
49
|
+
best_for:
|
|
50
|
+
- Quick edits
|
|
51
|
+
- Simple implementations
|
|
52
|
+
- Frequent iteration cycles
|
|
53
|
+
examples:
|
|
54
|
+
- "Flash/Turbo variants"
|
|
55
|
+
- "Smaller parameter models"
|
|
56
|
+
|
|
57
|
+
# Standard balanced models
|
|
58
|
+
standard:
|
|
59
|
+
speed_tier: standard
|
|
60
|
+
thinking_mode: false
|
|
61
|
+
long_context: true
|
|
62
|
+
tools: true
|
|
63
|
+
best_for:
|
|
64
|
+
- Most development tasks
|
|
65
|
+
- Moderate refactoring
|
|
66
|
+
- General coding
|
|
67
|
+
examples:
|
|
68
|
+
- "Pro/Standard variants"
|
|
69
|
+
- "Mid-tier models"
|
|
70
|
+
|
|
71
|
+
# Deep reasoning models
|
|
72
|
+
reasoning:
|
|
73
|
+
speed_tier: reasoning
|
|
74
|
+
thinking_mode: true
|
|
75
|
+
long_context: true
|
|
76
|
+
tools: true
|
|
77
|
+
best_for:
|
|
78
|
+
- Architecture planning
|
|
79
|
+
- Complex debugging
|
|
80
|
+
- Security analysis
|
|
81
|
+
examples:
|
|
82
|
+
- "Thinking/Reasoning variants"
|
|
83
|
+
- "Advanced reasoning models"
|
|
84
|
+
|
|
85
|
+
# Phase recommendations (suggestions, not requirements)
|
|
86
|
+
phase_recommendations:
|
|
87
|
+
planning:
|
|
88
|
+
preferred_profile: reasoning
|
|
89
|
+
reason: "Complex decisions benefit from extended thinking"
|
|
90
|
+
|
|
91
|
+
implementation:
|
|
92
|
+
preferred_profile: fast_coder
|
|
93
|
+
reason: "Frequent iteration needs speed"
|
|
94
|
+
|
|
95
|
+
refactoring:
|
|
96
|
+
preferred_profile: standard
|
|
97
|
+
reason: "Balance of context and speed"
|
|
98
|
+
|
|
99
|
+
debugging:
|
|
100
|
+
preferred_profile: reasoning
|
|
101
|
+
reason: "Hypothesis generation needs depth"
|
|
102
|
+
|
|
103
|
+
review:
|
|
104
|
+
preferred_profile: standard
|
|
105
|
+
reason: "Large context for full diffs"
|
|
106
|
+
|
|
107
|
+
# IMPORTANT: This file is for guidance only.
|
|
108
|
+
# Never fail a workflow because a specific model capability is missing.
|
|
@@ -0,0 +1,123 @@
|
|
|
1
|
+
# Debug Template
|
|
2
|
+
|
|
3
|
+
Template for `.gsd/debug/[slug].md` — active debug session tracking.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## File Template
|
|
8
|
+
|
|
9
|
+
```markdown
|
|
10
|
+
---
|
|
11
|
+
status: gathering | investigating | fixing | verifying | resolved
|
|
12
|
+
trigger: "[verbatim user input]"
|
|
13
|
+
created: [ISO timestamp]
|
|
14
|
+
updated: [ISO timestamp]
|
|
15
|
+
---
|
|
16
|
+
|
|
17
|
+
## Current Focus
|
|
18
|
+
<!-- OVERWRITE on each update - always reflects NOW -->
|
|
19
|
+
|
|
20
|
+
hypothesis: [current theory being tested]
|
|
21
|
+
test: [how testing it]
|
|
22
|
+
expecting: [what result means if true/false]
|
|
23
|
+
next_action: [immediate next step]
|
|
24
|
+
|
|
25
|
+
## Symptoms
|
|
26
|
+
<!-- Written during gathering, then immutable -->
|
|
27
|
+
|
|
28
|
+
expected: [what should happen]
|
|
29
|
+
actual: [what actually happens]
|
|
30
|
+
errors: [error messages if any]
|
|
31
|
+
reproduction: [how to trigger]
|
|
32
|
+
started: [when it broke / always broken]
|
|
33
|
+
|
|
34
|
+
## Eliminated
|
|
35
|
+
<!-- APPEND only - prevents re-investigating after context reset -->
|
|
36
|
+
|
|
37
|
+
- hypothesis: [theory that was wrong]
|
|
38
|
+
evidence: [what disproved it]
|
|
39
|
+
timestamp: [when eliminated]
|
|
40
|
+
|
|
41
|
+
## Evidence
|
|
42
|
+
<!-- APPEND only - facts discovered during investigation -->
|
|
43
|
+
|
|
44
|
+
- timestamp: [when found]
|
|
45
|
+
checked: [what was examined]
|
|
46
|
+
found: [what was observed]
|
|
47
|
+
implication: [what this means]
|
|
48
|
+
|
|
49
|
+
## Resolution
|
|
50
|
+
<!-- OVERWRITE as understanding evolves -->
|
|
51
|
+
|
|
52
|
+
root_cause: [empty until found]
|
|
53
|
+
fix: [empty until applied]
|
|
54
|
+
verification: [empty until verified]
|
|
55
|
+
files_changed: []
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
---
|
|
59
|
+
|
|
60
|
+
## Section Rules
|
|
61
|
+
|
|
62
|
+
**Frontmatter (status, trigger, timestamps):**
|
|
63
|
+
- `status`: OVERWRITE - reflects current phase
|
|
64
|
+
- `trigger`: IMMUTABLE - verbatim user input, never changes
|
|
65
|
+
- `created`: IMMUTABLE - set once
|
|
66
|
+
- `updated`: OVERWRITE - update on every change
|
|
67
|
+
|
|
68
|
+
**Current Focus:**
|
|
69
|
+
- OVERWRITE entirely on each update
|
|
70
|
+
- Always reflects what AI is doing RIGHT NOW
|
|
71
|
+
- If AI reads this after session reset, it knows exactly where to resume
|
|
72
|
+
- Fields: hypothesis, test, expecting, next_action
|
|
73
|
+
|
|
74
|
+
**Symptoms:**
|
|
75
|
+
- Written during initial gathering phase
|
|
76
|
+
- IMMUTABLE after gathering complete
|
|
77
|
+
- Reference point for what we're trying to fix
|
|
78
|
+
|
|
79
|
+
**Eliminated:**
|
|
80
|
+
- APPEND only - never remove entries
|
|
81
|
+
- Prevents re-investigating dead ends after context reset
|
|
82
|
+
- Critical for efficiency across session boundaries
|
|
83
|
+
|
|
84
|
+
**Evidence:**
|
|
85
|
+
- APPEND only - never remove entries
|
|
86
|
+
- Facts discovered during investigation
|
|
87
|
+
- Builds the case for root cause
|
|
88
|
+
|
|
89
|
+
**Resolution:**
|
|
90
|
+
- OVERWRITE as understanding evolves
|
|
91
|
+
- Final state shows confirmed root cause and verified fix
|
|
92
|
+
|
|
93
|
+
---
|
|
94
|
+
|
|
95
|
+
## Lifecycle
|
|
96
|
+
|
|
97
|
+
**Creation:** When /debug is called
|
|
98
|
+
- Create file with trigger from user input
|
|
99
|
+
- Set status to "gathering"
|
|
100
|
+
- next_action = "gather symptoms"
|
|
101
|
+
|
|
102
|
+
**During investigation:**
|
|
103
|
+
- OVERWRITE Current Focus with each hypothesis
|
|
104
|
+
- APPEND to Evidence with each finding
|
|
105
|
+
- APPEND to Eliminated when hypothesis disproved
|
|
106
|
+
|
|
107
|
+
**On resolution:**
|
|
108
|
+
- status → "resolved"
|
|
109
|
+
- Move file to .gsd/debug/resolved/
|
|
110
|
+
|
|
111
|
+
---
|
|
112
|
+
|
|
113
|
+
## Resume Behavior
|
|
114
|
+
|
|
115
|
+
When AI reads this file after session reset:
|
|
116
|
+
|
|
117
|
+
1. Parse frontmatter → know status
|
|
118
|
+
2. Read Current Focus → know exactly what was happening
|
|
119
|
+
3. Read Eliminated → know what NOT to retry
|
|
120
|
+
4. Read Evidence → know what's been learned
|
|
121
|
+
5. Continue from next_action
|
|
122
|
+
|
|
123
|
+
The file IS the debugging brain.
|
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
# PLAN.md Template
|
|
2
|
+
|
|
3
|
+
> Copy this template when creating execution plans.
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
---
|
|
7
|
+
phase: {N}
|
|
8
|
+
plan: {M}
|
|
9
|
+
wave: {W}
|
|
10
|
+
gap_closure: false
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
# Plan {N}.{M}: {Descriptive Name}
|
|
14
|
+
|
|
15
|
+
## Objective
|
|
16
|
+
{One paragraph explaining what this plan delivers and why it matters}
|
|
17
|
+
|
|
18
|
+
## Context
|
|
19
|
+
Load these files for context:
|
|
20
|
+
- .gsd/SPEC.md
|
|
21
|
+
- .gsd/ARCHITECTURE.md
|
|
22
|
+
- {relevant source files}
|
|
23
|
+
|
|
24
|
+
## Tasks
|
|
25
|
+
|
|
26
|
+
<task type="auto">
|
|
27
|
+
<name>{Clear, specific task name}</name>
|
|
28
|
+
<files>
|
|
29
|
+
{exact/file/path1.ext}
|
|
30
|
+
{exact/file/path2.ext}
|
|
31
|
+
</files>
|
|
32
|
+
<action>
|
|
33
|
+
{Specific implementation instructions}
|
|
34
|
+
|
|
35
|
+
Steps:
|
|
36
|
+
1. {Step 1}
|
|
37
|
+
2. {Step 2}
|
|
38
|
+
3. {Step 3}
|
|
39
|
+
|
|
40
|
+
AVOID: {common mistake} because {reason}
|
|
41
|
+
USE: {preferred approach} because {reason}
|
|
42
|
+
</action>
|
|
43
|
+
<verify>
|
|
44
|
+
{Executable command or check}
|
|
45
|
+
Example: npm test -- --testNamePattern="auth"
|
|
46
|
+
Example: curl -X POST localhost:3000/api/login
|
|
47
|
+
</verify>
|
|
48
|
+
<done>
|
|
49
|
+
{Measurable acceptance criteria}
|
|
50
|
+
Example: Valid credentials → 200 + Set-Cookie, invalid → 401
|
|
51
|
+
</done>
|
|
52
|
+
</task>
|
|
53
|
+
|
|
54
|
+
<task type="auto">
|
|
55
|
+
<name>{Task 2 name}</name>
|
|
56
|
+
<files>{files}</files>
|
|
57
|
+
<action>{instructions}</action>
|
|
58
|
+
<verify>{command}</verify>
|
|
59
|
+
<done>{criteria}</done>
|
|
60
|
+
</task>
|
|
61
|
+
|
|
62
|
+
## Must-Haves
|
|
63
|
+
After all tasks complete, verify:
|
|
64
|
+
- [ ] {Must-have 1 — derived from phase goal}
|
|
65
|
+
- [ ] {Must-have 2}
|
|
66
|
+
|
|
67
|
+
## Success Criteria
|
|
68
|
+
- [ ] All tasks verified passing
|
|
69
|
+
- [ ] Must-haves confirmed
|
|
70
|
+
- [ ] No regressions in tests
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
## Task Types
|
|
74
|
+
|
|
75
|
+
| Type | Use For | Behavior |
|
|
76
|
+
|------|---------|----------|
|
|
77
|
+
| `auto` | Everything Claude can do independently | Fully autonomous |
|
|
78
|
+
| `checkpoint:human-verify` | Visual/functional verification | Pauses for user |
|
|
79
|
+
| `checkpoint:decision` | Implementation choices | Pauses for user |
|
|
80
|
+
|
|
81
|
+
## Wave Assignment
|
|
82
|
+
|
|
83
|
+
| Wave | Use For |
|
|
84
|
+
|------|---------|
|
|
85
|
+
| 1 | Foundation (types, schemas, utilities) |
|
|
86
|
+
| 2 | Core implementations |
|
|
87
|
+
| 3 | Integration and validation |
|
|
88
|
+
|
|
89
|
+
Plans in the same wave can run in parallel.
|
|
90
|
+
Later waves depend on earlier waves.
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
# RESEARCH.md Template
|
|
2
|
+
|
|
3
|
+
> Copy this template when documenting phase research.
|
|
4
|
+
|
|
5
|
+
```markdown
|
|
6
|
+
---
|
|
7
|
+
phase: {N}
|
|
8
|
+
researched_at: {YYYY-MM-DD}
|
|
9
|
+
discovery_level: 1 | 2 | 3
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
# Phase {N} Research
|
|
13
|
+
|
|
14
|
+
## Objective
|
|
15
|
+
{What question is this research answering?}
|
|
16
|
+
|
|
17
|
+
## Discovery Level
|
|
18
|
+
**Level {1|2|3}** — {Quick verification | Standard research | Deep dive}
|
|
19
|
+
|
|
20
|
+
## Key Decisions
|
|
21
|
+
|
|
22
|
+
### Decision 1: {Topic}
|
|
23
|
+
**Question:** {What needed to be decided?}
|
|
24
|
+
**Options Considered:**
|
|
25
|
+
1. {Option A}: {pros/cons}
|
|
26
|
+
2. {Option B}: {pros/cons}
|
|
27
|
+
3. {Option C}: {pros/cons}
|
|
28
|
+
|
|
29
|
+
**Decision:** {Which option and why}
|
|
30
|
+
**Confidence:** {High | Medium | Low}
|
|
31
|
+
|
|
32
|
+
### Decision 2: {Topic}
|
|
33
|
+
...
|
|
34
|
+
|
|
35
|
+
## Findings
|
|
36
|
+
|
|
37
|
+
### {Topic 1}
|
|
38
|
+
{What was learned}
|
|
39
|
+
|
|
40
|
+
**Sources:**
|
|
41
|
+
- {URL or reference}
|
|
42
|
+
- {URL or reference}
|
|
43
|
+
|
|
44
|
+
### {Topic 2}
|
|
45
|
+
{What was learned}
|
|
46
|
+
|
|
47
|
+
## Patterns to Follow
|
|
48
|
+
- {Pattern 1}: {How to apply it}
|
|
49
|
+
- {Pattern 2}: {How to apply it}
|
|
50
|
+
|
|
51
|
+
## Anti-Patterns to Avoid
|
|
52
|
+
- {Anti-pattern 1}: {Why to avoid}
|
|
53
|
+
- {Anti-pattern 2}: {Why to avoid}
|
|
54
|
+
|
|
55
|
+
## Dependencies Identified
|
|
56
|
+
| Package | Version | Purpose |
|
|
57
|
+
|---------|---------|---------|
|
|
58
|
+
| {pkg} | {ver} | {why needed} |
|
|
59
|
+
|
|
60
|
+
## Risks
|
|
61
|
+
- **{Risk 1}:** {Impact and mitigation}
|
|
62
|
+
- **{Risk 2}:** {Impact and mitigation}
|
|
63
|
+
|
|
64
|
+
## Recommendations for Planning
|
|
65
|
+
1. {Recommendation 1}
|
|
66
|
+
2. {Recommendation 2}
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
## Discovery Levels
|
|
70
|
+
|
|
71
|
+
| Level | Time | Use When |
|
|
72
|
+
|-------|------|----------|
|
|
73
|
+
| 1 | 2-5 min | Single known library, confirming syntax |
|
|
74
|
+
| 2 | 15-30 min | Choosing between options, new integration |
|
|
75
|
+
| 3 | 1+ hour | Architectural decision, novel problem |
|
|
@@ -0,0 +1,103 @@
|
|
|
1
|
+
# Summary Template
|
|
2
|
+
|
|
3
|
+
Template for `.gsd/phases/{N}/{plan}-SUMMARY.md` — execution summary after plan completion.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## File Template
|
|
8
|
+
|
|
9
|
+
```markdown
|
|
10
|
+
---
|
|
11
|
+
phase: {N}
|
|
12
|
+
plan: {M}
|
|
13
|
+
completed_at: [ISO timestamp]
|
|
14
|
+
duration_minutes: {N}
|
|
15
|
+
status: complete | partial | failed
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
# Summary: {Plan Name}
|
|
19
|
+
|
|
20
|
+
## Results
|
|
21
|
+
|
|
22
|
+
- **Tasks:** {N}/{M} completed
|
|
23
|
+
- **Commits:** {N}
|
|
24
|
+
- **Verification:** {passed | failed}
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## Tasks Completed
|
|
29
|
+
|
|
30
|
+
| Task | Description | Commit | Status |
|
|
31
|
+
|------|-------------|--------|--------|
|
|
32
|
+
| 1 | {task name} | {hash} | ✅ Complete |
|
|
33
|
+
| 2 | {task name} | {hash} | ✅ Complete |
|
|
34
|
+
| 3 | {task name} | — | ❌ Blocked |
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
## Files Changed
|
|
39
|
+
|
|
40
|
+
| File | Change Type | Description |
|
|
41
|
+
|------|-------------|-------------|
|
|
42
|
+
| {path} | Created | {what it does} |
|
|
43
|
+
| {path} | Modified | {what changed} |
|
|
44
|
+
| {path} | Deleted | {why removed} |
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## Deviations Applied
|
|
49
|
+
|
|
50
|
+
{If none: "None — executed as planned."}
|
|
51
|
+
|
|
52
|
+
### Rule 1 — Bug Fixes
|
|
53
|
+
- {description of bug fixed}
|
|
54
|
+
|
|
55
|
+
### Rule 2 — Missing Critical
|
|
56
|
+
- {description of functionality added}
|
|
57
|
+
|
|
58
|
+
### Rule 3 — Blocking Issues
|
|
59
|
+
- {description of blocker fixed}
|
|
60
|
+
|
|
61
|
+
---
|
|
62
|
+
|
|
63
|
+
## Verification
|
|
64
|
+
|
|
65
|
+
| Check | Status | Evidence |
|
|
66
|
+
|-------|--------|----------|
|
|
67
|
+
| {verification 1} | ✅ Pass | {command/output} |
|
|
68
|
+
| {verification 2} | ✅ Pass | {command/output} |
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
## Notes
|
|
73
|
+
|
|
74
|
+
{Any observations, concerns, or recommendations for future phases}
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
## Metadata
|
|
79
|
+
|
|
80
|
+
- **Started:** {timestamp}
|
|
81
|
+
- **Completed:** {timestamp}
|
|
82
|
+
- **Duration:** {N} minutes
|
|
83
|
+
- **Context Usage:** ~{N}%
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
## Guidelines
|
|
89
|
+
|
|
90
|
+
**Create SUMMARY.md:**
|
|
91
|
+
- After each plan completes
|
|
92
|
+
- Before moving to next plan
|
|
93
|
+
- Even if plan failed (document what happened)
|
|
94
|
+
|
|
95
|
+
**Include:**
|
|
96
|
+
- All commits with hashes
|
|
97
|
+
- All deviations (never hide these)
|
|
98
|
+
- Verification results with evidence
|
|
99
|
+
|
|
100
|
+
**Keep it factual:**
|
|
101
|
+
- No opinions
|
|
102
|
+
- Just what happened
|
|
103
|
+
- Evidence over claims
|