specflow-cc 1.0.0 → 1.2.0

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.0.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

@@ -0,0 +1,96 @@
+# Codebase Scan Report
+
+**Date:** [YYYY-MM-DD]
+**Focus:** [all | concerns | quality | arch]
+
+## Executive Summary
+
+[2-3 sentence overview of codebase health and key findings]
+
+**Health Score:** [Good | Moderate | Needs Attention | Critical]
+
+---
+
+## Tech Debt
+
+### High Priority
+
+**[Issue Title]**
+- Files: `[file/path.ts]`
+- Problem: [What's wrong]
+- Impact: [Why it matters]
+- Fix: [How to address]
+
+### Medium Priority
+
+<!-- Add issues here -->
+
+### Low Priority
+
+<!-- Add issues here -->
+
+---
+
+## Code Quality Issues
+
+### Type Safety
+
+**[Issue]**
+- Files: `[paths]`
+- Count: [N occurrences]
+- Fix: [Approach]
+
+### Error Handling
+
+<!-- Swallowed errors, missing catches, etc. -->
+
+### Code Duplication
+
+<!-- Similar code patterns that should be abstracted -->
+
+---
+
+## Security Considerations
+
+**[Risk Area]**
+- Files: `[paths]`
+- Risk: [What could happen]
+- Severity: [Critical | High | Medium | Low]
+- Mitigation: [What to do]
+
+---
+
+## Test Coverage Gaps
+
+**[Untested Area]**
+- Files: `[paths]`
+- What's missing: [Description]
+- Priority: [High | Medium | Low]
+
+---
+
+## Architecture Observations
+
+**[Observation]**
+- Current: [How it is]
+- Concern: [Why it's problematic]
+- Suggestion: [Improvement]
+
+---
+
+## Suggested Specifications
+
+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]"`
+
+2. **[Spec title]** — [brief description]
+   - Priority: ...
+   - Complexity: ...
+
+---
+
+*Scan completed: [timestamp]*

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