specflow-cc 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/CHANGELOG.md +73 -0
- package/LICENSE +21 -0
- package/README.md +246 -0
- package/agents/impl-reviewer.md +271 -0
- package/agents/spec-auditor.md +196 -0
- package/agents/spec-creator.md +155 -0
- package/agents/spec-executor.md +235 -0
- package/agents/spec-reviser.md +184 -0
- package/agents/spec-splitter.md +197 -0
- package/bin/install.js +398 -0
- package/commands/sf/audit.md +210 -0
- package/commands/sf/deps.md +234 -0
- package/commands/sf/done.md +271 -0
- package/commands/sf/fix.md +272 -0
- package/commands/sf/help.md +263 -0
- package/commands/sf/history.md +268 -0
- package/commands/sf/init.md +217 -0
- package/commands/sf/list.md +127 -0
- package/commands/sf/metrics.md +319 -0
- package/commands/sf/new.md +171 -0
- package/commands/sf/next.md +182 -0
- package/commands/sf/pause.md +211 -0
- package/commands/sf/plan.md +210 -0
- package/commands/sf/priority.md +198 -0
- package/commands/sf/resume.md +248 -0
- package/commands/sf/review.md +258 -0
- package/commands/sf/revise.md +232 -0
- package/commands/sf/run.md +265 -0
- package/commands/sf/show.md +203 -0
- package/commands/sf/split.md +341 -0
- package/commands/sf/status.md +170 -0
- package/commands/sf/todo.md +130 -0
- package/commands/sf/todos.md +133 -0
- package/hooks/statusline.js +69 -0
- package/package.json +37 -0
- package/templates/audit.md +61 -0
- package/templates/project.md +39 -0
- package/templates/spec.md +59 -0
- package/templates/state.md +32 -0
- package/templates/todo.md +15 -0
|
@@ -0,0 +1,272 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: sf:fix
|
|
3
|
+
description: Fix implementation based on review feedback
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- Read
|
|
6
|
+
- Write
|
|
7
|
+
- Edit
|
|
8
|
+
- Bash
|
|
9
|
+
- Glob
|
|
10
|
+
- Grep
|
|
11
|
+
- Task
|
|
12
|
+
- AskUserQuestion
|
|
13
|
+
---
|
|
14
|
+
|
|
15
|
+
<purpose>
|
|
16
|
+
Fix the implementation based on review feedback. Can apply all fixes, specific numbered items, or custom fixes described by user. Creates atomic commits for each fix.
|
|
17
|
+
</purpose>
|
|
18
|
+
|
|
19
|
+
<context>
|
|
20
|
+
@.specflow/STATE.md
|
|
21
|
+
@.specflow/PROJECT.md
|
|
22
|
+
@~/.claude/specflow-cc/agents/spec-executor.md
|
|
23
|
+
</context>
|
|
24
|
+
|
|
25
|
+
<workflow>
|
|
26
|
+
|
|
27
|
+
## Step 1: Verify Initialization
|
|
28
|
+
|
|
29
|
+
```bash
|
|
30
|
+
[ -d .specflow ] && echo "OK" || echo "NOT_INITIALIZED"
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
**If NOT_INITIALIZED:**
|
|
34
|
+
```
|
|
35
|
+
SpecFlow not initialized.
|
|
36
|
+
|
|
37
|
+
Run `/sf init` first.
|
|
38
|
+
```
|
|
39
|
+
Exit.
|
|
40
|
+
|
|
41
|
+
## Step 2: Get Active Specification
|
|
42
|
+
|
|
43
|
+
Read `.specflow/STATE.md` and extract Active Specification.
|
|
44
|
+
|
|
45
|
+
**If no active specification:**
|
|
46
|
+
```
|
|
47
|
+
No active specification to fix.
|
|
48
|
+
|
|
49
|
+
Run `/sf new "task description"` to create one.
|
|
50
|
+
```
|
|
51
|
+
Exit.
|
|
52
|
+
|
|
53
|
+
## Step 3: Load Specification
|
|
54
|
+
|
|
55
|
+
Read the active spec file: `.specflow/specs/SPEC-XXX.md`
|
|
56
|
+
|
|
57
|
+
**If status is not 'review':**
|
|
58
|
+
```
|
|
59
|
+
Specification SPEC-XXX is not in review status (status: {status}).
|
|
60
|
+
|
|
61
|
+
{If not yet run:}
|
|
62
|
+
Run `/sf run` first to implement the specification.
|
|
63
|
+
|
|
64
|
+
{If already done:}
|
|
65
|
+
Specification already completed.
|
|
66
|
+
```
|
|
67
|
+
Exit.
|
|
68
|
+
|
|
69
|
+
## Step 4: Extract Latest Review
|
|
70
|
+
|
|
71
|
+
Find the most recent "Review v[N]" section in Review History.
|
|
72
|
+
|
|
73
|
+
**If no review exists:**
|
|
74
|
+
```
|
|
75
|
+
Specification SPEC-XXX has no review history.
|
|
76
|
+
|
|
77
|
+
Run `/sf review` first to get feedback.
|
|
78
|
+
```
|
|
79
|
+
Exit.
|
|
80
|
+
|
|
81
|
+
## Step 5: Parse Arguments
|
|
82
|
+
|
|
83
|
+
| Argument | Action |
|
|
84
|
+
|----------|--------|
|
|
85
|
+
| (none) | Interactive mode — show issues, ask what to fix |
|
|
86
|
+
| "all" | Apply all critical AND major AND minor fixes |
|
|
87
|
+
| "1,2,3" | Apply only numbered items |
|
|
88
|
+
| "..." | Treat as custom fix instructions |
|
|
89
|
+
|
|
90
|
+
### If Interactive Mode (no arguments):
|
|
91
|
+
|
|
92
|
+
Display review findings:
|
|
93
|
+
|
|
94
|
+
```
|
|
95
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
96
|
+
FIX: SPEC-XXX
|
|
97
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
98
|
+
|
|
99
|
+
Last review (v{N}) found:
|
|
100
|
+
|
|
101
|
+
**Critical:**
|
|
102
|
+
1. {Issue} — `path/file.ts:line`
|
|
103
|
+
|
|
104
|
+
**Major:**
|
|
105
|
+
2. {Issue} — `path/file.ts:line`
|
|
106
|
+
|
|
107
|
+
**Minor:**
|
|
108
|
+
3. {Issue}
|
|
109
|
+
|
|
110
|
+
---
|
|
111
|
+
|
|
112
|
+
What to fix?
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
Use AskUserQuestion with options:
|
|
116
|
+
- "Fix all issues" → treat as "all"
|
|
117
|
+
- "Fix critical and major only (1, 2)" → treat as "1,2"
|
|
118
|
+
- "Custom selection" → ask for numbers or description
|
|
119
|
+
|
|
120
|
+
## Step 6: Apply Fixes
|
|
121
|
+
|
|
122
|
+
For each issue to fix:
|
|
123
|
+
|
|
124
|
+
### 6.1 Locate
|
|
125
|
+
|
|
126
|
+
Find the file and location mentioned.
|
|
127
|
+
|
|
128
|
+
### 6.2 Fix
|
|
129
|
+
|
|
130
|
+
Apply the fix following:
|
|
131
|
+
- The reviewer's suggestion
|
|
132
|
+
- Project patterns from PROJECT.md
|
|
133
|
+
- Specification requirements
|
|
134
|
+
|
|
135
|
+
### 6.3 Commit
|
|
136
|
+
|
|
137
|
+
Create atomic commit:
|
|
138
|
+
|
|
139
|
+
```bash
|
|
140
|
+
git add <files>
|
|
141
|
+
git commit -m "fix(sf-XXX): {brief description}
|
|
142
|
+
|
|
143
|
+
- Fixed: {issue description}
|
|
144
|
+
"
|
|
145
|
+
```
|
|
146
|
+
|
|
147
|
+
## Step 7: Record Fix Response
|
|
148
|
+
|
|
149
|
+
Append to Review History:
|
|
150
|
+
|
|
151
|
+
```markdown
|
|
152
|
+
### Fix Response v[N] ([date] [time])
|
|
153
|
+
**Applied:** {scope description}
|
|
154
|
+
|
|
155
|
+
**Fixes:**
|
|
156
|
+
1. [✓/✗] {Issue} — {what was done}
|
|
157
|
+
- Commit: {hash}
|
|
158
|
+
2. [✓/✗] {Issue} — {what was done}
|
|
159
|
+
- Commit: {hash}
|
|
160
|
+
|
|
161
|
+
{If any skipped:}
|
|
162
|
+
**Skipped:** {reason}
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
## Step 8: Update STATE.md
|
|
166
|
+
|
|
167
|
+
- Status → "review" (ready for re-review)
|
|
168
|
+
- Next Step → "/sf review"
|
|
169
|
+
|
|
170
|
+
## Step 9: Display Result
|
|
171
|
+
|
|
172
|
+
```
|
|
173
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
174
|
+
FIXES APPLIED
|
|
175
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
176
|
+
|
|
177
|
+
**Specification:** SPEC-XXX
|
|
178
|
+
**Review:** v{N} → Fix Response v{N}
|
|
179
|
+
|
|
180
|
+
### Fixes Applied
|
|
181
|
+
|
|
182
|
+
1. [✓] {Issue} — {what was done}
|
|
183
|
+
- Commit: {hash}
|
|
184
|
+
2. [✓] {Issue} — {what was done}
|
|
185
|
+
- Commit: {hash}
|
|
186
|
+
|
|
187
|
+
{If any skipped:}
|
|
188
|
+
### Skipped
|
|
189
|
+
|
|
190
|
+
3. [✗] {Issue} — {reason}
|
|
191
|
+
|
|
192
|
+
---
|
|
193
|
+
|
|
194
|
+
## Next Step
|
|
195
|
+
|
|
196
|
+
`/sf review` — re-review to verify fixes
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
</workflow>
|
|
200
|
+
|
|
201
|
+
<fallback>
|
|
202
|
+
|
|
203
|
+
**If complex fixes needed**, spawn executor agent in fix mode:
|
|
204
|
+
|
|
205
|
+
```
|
|
206
|
+
Task(prompt="
|
|
207
|
+
<specification>
|
|
208
|
+
@.specflow/specs/SPEC-XXX.md
|
|
209
|
+
</specification>
|
|
210
|
+
|
|
211
|
+
<project_context>
|
|
212
|
+
@.specflow/PROJECT.md
|
|
213
|
+
</project_context>
|
|
214
|
+
|
|
215
|
+
<fix_scope>
|
|
216
|
+
{Parsed scope: "all", "1,2", or custom instructions}
|
|
217
|
+
</fix_scope>
|
|
218
|
+
|
|
219
|
+
<review_findings>
|
|
220
|
+
{Latest review findings from spec}
|
|
221
|
+
</review_findings>
|
|
222
|
+
|
|
223
|
+
Fix the implementation issues identified in the review.
|
|
224
|
+
Create atomic commits for each fix.
|
|
225
|
+
Record Fix Response in Review History.
|
|
226
|
+
", subagent_type="sf-spec-executor", description="Fix implementation")
|
|
227
|
+
```
|
|
228
|
+
|
|
229
|
+
## Inline Fix (for simple fixes)
|
|
230
|
+
|
|
231
|
+
### Locate Issues
|
|
232
|
+
|
|
233
|
+
Parse review findings with file paths and line numbers.
|
|
234
|
+
|
|
235
|
+
### Apply Each Fix
|
|
236
|
+
|
|
237
|
+
1. Read the file
|
|
238
|
+
2. Make the correction
|
|
239
|
+
3. Verify fix works
|
|
240
|
+
4. Commit:
|
|
241
|
+
```bash
|
|
242
|
+
git add <file>
|
|
243
|
+
git commit -m "fix(sf-XXX): {description}"
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
### Record Response
|
|
247
|
+
|
|
248
|
+
Get fix response version:
|
|
249
|
+
```bash
|
|
250
|
+
FIX_COUNT=$(grep -c "### Fix Response v" .specflow/specs/SPEC-XXX.md 2>/dev/null || echo 0)
|
|
251
|
+
NEXT_VERSION=$((FIX_COUNT + 1))
|
|
252
|
+
```
|
|
253
|
+
|
|
254
|
+
Append to Review History.
|
|
255
|
+
|
|
256
|
+
### Update STATE.md
|
|
257
|
+
|
|
258
|
+
- Status → "review"
|
|
259
|
+
- Next Step → "/sf review"
|
|
260
|
+
|
|
261
|
+
</fallback>
|
|
262
|
+
|
|
263
|
+
<success_criteria>
|
|
264
|
+
- [ ] Active specification identified
|
|
265
|
+
- [ ] Latest review parsed
|
|
266
|
+
- [ ] Fix scope determined (all/specific/custom)
|
|
267
|
+
- [ ] All requested fixes applied
|
|
268
|
+
- [ ] Atomic commits created for each fix
|
|
269
|
+
- [ ] Fix Response recorded in Review History
|
|
270
|
+
- [ ] STATE.md updated
|
|
271
|
+
- [ ] Clear summary of fixes shown
|
|
272
|
+
</success_criteria>
|
|
@@ -0,0 +1,263 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: sf:help
|
|
3
|
+
description: Show SpecFlow help and command reference
|
|
4
|
+
allowed-tools:
|
|
5
|
+
- Read
|
|
6
|
+
- Glob
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
<purpose>
|
|
10
|
+
Display comprehensive help for SpecFlow commands. Without arguments, shows an overview of all commands grouped by category. With a command name, shows detailed help including examples and related commands.
|
|
11
|
+
</purpose>
|
|
12
|
+
|
|
13
|
+
<context>
|
|
14
|
+
@~/.claude/specflow-cc/commands/sf/*.md
|
|
15
|
+
</context>
|
|
16
|
+
|
|
17
|
+
<arguments>
|
|
18
|
+
- `[command]` — Command name to get detailed help for (e.g., `new`, `audit`). Optional — shows overview if omitted.
|
|
19
|
+
</arguments>
|
|
20
|
+
|
|
21
|
+
<workflow>
|
|
22
|
+
|
|
23
|
+
## Step 1: Check for Arguments
|
|
24
|
+
|
|
25
|
+
**If command argument provided:** Go to Step 2a (Detailed Help)
|
|
26
|
+
**If no arguments:** Go to Step 2b (Overview)
|
|
27
|
+
|
|
28
|
+
## Step 2a: Detailed Command Help
|
|
29
|
+
|
|
30
|
+
### Validate Command
|
|
31
|
+
|
|
32
|
+
Check if command exists:
|
|
33
|
+
```bash
|
|
34
|
+
[ -f ~/.claude/specflow-cc/commands/sf/{command}.md ] && echo "FOUND" || echo "NOT_FOUND"
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
**If NOT_FOUND:**
|
|
38
|
+
```
|
|
39
|
+
Unknown command: {command}
|
|
40
|
+
|
|
41
|
+
Run `/sf help` for available commands.
|
|
42
|
+
```
|
|
43
|
+
Exit.
|
|
44
|
+
|
|
45
|
+
### Display Detailed Help
|
|
46
|
+
|
|
47
|
+
Read the command file and extract:
|
|
48
|
+
- Name and description from frontmatter
|
|
49
|
+
- Purpose from `<purpose>` section
|
|
50
|
+
- Arguments from `<arguments>` section
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
54
|
+
/sf {command}
|
|
55
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
56
|
+
|
|
57
|
+
{Description from frontmatter}
|
|
58
|
+
|
|
59
|
+
## Usage
|
|
60
|
+
|
|
61
|
+
```
|
|
62
|
+
/sf {command} {arguments syntax}
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
## Description
|
|
66
|
+
|
|
67
|
+
{Purpose section content, summarized}
|
|
68
|
+
|
|
69
|
+
## Arguments
|
|
70
|
+
|
|
71
|
+
{Arguments section content}
|
|
72
|
+
|
|
73
|
+
## Examples
|
|
74
|
+
|
|
75
|
+
{Generate contextual examples based on command}
|
|
76
|
+
|
|
77
|
+
## Related Commands
|
|
78
|
+
|
|
79
|
+
{List 2-4 related commands with brief descriptions}
|
|
80
|
+
|
|
81
|
+
## See Also
|
|
82
|
+
|
|
83
|
+
- DESIGN.md section {relevant section}
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
### Command-Specific Examples
|
|
87
|
+
|
|
88
|
+
**For `/sf new`:**
|
|
89
|
+
```
|
|
90
|
+
## Examples
|
|
91
|
+
|
|
92
|
+
```
|
|
93
|
+
/sf new "Add user authentication with JWT"
|
|
94
|
+
/sf new "Fix pagination bug in user list"
|
|
95
|
+
/sf new "Refactor UserService to use repository pattern"
|
|
96
|
+
/sf new # Interactive mode
|
|
97
|
+
```
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
**For `/sf audit`:**
|
|
101
|
+
```
|
|
102
|
+
## Examples
|
|
103
|
+
|
|
104
|
+
```
|
|
105
|
+
/sf audit # Audit active specification
|
|
106
|
+
/sf audit SPEC-003 # Audit specific specification
|
|
107
|
+
```
|
|
108
|
+
```
|
|
109
|
+
|
|
110
|
+
**For `/sf run`:**
|
|
111
|
+
```
|
|
112
|
+
## Examples
|
|
113
|
+
|
|
114
|
+
```
|
|
115
|
+
/sf run # Run active specification
|
|
116
|
+
/sf run SPEC-003 # Run specific specification
|
|
117
|
+
```
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
**For `/sf revise`:**
|
|
121
|
+
```
|
|
122
|
+
## Examples
|
|
123
|
+
|
|
124
|
+
```
|
|
125
|
+
/sf revise # Interactive — shows audit comments
|
|
126
|
+
/sf revise all # Apply all audit comments
|
|
127
|
+
/sf revise 1,2 # Apply only comments 1 and 2
|
|
128
|
+
/sf revise "add error handling, ignore item 3"
|
|
129
|
+
```
|
|
130
|
+
```
|
|
131
|
+
|
|
132
|
+
**For `/sf split`:**
|
|
133
|
+
```
|
|
134
|
+
## Examples
|
|
135
|
+
|
|
136
|
+
```
|
|
137
|
+
/sf split # Split active specification
|
|
138
|
+
/sf split SPEC-001 # Split specific specification
|
|
139
|
+
```
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
**For `/sf todo`:**
|
|
143
|
+
```
|
|
144
|
+
## Examples
|
|
145
|
+
|
|
146
|
+
```
|
|
147
|
+
/sf todo "Add caching layer for API"
|
|
148
|
+
/sf todo "Research WebSocket alternatives"
|
|
149
|
+
/sf todo "Refactor authentication flow"
|
|
150
|
+
```
|
|
151
|
+
```
|
|
152
|
+
|
|
153
|
+
Exit.
|
|
154
|
+
|
|
155
|
+
## Step 2b: Overview Help
|
|
156
|
+
|
|
157
|
+
Display full command reference:
|
|
158
|
+
|
|
159
|
+
```
|
|
160
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
161
|
+
SPECFLOW HELP
|
|
162
|
+
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
|
|
163
|
+
|
|
164
|
+
**SpecFlow** — Spec-driven development for Claude Code
|
|
165
|
+
|
|
166
|
+
Workflow: Spec → Audit → Revise → Run → Review → Fix → Done
|
|
167
|
+
|
|
168
|
+
---
|
|
169
|
+
|
|
170
|
+
## Core Workflow
|
|
171
|
+
|
|
172
|
+
| Command | Description |
|
|
173
|
+
|--------------|-----------------------------------------|
|
|
174
|
+
| /sf init | Initialize project, analyze codebase |
|
|
175
|
+
| /sf new | Create specification from task |
|
|
176
|
+
| /sf audit | Audit specification (fresh context) |
|
|
177
|
+
| /sf revise | Revise spec based on audit feedback |
|
|
178
|
+
| /sf run | Execute specification |
|
|
179
|
+
| /sf review | Review implementation (fresh context) |
|
|
180
|
+
| /sf fix | Fix implementation based on review |
|
|
181
|
+
| /sf done | Finalize, commit, and archive |
|
|
182
|
+
|
|
183
|
+
## Navigation
|
|
184
|
+
|
|
185
|
+
| Command | Description |
|
|
186
|
+
|--------------|-----------------------------------------|
|
|
187
|
+
| /sf status | Show current state and next step |
|
|
188
|
+
| /sf list | List all specifications |
|
|
189
|
+
| /sf show | Show specification details |
|
|
190
|
+
| /sf next | Work on highest priority task |
|
|
191
|
+
|
|
192
|
+
## To-Do
|
|
193
|
+
|
|
194
|
+
| Command | Description |
|
|
195
|
+
|--------------|-----------------------------------------|
|
|
196
|
+
| /sf todo | Add idea to backlog |
|
|
197
|
+
| /sf todos | List all to-do items |
|
|
198
|
+
| /sf plan | Convert to-do to specification |
|
|
199
|
+
| /sf priority | Change to-do priorities |
|
|
200
|
+
|
|
201
|
+
## Decomposition
|
|
202
|
+
|
|
203
|
+
| Command | Description |
|
|
204
|
+
|--------------|-----------------------------------------|
|
|
205
|
+
| /sf split | Split large spec into sub-specs |
|
|
206
|
+
| /sf deps | Show dependency graph |
|
|
207
|
+
|
|
208
|
+
## Sessions
|
|
209
|
+
|
|
210
|
+
| Command | Description |
|
|
211
|
+
|--------------|-----------------------------------------|
|
|
212
|
+
| /sf pause | Save session context for later |
|
|
213
|
+
| /sf resume | Restore previous session context |
|
|
214
|
+
|
|
215
|
+
## Utilities
|
|
216
|
+
|
|
217
|
+
| Command | Description |
|
|
218
|
+
|--------------|-----------------------------------------|
|
|
219
|
+
| /sf help | This help (or detailed: /sf help new) |
|
|
220
|
+
| /sf history | View completed specifications |
|
|
221
|
+
| /sf metrics | Project statistics and insights |
|
|
222
|
+
|
|
223
|
+
---
|
|
224
|
+
|
|
225
|
+
## Quick Start
|
|
226
|
+
|
|
227
|
+
1. `/sf init` — Initialize project (once)
|
|
228
|
+
2. `/sf new "task"` — Create specification
|
|
229
|
+
3. `/sf audit` — Audit the spec
|
|
230
|
+
4. `/sf run` — Implement
|
|
231
|
+
5. `/sf review` — Review implementation
|
|
232
|
+
6. `/sf done` — Complete and archive
|
|
233
|
+
|
|
234
|
+
## Typical Session
|
|
235
|
+
|
|
236
|
+
```
|
|
237
|
+
/sf status # Where am I?
|
|
238
|
+
/sf next # What should I work on?
|
|
239
|
+
/sf audit # Audit current spec
|
|
240
|
+
/sf revise all # Apply audit feedback
|
|
241
|
+
/sf run # Implement
|
|
242
|
+
/sf review # Review implementation
|
|
243
|
+
/sf done # Complete
|
|
244
|
+
```
|
|
245
|
+
|
|
246
|
+
---
|
|
247
|
+
|
|
248
|
+
**Detailed help:** `/sf help <command>`
|
|
249
|
+
|
|
250
|
+
**Documentation:** See DESIGN.md for full specification
|
|
251
|
+
```
|
|
252
|
+
|
|
253
|
+
</workflow>
|
|
254
|
+
|
|
255
|
+
<success_criteria>
|
|
256
|
+
- [ ] Command argument parsed correctly
|
|
257
|
+
- [ ] Unknown commands handled gracefully
|
|
258
|
+
- [ ] Detailed help shows usage, examples, related commands
|
|
259
|
+
- [ ] Overview shows all commands grouped by category
|
|
260
|
+
- [ ] Quick start guide included
|
|
261
|
+
- [ ] Typical session example provided
|
|
262
|
+
- [ ] Clear formatting with tables
|
|
263
|
+
</success_criteria>
|