specflow-cc 1.0.0

package/commands/sf/revise.md

@@ -0,0 +1,232 @@
+---
+name: sf:revise
+description: Revise specification based on audit feedback
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+
+<purpose>
+Revise the active specification based on audit feedback. Can apply all comments, specific numbered items, or custom changes described by user.
+</purpose>
+
+<context>
+@.specflow/STATE.md
+@.specflow/PROJECT.md
+@~/.claude/specflow-cc/agents/spec-reviser.md
+</context>
+
+<workflow>
+
+## Step 1: Verify Initialization
+
+```bash
+[ -d .specflow ] && echo "OK" || echo "NOT_INITIALIZED"
+```
+
+**If NOT_INITIALIZED:**
+```
+SpecFlow not initialized.
+
+Run `/sf init` first.
+```
+Exit.
+
+## Step 2: Get Active Specification
+
+Read `.specflow/STATE.md` and extract Active Specification.
+
+**If no active specification:**
+```
+No active specification to revise.
+
+Run `/sf new "task description"` to create one.
+```
+Exit.
+
+## Step 3: Load Specification
+
+Read the active spec file: `.specflow/specs/SPEC-XXX.md`
+
+**If status is not 'draft', 'auditing', or 'revision_requested':**
+```
+Specification SPEC-XXX cannot be revised (status: {status}).
+
+Use `/sf status` to see current state.
+```
+Exit.
+
+## Step 4: Extract Latest Audit
+
+Find the most recent "Audit v[N]" section in Audit History.
+
+**If no audit exists:**
+```
+Specification SPEC-XXX has no audit history.
+
+Run `/sf audit` first to get feedback.
+```
+Exit.
+
+## Step 5: Parse Arguments
+
+| Argument | Action |
+|----------|--------|
+| (none) | Interactive mode — show comments, ask what to fix |
+| "all" | Apply all critical issues AND recommendations |
+| "1,2,3" | Apply only numbered items |
+| "..." | Treat as custom revision instructions |
+
+### If Interactive Mode (no arguments):
+
+Display audit comments:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ REVISION: SPEC-XXX
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Last audit (v{N}) found:
+
+**Critical:**
+1. [Issue 1]
+2. [Issue 2]
+
+**Recommendations:**
+3. [Recommendation 1]
+4. [Recommendation 2]
+
+---
+
+What to fix?
+```
+
+Use AskUserQuestion with options:
+- "Apply all feedback" → treat as "all"
+- "Fix critical only (1, 2)" → treat as "1,2"
+- "Custom selection" → ask for numbers or description
+
+## Step 6: Spawn Reviser Agent
+
+Launch the spec-reviser subagent:
+
+```
+Task(prompt="
+<specification>
+@.specflow/specs/SPEC-XXX.md
+</specification>
+
+<project_context>
+@.specflow/PROJECT.md
+</project_context>
+
+<revision_scope>
+{Parsed scope: "all", "1,2", or custom instructions}
+</revision_scope>
+
+Revise this specification following the spec-reviser agent instructions.
+Apply the specified changes and record the revision response.
+", subagent_type="sf-spec-reviser", description="Revise specification")
+```
+
+## Step 7: Handle Agent Response
+
+The agent will:
+1. Parse the latest audit
+2. Apply requested revisions
+3. Record Response v[N] in Audit History
+4. Update status to "auditing"
+5. Update STATE.md
+
+## Step 8: Display Result
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ REVISION COMPLETE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Specification:** SPEC-XXX
+**Audit:** v{N} → Response v{N}
+
+### Changes Applied
+
+1. [✓] {Change description}
+2. [✓] {Change description}
+
+{If any skipped:}
+### Skipped
+
+3. [✗] {Item} — {reason}
+
+---
+
+## Next Step
+
+`/sf audit` — re-audit revised specification
+```
+
+</workflow>
+
+<fallback>
+
+**If agent spawning fails**, execute inline:
+
+## Inline Revision
+
+### Parse Audit Comments
+
+Extract issues from latest audit section.
+
+### Apply Changes
+
+For each item in scope:
+
+1. Locate the relevant section
+2. Make minimal, targeted changes
+3. Track what was changed
+
+### Record Response
+
+Get response version:
+
+```bash
+RESPONSE_COUNT=$(grep -c "### Response v" .specflow/specs/SPEC-XXX.md 2>/dev/null || echo 0)
+NEXT_VERSION=$((RESPONSE_COUNT + 1))
+```
+
+Append to Audit History:
+
+```markdown
+### Response v{N} ({date} {time})
+**Applied:** {scope description}
+
+**Changes:**
+1. [✓/✗] {Item} — {what was done}
+2. [✓/✗] {Item} — {what was done}
+```
+
+### Update Status
+
+In spec frontmatter: `status: auditing`
+
+In STATE.md:
+- Status → "auditing"
+- Next Step → "/sf audit"
+
+</fallback>
+
+<success_criteria>
+- [ ] Active specification identified
+- [ ] Latest audit parsed
+- [ ] Revision scope determined (all/specific/custom)
+- [ ] Changes applied correctly
+- [ ] Response recorded in Audit History
+- [ ] Spec frontmatter status updated
+- [ ] STATE.md updated
+- [ ] Clear summary of changes shown
+</success_criteria>

package/commands/sf/run.md

@@ -0,0 +1,265 @@
+---
+name: sf:run
+description: Execute the specification (implement the code)
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+
+<purpose>
+Execute the active specification by implementing all requirements. Creates atomic commits during implementation and prepares for review.
+</purpose>
+
+<context>
+@.specflow/STATE.md
+@.specflow/PROJECT.md
+@~/.claude/specflow-cc/agents/spec-executor.md
+</context>
+
+<workflow>
+
+## Step 1: Verify Initialization
+
+```bash
+[ -d .specflow ] && echo "OK" || echo "NOT_INITIALIZED"
+```
+
+**If NOT_INITIALIZED:**
+```
+SpecFlow not initialized.
+
+Run `/sf init` first.
+```
+Exit.
+
+## Step 2: Get Active Specification
+
+Read `.specflow/STATE.md` and extract Active Specification.
+
+**If no active specification:**
+```
+No active specification to execute.
+
+Run `/sf new "task description"` to create one.
+```
+Exit.
+
+## Step 3: Load Specification
+
+Read the active spec file: `.specflow/specs/SPEC-XXX.md`
+
+## Step 4: Check Audit Status
+
+**If status is "audited":**
+Continue to execution.
+
+**If status is NOT "audited":**
+Show warning:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ WARNING: Specification has not passed audit
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Specification:** SPEC-XXX
+**Current Status:** {status}
+
+{If audit exists and has issues:}
+### Outstanding Issues
+
+From last audit (v{N}):
+
+**Critical:**
+1. {Issue 1}
+2. {Issue 2}
+
+**Recommendations:**
+3. {Recommendation 1}
+
+---
+
+Proceeding without audit approval may result in:
+- Implementation that doesn't meet requirements
+- Rework needed after review
+
+Continue anyway?
+```
+
+Use AskUserQuestion with options:
+- "Yes, proceed anyway" → continue, log warning
+- "No, run audit first" → exit with `/sf audit` suggestion
+
+**If user proceeds anyway:**
+Log in STATE.md Warnings table:
+```
+| {date} | SPEC-XXX | Executed without audit approval |
+```
+
+## Step 5: Pre-Execution Summary
+
+Display what will be implemented:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ EXECUTING: SPEC-XXX
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Title:** {spec title}
+**Type:** {feature|refactor|bugfix}
+**Complexity:** {small|medium|large}
+
+### Scope
+
+**Files to create:** {count}
+**Files to modify:** {count}
+**Files to delete:** {count}
+
+### Acceptance Criteria
+
+- [ ] {Criterion 1}
+- [ ] {Criterion 2}
+- [ ] {Criterion 3}
+
+---
+
+Beginning implementation...
+```
+
+## Step 6: Update Status
+
+Update STATE.md:
+- Status → "running"
+- Next Step → "(in progress)"
+
+Update spec frontmatter:
+- status → "running"
+
+## Step 7: Spawn Executor Agent
+
+Launch the spec-executor subagent:
+
+```
+Task(prompt="
+<specification>
+@.specflow/specs/SPEC-XXX.md
+</specification>
+
+<project_context>
+@.specflow/PROJECT.md
+</project_context>
+
+Execute this specification following the spec-executor agent instructions.
+Implement all requirements with atomic commits.
+", subagent_type="sf-spec-executor", description="Execute specification")
+```
+
+## Step 8: Handle Agent Response
+
+The agent will:
+1. Implement all requirements
+2. Create atomic commits
+3. Handle deviations
+4. Add Execution Summary to spec
+5. Update STATE.md to "review"
+
+## Step 9: Display Result
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ EXECUTION COMPLETE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Specification:** SPEC-XXX
+**Status:** Ready for review
+
+### Summary
+
+- **Files created:** {count}
+- **Files modified:** {count}
+- **Files deleted:** {count}
+- **Commits:** {count}
+
+### Acceptance Criteria
+
+- [x] {Criterion 1}
+- [x] {Criterion 2}
+- [x] {Criterion 3}
+
+{If deviations occurred:}
+### Deviations
+
+1. [Rule {N}] {description}
+
+---
+
+## Next Step
+
+`/sf review` — audit the implementation
+```
+
+</workflow>
+
+<fallback>
+
+**If agent spawning fails**, execute inline:
+
+## Inline Execution
+
+### Load Requirements
+
+Parse specification for:
+- Files to create/modify/delete
+- Interfaces
+- Acceptance criteria
+- Constraints
+
+### Implement
+
+For each requirement:
+1. Create/modify file
+2. Follow project patterns
+3. Meet acceptance criteria
+
+### Commit
+
+After each logical unit:
+```bash
+git add <files>
+git commit -m "feat(sf-XXX): <description>"
+```
+
+### Handle Deletions
+
+After replacements work:
+1. Check no remaining references
+2. Delete old files
+3. Commit removal
+
+### Update Specification
+
+Append Execution Summary to spec.
+
+### Update STATE.md
+
+- Status → "review"
+- Next Step → "/sf review"
+
+</fallback>
+
+<success_criteria>
+- [ ] Active specification identified
+- [ ] Audit status checked (warning if not audited)
+- [ ] All files created as specified
+- [ ] All files modified as specified
+- [ ] All files deleted as specified
+- [ ] Atomic commits created
+- [ ] Execution Summary added to spec
+- [ ] STATE.md updated to "review"
+- [ ] Clear next step shown
+</success_criteria>

package/commands/sf/show.md

@@ -0,0 +1,203 @@
+---
+name: sf:show
+description: Display full specification details
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+---
+
+<purpose>
+Display the full content of a specification including context, task, requirements, acceptance criteria, and audit/review history. Without arguments, shows the active specification.
+</purpose>
+
+<context>
+@.specflow/STATE.md
+</context>
+
+<arguments>
+- `[ID]` — Optional. Specification ID (e.g., SPEC-003). If omitted, shows active specification.
+</arguments>
+
+<workflow>
+
+## Step 1: Verify Initialization
+
+```bash
+[ -d .specflow ] && echo "OK" || echo "NOT_INITIALIZED"
+```
+
+**If NOT_INITIALIZED:**
+```
+SpecFlow not initialized.
+
+Run `/sf init` to start.
+```
+Exit.
+
+## Step 2: Determine Specification ID
+
+**If argument provided:**
+Use provided ID (e.g., SPEC-003).
+
+**If no argument:**
+Read `.specflow/STATE.md` and get Active Specification.
+
+**If no active specification and no argument:**
+```
+No specification specified and no active specification.
+
+Use `/sf show SPEC-XXX` to view a specific spec
+or `/sf list` to see all specifications.
+```
+Exit.
+
+## Step 3: Find Specification File
+
+```bash
+# Check in specs directory
+[ -f .specflow/specs/{ID}.md ] && echo "SPECS"
+
+# Check in archive
+[ -f .specflow/archive/{ID}.md ] && echo "ARCHIVE"
+```
+
+**If not found:**
+```
+Specification {ID} not found.
+
+Use `/sf list` to see available specifications.
+```
+Exit.
+
+## Step 4: Read Specification
+
+Read the spec file and parse:
+- Frontmatter (id, type, status, priority, complexity, created)
+- Title
+- Context section
+- Task section
+- Requirements section
+- Acceptance Criteria section
+- Constraints section
+- Assumptions section
+- Audit History section
+- Review History section (if exists)
+
+## Step 5: Summarize History
+
+### Audit History Summary
+Count audit versions and get final status:
+- "v{N} — APPROVED" or "v{N} — NEEDS_REVISION"
+
+### Review History Summary
+If review section exists:
+- Count review versions
+- Get final review status
+
+## Step 6: Determine Recommended Action
+
+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` |
+| done | No action (archived) |
+
+## Step 7: Display Specification
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ {ID}: {Title}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Status:** {status} | **Priority:** {priority} | **Complexity:** {complexity}
+**Type:** {type} | **Created:** {created}
+
+{If archived:}
+**Location:** Archive (completed)
+
+---
+
+## Context
+
+{Context from spec}
+
+## Task
+
+{Task from spec}
+
+## Requirements
+
+{Requirements from spec - files to create/modify/delete}
+
+## Acceptance Criteria
+
+{Criteria from spec with checkboxes}
+
+{If constraints exist:}
+## Constraints
+
+{Constraints from spec}
+
+{If assumptions exist:}
+## Assumptions
+
+{Assumptions from spec}
+
+---
+
+## History
+
+{If audit history exists:}
+**Audit:** v{N} — {APPROVED|NEEDS_REVISION} ({date})
+
+{If review history exists:}
+**Review:** v{N} — {APPROVED|NEEDS_FIXES} ({date})
+
+{If implementation started:}
+**Implementation:** {In progress | Completed}
+
+---
+
+**Next Step:** `{recommended_command}` — {description}
+```
+
+## Step 8: Additional Context
+
+**If spec is in archive:**
+```
+This specification is complete and archived.
+
+To view active specs: `/sf list`
+To see completed history: `/sf history`
+```
+
+**If spec has outstanding issues:**
+```
+**Outstanding Issues:**
+
+From {audit/review} v{N}:
+1. {issue}
+2. {issue}
+
+Address with `/sf revise` or `/sf fix`.
+```
+
+</workflow>
+
+<success_criteria>
+- [ ] Initialization verified
+- [ ] Spec ID determined (from argument or active)
+- [ ] Spec file found (specs or archive)
+- [ ] Full content displayed
+- [ ] Frontmatter parsed and shown
+- [ ] History summarized
+- [ ] Recommended next action clear
+- [ ] Archive status indicated if applicable
+</success_criteria>