specflow-cc 1.1.0 → 1.2.0

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

@@ -39,7 +39,7 @@ Valid focus areas:
 ```
 ⚠️  Project not initialized
 
-Run /sf init first to set up SpecFlow.
+Run /sf:init first to set up SpecFlow.
 ```
 STOP.
 
@@ -113,8 +113,8 @@ Top Priority Issues:
 📁 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
+• /sf:new "Fix: {top concern}" — Create spec for top issue
+• /sf:todo {concern} — Add to backlog for later
 ```
 
 </workflow>

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>

package/commands/sf/split.md

@@ -37,7 +37,7 @@ Analyze a specification's complexity and split it into smaller, manageable sub-s
 ```
 SpecFlow not initialized.
 
-Run `/sf init` first.
+Run `/sf:init` first.
 ```
 Exit.
 
@@ -52,7 +52,7 @@ Exit.
 ```
 Specification {ID} not found.
 
-Use `/sf list` to see available specifications.
+Use `/sf:list` to see available specifications.
 ```
 Exit.
 
@@ -65,8 +65,8 @@ Read active specification from `.specflow/STATE.md`:
 ```
 No specification specified and no active specification.
 
-Usage: `/sf split SPEC-001`
-   or: Set active spec with `/sf show SPEC-001`
+Usage: `/sf:split SPEC-001`
+   or: Set active spec with `/sf:show SPEC-001`
 ```
 Exit.
 
@@ -88,7 +88,7 @@ Read the specification and assess complexity:
 
 This specification is small enough to implement directly.
 
-**Next Step:** `/sf audit {ID}` — audit before implementation
+**Next Step:** `/sf:audit {ID}` — audit before implementation
 ```
 Exit.
 
@@ -241,9 +241,9 @@ Exit.
 
 ## Next Step
 
-`/sf audit {ID}a` — start with first sub-specification (no dependencies)
+`/sf:audit {ID}a` — start with first sub-specification (no dependencies)
 
-**Tip:** Use `/sf deps` to see the full dependency graph.
+**Tip:** Use `/sf:deps` to see the full dependency graph.
 ```
 
 </workflow>

package/commands/sf/status.md

@@ -28,7 +28,7 @@ Display the current SpecFlow state including active specification, queue, and re
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -67,12 +67,12 @@ Based on current status:
 
 | Status | Next Action |
 |--------|-------------|
-| idle | `/sf new "task"` — create specification |
-| drafting | `/sf audit` — audit specification |
-| revision_requested | `/sf revise` — fix issues |
-| audited | `/sf run` — implement |
-| running | Continue implementation or `/sf review` |
-| reviewing | `/sf fix` or `/sf done` |
+| idle | `/sf:new "task"` — create specification |
+| drafting | `/sf:audit` — audit specification |
+| revision_requested | `/sf:revise` — fix issues |
+| audited | `/sf:run` — implement |
+| running | Continue implementation or `/sf:review` |
+| reviewing | `/sf:fix` or `/sf:done` |
 
 ## Step 6: Display Status
 
@@ -138,17 +138,17 @@ Based on state, provide additional guidance:
 
 **If idle for long time:**
 ```
-**Tip:** Have ideas? Use `/sf todo "idea"` to capture for later.
+**Tip:** Have ideas? Use `/sf:todo "idea"` to capture for later.
 ```
 
 **If spec is large:**
 ```
-**Tip:** Consider `/sf split SPEC-XXX` to break into smaller specs.
+**Tip:** Consider `/sf:split SPEC-XXX` to break into smaller specs.
 ```
 
 **If multiple specs in queue:**
 ```
-**Tip:** Use `/sf next` to work on highest priority item.
+**Tip:** Use `/sf:next` to work on highest priority item.
 ```
 
 **If warnings present:**

package/commands/sf/todo.md

@@ -9,7 +9,7 @@ allowed-tools:
 ---
 
 <purpose>
-Add a new to-do item to the backlog. To-dos are ideas or tasks that don't need immediate specification but should be captured for later. They can later be converted to specifications with `/sf plan`.
+Add a new to-do item to the backlog. To-dos are ideas or tasks that don't need immediate specification but should be captured for later. They can later be converted to specifications with `/sf:plan`.
 </purpose>
 
 <context>
@@ -32,7 +32,7 @@ Add a new to-do item to the backlog. To-dos are ideas or tasks that don't need i
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -111,9 +111,9 @@ Also update `*Last updated:` line at the bottom.
 ---
 
 **Actions:**
-- `/sf todos` — view all to-do items
-- `/sf plan TODO-{XXX}` — convert to specification
-- `/sf priority` — set priorities
+- `/sf:todos` — view all to-do items
+- `/sf:plan TODO-{XXX}` — convert to specification
+- `/sf:priority` — set priorities
 ```
 
 </workflow>

package/commands/sf/todos.md

@@ -26,7 +26,7 @@ Display all to-do items from the backlog, sorted by priority. Shows ID, descript
 ```
 SpecFlow not initialized.
 
-Run `/sf init` to start.
+Run `/sf:init` to start.
 ```
 Exit.
 
@@ -45,7 +45,7 @@ Exit.
 No to-do items found.
 
 Add your first idea:
-`/sf todo "your idea here"`
+`/sf:todo "your idea here"`
 ```
 Exit.
 
@@ -100,10 +100,10 @@ Within same priority, sort by date (oldest first).
 ---
 
 **Actions:**
-- `/sf plan 1` — convert first item to specification
-- `/sf plan TODO-001` — convert by ID
-- `/sf priority` — change priorities
-- `/sf todo "new idea"` — add new item
+- `/sf:plan 1` — convert first item to specification
+- `/sf:plan TODO-001` — convert by ID
+- `/sf:priority` — change priorities
+- `/sf:todo "new idea"` — add new item
 ```
 
 ## Step 7: Show Notes (if any have notes)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specflow-cc",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "description": "Spec-driven development system for Claude Code — quality-first workflow with explicit audit cycles",
   "bin": {
     "specflow-cc": "bin/install.js"

package/templates/audit.md

@@ -58,4 +58,4 @@ verdict: pass | fail | conditional
 
 ## Response History
 
-<!-- Filled by /sf revise -->
+<!-- Filled by /sf:revise -->

package/templates/scan.md

@@ -85,7 +85,7 @@ Based on this scan, consider creating specs for:
 1. **[Spec title]** — [brief description]
    - Priority: high | medium | low
    - Complexity: small | medium | large
-   - Command: `/sf new "[title]"`
+   - Command: `/sf:new "[title]"`
 
 2. **[Spec title]** — [brief description]
    - Priority: ...

package/templates/spec.md

@@ -56,4 +56,4 @@ created: YYYY-MM-DD
 
 ## Audit History
 
-<!-- Filled by /sf audit -->
+<!-- Filled by /sf:audit -->

package/templates/state.md

@@ -4,7 +4,7 @@
 
 - **Active Specification:** [none | SPEC-XXX]
 - **Status:** [idle | drafting | auditing | running | reviewing]
-- **Next Step:** [/sf new | /sf audit | /sf run | /sf review | /sf done]
+- **Next Step:** [/sf:new | /sf:audit | /sf:run | /sf:review | /sf:done]
 
 ## Queue