specflow-cc 1.0.0 → 1.2.0

package/commands/sf/new.md

@@ -34,7 +34,7 @@ Create a new specification from a task description. Asks critical questions if n
 ```
 SpecFlow not initialized.
 
-Run `/sf init` first.
+Run `/sf:init` first.
 ```
 Exit.
 
@@ -102,14 +102,14 @@ The agent will:
 
 ## Next Step
 
-`/sf audit` — audit specification before implementation
+`/sf:audit` — audit specification before implementation
 
 {If complexity is large:}
 
 ### Warning
 
 Specification is large (>150k tokens estimated).
-Consider `/sf split SPEC-XXX` to decompose into smaller specs.
+Consider `/sf:split SPEC-XXX` to decompose into smaller specs.
 ```
 
 </workflow>
@@ -153,7 +153,7 @@ Create `.specflow/specs/SPEC-XXX.md` with:
 
 - **Active Specification:** SPEC-XXX
 - **Status:** drafting
-- **Next Step:** /sf audit
+- **Next Step:** /sf:audit
 ```
 
 Add to Queue table.
@@ -167,5 +167,5 @@ Add to Queue table.
 - [ ] Complexity estimated (small/medium/large)
 - [ ] Assumptions documented
 - [ ] STATE.md updated with new spec
-- [ ] User knows next step is /sf audit
+- [ ] User knows next step is /sf:audit
 </success_criteria>

package/commands/sf/next.md

@@ -28,7 +28,7 @@ Find the highest priority specification that needs action, set it as active in S
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -47,8 +47,8 @@ ls -1 .specflow/specs/SPEC-*.md 2>/dev/null
 No specifications ready for work.
 
 **Options:**
-- `/sf new "description"` — create new specification
-- `/sf todos` — view idea backlog
+- `/sf:new "description"` — create new specification
+- `/sf:todos` — view idea backlog
 ```
 Exit.
 
@@ -91,9 +91,9 @@ Choose spec with highest score.
 All specifications are either completed or blocked.
 
 **Options:**
-- `/sf new "description"` — create new specification
-- `/sf todos` — view idea backlog
-- `/sf list` — see all specifications
+- `/sf:new "description"` — create new specification
+- `/sf:todos` — view idea backlog
+- `/sf:list` — see all specifications
 ```
 Exit.
 
@@ -108,12 +108,12 @@ Update `.specflow/STATE.md`:
 
 | Status | Recommended Command | Description |
 |--------|---------------------|-------------|
-| draft | `/sf audit` | Audit specification |
+| draft | `/sf:audit` | Audit specification |
 | auditing | Continue audit | Complete the audit |
-| revision_requested | `/sf revise` | Address audit comments |
-| audited | `/sf run` | Implement specification |
-| running | Continue or `/sf review` | Complete implementation |
-| review | `/sf fix` or `/sf done` | Address review or finalize |
+| revision_requested | `/sf:revise` | Address audit comments |
+| audited | `/sf:run` | Implement specification |
+| running | Continue or `/sf:review` | Complete implementation |
+| review | `/sf:fix` or `/sf:done` | Address review or finalize |
 
 ## Step 7: Display Next Task
 
@@ -156,7 +156,7 @@ From {audit/review} v{N}:
 
 **If status is revision_requested:**
 ```
-**Tip:** Review audit comments with `/sf show {ID}` before revising.
+**Tip:** Review audit comments with `/sf:show {ID}` before revising.
 ```
 
 **If status is review:**
@@ -166,7 +166,7 @@ From {audit/review} v{N}:
 
 **If complexity is large:**
 ```
-**Tip:** Consider `/sf split {ID}` to break into smaller specs.
+**Tip:** Consider `/sf:split {ID}` to break into smaller specs.
 ```
 
 </workflow>

package/commands/sf/pause.md

@@ -29,7 +29,7 @@ Save the current work context to enable seamless resumption later. Creates a pau
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -192,7 +192,7 @@ Under Current Position, add:
 
 **Session saved successfully.**
 
-Resume with: `/sf resume`
+Resume with: `/sf:resume`
 ```
 
 </workflow>

package/commands/sf/plan.md

@@ -23,7 +23,7 @@ Convert a to-do item from the backlog into a full specification. Reuses the spec
 </context>
 
 <arguments>
-- `[ID or #]` — Optional. Either TODO-XXX ID or list number from `/sf todos`. If omitted, shows todos and prompts for selection.
+- `[ID or #]` — Optional. Either TODO-XXX ID or list number from `/sf:todos`. If omitted, shows todos and prompts for selection.
 </arguments>
 
 <workflow>
@@ -38,7 +38,7 @@ Convert a to-do item from the backlog into a full specification. Reuses the spec
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -52,7 +52,7 @@ Exit.
 ```
 No to-do items found.
 
-Add ideas first with `/sf todo "your idea"`.
+Add ideas first with `/sf:todo "your idea"`.
 ```
 Exit.
 
@@ -95,7 +95,7 @@ Read the selected todo:
 ```
 Todo "{arg}" not found.
 
-Use `/sf todos` to see available items.
+Use `/sf:todos` to see available items.
 ```
 Exit.
 
@@ -161,14 +161,14 @@ Update `*Last updated:` timestamp.
 
 ## Next Step
 
-`/sf audit` — audit specification before implementation
+`/sf:audit` — audit specification before implementation
 
 {If complexity is large:}
 
 ### Warning
 
 Specification is large (>150k tokens estimated).
-Consider `/sf split SPEC-{YYY}` to decompose.
+Consider `/sf:split SPEC-{YYY}` to decompose.
 ```
 
 </workflow>
@@ -183,9 +183,9 @@ Consider `/sf split SPEC-{YYY}` to decompose.
 
 Read from TODO.md.
 
-### Create Spec (same as /sf new)
+### Create Spec (same as /sf:new)
 
-Use `/sf new "{todo description}"` logic:
+Use `/sf:new "{todo description}"` logic:
 1. Generate SPEC-XXX ID
 2. Create spec with todo context
 3. Set priority from todo

package/commands/sf/priority.md

@@ -30,7 +30,7 @@ Interactively prioritize specifications and to-do items. Allows reordering, sett
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -179,7 +179,7 @@ After changes:
 
 ---
 
-Use `/sf next` to work on highest priority task.
+Use `/sf:next` to work on highest priority task.
 ```
 
 </workflow>

package/commands/sf/resume.md

@@ -29,7 +29,7 @@ Restore the work context from the last pause. Reads the pause file, displays ful
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -48,9 +48,9 @@ ls -1 .specflow/sessions/PAUSE-*.md 2>/dev/null | sort -r | head -1
 No paused session found.
 
 **Options:**
-- `/sf status` — view current state
-- `/sf next` — find next task to work on
-- `/sf list` — see all specifications
+- `/sf:status` — view current state
+- `/sf:next` — find next task to work on
+- `/sf:list` — see all specifications
 ```
 Exit.
 
@@ -228,7 +228,7 @@ Based on your notes and progress:
 If more than 5 pause files exist, suggest cleanup:
 
 ```
-**Note:** {N} old pause files in sessions/. Run `/sf history` to review or clean up.
+**Note:** {N} old pause files in sessions/. Run `/sf:history` to review or clean up.
 ```
 
 </workflow>

package/commands/sf/review.md

@@ -32,7 +32,7 @@ Review the implementation of the active specification in a fresh context. The re
 ```
 SpecFlow not initialized.
 
-Run `/sf init` first.
+Run `/sf:init` first.
 ```
 Exit.
 
@@ -44,7 +44,7 @@ Read `.specflow/STATE.md` and extract Active Specification.
 ```
 No active specification to review.
 
-Run `/sf new "task description"` to create one.
+Run `/sf:new "task description"` to create one.
 ```
 Exit.
 
@@ -57,10 +57,10 @@ Read the active spec file: `.specflow/specs/SPEC-XXX.md`
 Specification SPEC-XXX is not ready for review (status: {status}).
 
 {If status is draft/auditing/revision_requested:}
-Run `/sf run` first to implement the specification.
+Run `/sf:run` first to implement the specification.
 
 {If status is done:}
-Specification already completed. Use `/sf history` to view archived specs.
+Specification already completed. Use `/sf:history` to view archived specs.
 ```
 Exit.
 
@@ -72,7 +72,7 @@ Check that Execution Summary exists in spec:
 ```
 No implementation found for SPEC-XXX.
 
-Run `/sf run` to execute the specification first.
+Run `/sf:run` to execute the specification first.
 ```
 Exit.
 
@@ -108,7 +108,7 @@ The agent will:
 
 ## Step 7: Display Result
 
-### If APPROVED:
+### If APPROVED (no minor issues):
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -133,7 +133,38 @@ The agent will:
 
 ## Next Step
 
-`/sf done` — finalize and archive specification
+`/sf:done` — finalize and archive specification
+```
+
+### If APPROVED (with minor suggestions):
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ REVIEW PASSED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Specification:** SPEC-XXX
+**Result:** APPROVED
+
+### Verified
+
+- [✓] All acceptance criteria met
+- [✓] All files created
+- [✓] All deletions performed
+- [✓] Code quality acceptable
+
+### Minor Suggestions (Optional)
+
+1. {Suggestion 1}
+2. {Suggestion 2}
+
+---
+
+## Next Steps
+
+Choose one:
+• `/sf:done` — finalize and archive as-is
+• `/sf:fix` — apply minor suggestions first ({N} items)
 ```
 
 ### If CHANGES_REQUESTED:
@@ -171,12 +202,12 @@ The agent will:
 
 ## Next Step
 
-`/sf fix` — address the issues
+`/sf:fix` — address the issues
 
 Options:
-- `/sf fix all` — apply all fixes
-- `/sf fix 1,2` — fix specific issues
-- `/sf fix [instructions]` — custom fixes
+- `/sf:fix all` — apply all fixes
+- `/sf:fix 1,2` — fix specific issues
+- `/sf:fix [instructions]` — custom fixes
 ```
 
 </workflow>
@@ -239,8 +270,8 @@ Append Review History to spec.
 
 ### Update STATE.md
 
-- If APPROVED: Status → "done", Next Step → "/sf done"
-- If CHANGES_REQUESTED: Status → "review", Next Step → "/sf fix"
+- If APPROVED: Status → "done", Next Step → "/sf:done"
+- If CHANGES_REQUESTED: Status → "review", Next Step → "/sf:fix"
 
 </fallback>
 

package/commands/sf/revise.md

@@ -33,7 +33,7 @@ Revise the active specification based on audit feedback. Can apply all comments,
 ```
 SpecFlow not initialized.
 
-Run `/sf init` first.
+Run `/sf:init` first.
 ```
 Exit.
 
@@ -45,7 +45,7 @@ Read `.specflow/STATE.md` and extract Active Specification.
 ```
 No active specification to revise.
 
-Run `/sf new "task description"` to create one.
+Run `/sf:new "task description"` to create one.
 ```
 Exit.
 
@@ -57,7 +57,7 @@ Read the active spec file: `.specflow/specs/SPEC-XXX.md`
 ```
 Specification SPEC-XXX cannot be revised (status: {status}).
 
-Use `/sf status` to see current state.
+Use `/sf:status` to see current state.
 ```
 Exit.
 
@@ -69,7 +69,7 @@ Find the most recent "Audit v[N]" section in Audit History.
 ```
 Specification SPEC-XXX has no audit history.
 
-Run `/sf audit` first to get feedback.
+Run `/sf:audit` first to get feedback.
 ```
 Exit.
 
@@ -167,7 +167,7 @@ The agent will:
 
 ## Next Step
 
-`/sf audit` — re-audit revised specification
+`/sf:audit` — re-audit revised specification
 ```
 
 </workflow>
@@ -216,7 +216,7 @@ In spec frontmatter: `status: auditing`
 
 In STATE.md:
 - Status → "auditing"
-- Next Step → "/sf audit"
+- Next Step → "/sf:audit"
 
 </fallback>
 

package/commands/sf/run.md

@@ -34,7 +34,7 @@ Execute the active specification by implementing all requirements. Creates atomi
 ```
 SpecFlow not initialized.
 
-Run `/sf init` first.
+Run `/sf:init` first.
 ```
 Exit.
 
@@ -46,7 +46,7 @@ Read `.specflow/STATE.md` and extract Active Specification.
 ```
 No active specification to execute.
 
-Run `/sf new "task description"` to create one.
+Run `/sf:new "task description"` to create one.
 ```
 Exit.
 
@@ -93,7 +93,7 @@ Continue anyway?
 
 Use AskUserQuestion with options:
 - "Yes, proceed anyway" → continue, log warning
-- "No, run audit first" → exit with `/sf audit` suggestion
+- "No, run audit first" → exit with `/sf:audit` suggestion
 
 **If user proceeds anyway:**
 Log in STATE.md Warnings table:
@@ -200,7 +200,7 @@ The agent will:
 
 ## Next Step
 
-`/sf review` — audit the implementation
+`/sf:review` — audit the implementation
 ```
 
 </workflow>
@@ -248,7 +248,7 @@ Append Execution Summary to spec.
 ### Update STATE.md
 
 - Status → "review"
-- Next Step → "/sf review"
+- Next Step → "/sf:review"
 
 </fallback>
 

package/commands/sf/scan.md

@@ -0,0 +1,164 @@
+---
+name: sf:scan
+description: Deep codebase analysis — identifies concerns, tech debt, and improvement opportunities
+argument-hint: "[--focus=concerns|quality|arch|all]"
+---
+
+<purpose>
+Perform deep analysis of the codebase to identify technical debt, code quality issues, architectural problems, and improvement opportunities. Results are saved to `.specflow/SCAN.md` for use in creating specifications.
+</purpose>
+
+<context>
+@.specflow/PROJECT.md
+@.specflow/STATE.md
+@~/.claude/specflow-cc/templates/scan.md
+@~/.claude/specflow-cc/agents/codebase-scanner.md
+</context>
+
+<workflow>
+
+## 1. Parse Arguments
+
+```
+FOCUS = $ARGUMENTS or "all"
+```
+
+Valid focus areas:
+- `concerns` — Technical debt, bugs, security issues
+- `quality` — Code quality, conventions, test coverage
+- `arch` — Architecture, structure, patterns
+- `all` — Full analysis (default)
+
+## 2. Check Prerequisites
+
+```bash
+[ -d .specflow ] && echo "INITIALIZED" || echo "NOT_INITIALIZED"
+```
+
+**If NOT_INITIALIZED:**
+```
+⚠️  Project not initialized
+
+Run /sf:init first to set up SpecFlow.
+```
+STOP.
+
+## 3. Check Existing Scan
+
+```bash
+[ -f .specflow/SCAN.md ] && echo "EXISTS" || echo "NEW"
+```
+
+**If EXISTS:**
+Ask user:
+```
+📊 Previous scan found (.specflow/SCAN.md)
+
+Options:
+1) Refresh — Run new scan (overwrites existing)
+2) View — Show existing scan results
+3) Cancel
+
+Choice?
+```
+
+## 4. Launch Scanner Agent
+
+Use the Task tool to spawn codebase-scanner agent:
+
+```
+subagent_type="sf-codebase-scanner"
+prompt="""
+Focus: {FOCUS}
+Project: {from PROJECT.md}
+
+Scan the codebase and write findings to .specflow/SCAN.md
+
+Return only confirmation when done.
+"""
+```
+
+## 5. Verify Results
+
+After agent completes:
+
+```bash
+[ -f .specflow/SCAN.md ] && wc -l .specflow/SCAN.md
+```
+
+## 6. Display Summary
+
+Read `.specflow/SCAN.md` and extract summary:
+
+```
+📊 Codebase Scan Complete
+
+Focus: {FOCUS}
+Lines analyzed: ~{estimate}
+
+┌─────────────────────────────────────────────┐
+│ Summary                                      │
+├─────────────────────────────────────────────┤
+│ Tech Debt:        {count} issues            │
+│ Quality Issues:   {count} findings          │
+│ Security:         {count} considerations    │
+│ Test Gaps:        {count} areas             │
+└─────────────────────────────────────────────┘
+
+Top Priority Issues:
+1. {issue 1}
+2. {issue 2}
+3. {issue 3}
+
+📁 Full report: .specflow/SCAN.md
+
+Next steps:
+• /sf:new "Fix: {top concern}" — Create spec for top issue
+• /sf:todo {concern} — Add to backlog for later
+```
+
+</workflow>
+
+<fallback>
+If agent cannot be spawned, perform scan directly:
+
+1. Explore codebase structure
+2. Search for TODO/FIXME comments
+3. Identify large/complex files
+4. Check test coverage gaps
+5. Look for code smells
+6. Write findings to `.specflow/SCAN.md`
+</fallback>
+
+<output_format>
+**Success:**
+```
+📊 Codebase Scan Complete
+
+[Summary table]
+[Top issues]
+[Next steps]
+```
+
+**No issues found:**
+```
+✅ Codebase scan complete — no critical concerns found
+
+Minor observations saved to .specflow/SCAN.md
+```
+
+**Error:**
+```
+❌ Scan failed: {reason}
+
+Try running manually or check .specflow/ permissions.
+```
+</output_format>
+
+<success_criteria>
+- [ ] Focus area parsed correctly
+- [ ] Scanner agent spawned (or fallback executed)
+- [ ] .specflow/SCAN.md created with findings
+- [ ] Summary displayed to user
+- [ ] Next steps provided
+</success_criteria>

package/commands/sf/show.md

@@ -31,7 +31,7 @@ Display the full content of a specification including context, task, requirement
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -47,8 +47,8 @@ Read `.specflow/STATE.md` and get Active Specification.
 ```
 No specification specified and no active specification.
 
-Use `/sf show SPEC-XXX` to view a specific spec
-or `/sf list` to see all specifications.
+Use `/sf:show SPEC-XXX` to view a specific spec
+or `/sf:list` to see all specifications.
 ```
 Exit.
 
@@ -66,7 +66,7 @@ Exit.
 ```
 Specification {ID} not found.
 
-Use `/sf list` to see available specifications.
+Use `/sf:list` to see available specifications.
 ```
 Exit.
 
@@ -101,12 +101,12 @@ Based on current status:
 
 | Status | Recommended Action |
 |--------|-------------------|
-| draft | `/sf audit` — audit specification |
-| auditing | Complete audit or `/sf revise` |
-| revision_requested | `/sf revise` — address comments |
-| audited | `/sf run` — implement specification |
-| running | Continue implementation or `/sf review` |
-| review | `/sf fix` or `/sf done` |
+| draft | `/sf:audit` — audit specification |
+| auditing | Complete audit or `/sf:revise` |
+| revision_requested | `/sf:revise` — address comments |
+| audited | `/sf:run` — implement specification |
+| running | Continue implementation or `/sf:review` |
+| review | `/sf:fix` or `/sf:done` |
 | done | No action (archived) |
 
 ## Step 7: Display Specification
@@ -174,8 +174,8 @@ Based on current status:
 ```
 This specification is complete and archived.
 
-To view active specs: `/sf list`
-To see completed history: `/sf history`
+To view active specs: `/sf:list`
+To see completed history: `/sf:history`
 ```
 
 **If spec has outstanding issues:**
@@ -186,7 +186,7 @@ From {audit/review} v{N}:
 1. {issue}
 2. {issue}
 
-Address with `/sf revise` or `/sf fix`.
+Address with `/sf:revise` or `/sf:fix`.
 ```
 
 </workflow>