specflow-cc 1.0.0

package/commands/sf/pause.md

@@ -0,0 +1,211 @@
+---
+name: sf:pause
+description: Save current work context for later resumption
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - AskUserQuestion
+---
+
+<purpose>
+Save the current work context to enable seamless resumption later. Creates a pause file with active specification, progress, recent changes, and optional notes. Essential for context preservation across sessions.
+</purpose>
+
+<context>
+@.specflow/STATE.md
+</context>
+
+<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: Get Current State
+
+Read `.specflow/STATE.md` and extract:
+- Active Specification
+- Status
+- Next Step
+
+**If no active specification:**
+```
+No active work to pause.
+
+Current state: idle
+```
+But still allow pausing to capture general notes.
+
+## Step 3: Load Active Specification Details
+
+If active spec exists, read `.specflow/specs/SPEC-XXX.md`:
+- Title
+- Type
+- Priority
+- Complexity
+- Acceptance Criteria (for progress tracking)
+
+## Step 4: Capture Git State
+
+```bash
+# Get uncommitted changes
+git status --porcelain 2>/dev/null
+
+# Get recent commits related to spec (if any)
+git log --oneline -5 2>/dev/null
+```
+
+Categorize changes:
+- New files (A or ??)
+- Modified files (M)
+- Deleted files (D)
+
+## Step 5: Estimate Progress
+
+If acceptance criteria exist with checkboxes:
+- Count total criteria
+- Count checked criteria
+- Calculate progress percentage
+
+Also count:
+- Files created
+- Files modified
+- Commits made (from Execution Summary if exists)
+
+## Step 6: Ask for Notes
+
+Use AskUserQuestion:
+- header: "Notes"
+- question: "Add notes for next session? (Enter to skip)"
+- options: (freeform text)
+
+Notes help remember context that isn't captured in code.
+
+## Step 7: Create Sessions Directory
+
+```bash
+mkdir -p .specflow/sessions
+```
+
+## Step 8: Generate Pause File
+
+Create `.specflow/sessions/PAUSE-{YYYYMMDD}-{HHMMSS}.md`:
+
+```markdown
+# Session Pause — {YYYY-MM-DD HH:MM:SS}
+
+## Context
+
+- **Specification:** {SPEC-XXX} ({title}) | none
+- **Status:** {status}
+- **Workflow Position:** {description based on status}
+
+## Specification Details
+
+{If active spec:}
+- **Type:** {feature|refactor|bugfix}
+- **Priority:** {priority}
+- **Complexity:** {complexity}
+
+## Progress
+
+- **Acceptance Criteria:** {checked}/{total} ({percentage}%)
+- **Files Created:** {count}
+- **Files Modified:** {count}
+- **Commits:** {count}
+
+## Recent Changes
+
+{If uncommitted changes:}
+```
++ {new file 1}
++ {new file 2}
+M {modified file 1}
+D {deleted file 1}
+```
+
+{If no uncommitted changes:}
+No uncommitted changes.
+
+## Notes
+
+{User's notes or "No notes added."}
+
+## Conversation Summary
+
+{Brief summary of what was being worked on}
+{Key decisions made}
+{What needs to happen next}
+
+---
+*Paused at: {YYYY-MM-DD HH:MM:SS}*
+```
+
+## Step 9: Update STATE.md
+
+Add reference to pause file:
+
+Under Current Position, add:
+```markdown
+- **Last Pause:** PAUSE-{YYYYMMDD}-{HHMMSS}
+```
+
+## Step 10: Display Confirmation
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ SESSION PAUSED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Saved:** PAUSE-{YYYYMMDD}-{HHMMSS}
+
+---
+
+## Context
+
+- **Specification:** {SPEC-XXX} — {title}
+- **Status:** {status}
+- **Progress:** {checked}/{total} criteria ({percentage}%)
+
+## Recent Changes
+
+{List of changed files}
+
+{If notes provided:}
+## Notes Saved
+
+"{notes}"
+
+---
+
+**Session saved successfully.**
+
+Resume with: `/sf resume`
+```
+
+</workflow>
+
+<success_criteria>
+- [ ] Initialization verified
+- [ ] Current state captured from STATE.md
+- [ ] Active spec details loaded (if any)
+- [ ] Git state captured
+- [ ] Progress estimated
+- [ ] User notes captured (optional)
+- [ ] Sessions directory created
+- [ ] PAUSE-{timestamp}.md created with full context
+- [ ] STATE.md updated with pause reference
+- [ ] Clear confirmation with resume instructions
+</success_criteria>

package/commands/sf/plan.md

@@ -0,0 +1,210 @@
+---
+name: sf:plan
+description: Convert a to-do item into a full specification
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+
+<purpose>
+Convert a to-do item from the backlog into a full specification. Reuses the spec-creator agent with the todo's context pre-filled. After creating the spec, removes the todo from the list.
+</purpose>
+
+<context>
+@.specflow/todos/TODO.md
+@.specflow/PROJECT.md
+@.specflow/STATE.md
+@~/.claude/specflow-cc/agents/spec-creator.md
+</context>
+
+<arguments>
+- `[ID or #]` — Optional. Either TODO-XXX ID or list number from `/sf todos`. If omitted, shows todos and prompts for selection.
+</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: Check for Todos
+
+```bash
+[ -f .specflow/todos/TODO.md ] && echo "EXISTS" || echo "NO_TODOS"
+```
+
+**If NO_TODOS:**
+```
+No to-do items found.
+
+Add ideas first with `/sf todo "your idea"`.
+```
+Exit.
+
+## Step 3: Determine Target Todo
+
+**If argument is a number (e.g., "1", "2"):**
+Parse TODO.md, sort by priority, and select the Nth item.
+
+**If argument is TODO-XXX format:**
+Find todo with matching ID.
+
+**If no argument:**
+Display todos and prompt:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ SELECT TODO TO CONVERT
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| #  | ID       | Description              | Priority |
+|----|----------|--------------------------|----------|
+| 1  | TODO-001 | Add caching for API      | high     |
+| 2  | TODO-003 | Refactor AuthService     | medium   |
+| 3  | TODO-002 | Update documentation     | low      |
+
+Enter number or ID to convert:
+```
+
+Use AskUserQuestion with options as todo items.
+
+## Step 4: Extract Todo Details
+
+Read the selected todo:
+- ID
+- Description
+- Priority
+- Notes (if any)
+
+**If todo not found:**
+```
+Todo "{arg}" not found.
+
+Use `/sf todos` to see available items.
+```
+Exit.
+
+## Step 5: Spawn Spec Creator Agent
+
+Launch the spec-creator subagent with todo context:
+
+```
+Task(prompt="
+<task_description>
+{todo description}
+</task_description>
+
+<todo_context>
+**From:** TODO-{XXX}
+**Priority:** {priority}
+**Notes:** {notes or 'None'}
+</todo_context>
+
+<project_context>
+@.specflow/PROJECT.md
+</project_context>
+
+<current_state>
+@.specflow/STATE.md
+</current_state>
+
+Create a specification following the spec-creator agent instructions.
+Use the priority from the todo as the spec's initial priority.
+", subagent_type="sf-spec-creator", description="Create specification from todo")
+```
+
+## Step 6: Remove Todo from List
+
+After spec is successfully created, remove the todo entry from TODO.md.
+
+Update `*Last updated:` timestamp.
+
+**Important:** Only remove after confirmed spec creation.
+
+## Step 7: Display Result
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ TODO CONVERTED TO SPECIFICATION
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**From:** TODO-{XXX} — "{description}"
+**To:** SPEC-{YYY} — "{title}"
+
+**Type:** {feature|refactor|bugfix}
+**Complexity:** {small|medium|large}
+**Priority:** {priority} (inherited from todo)
+
+### Assumptions Made
+
+- {assumption 1}
+- {assumption 2}
+
+---
+
+**Todo removed from backlog.**
+
+## Next Step
+
+`/sf audit` — audit specification before implementation
+
+{If complexity is large:}
+
+### Warning
+
+Specification is large (>150k tokens estimated).
+Consider `/sf split SPEC-{YYY}` to decompose.
+```
+
+</workflow>
+
+<fallback>
+
+**If agent spawning fails**, execute inline:
+
+## Inline Conversion
+
+### Get Todo Details
+
+Read from TODO.md.
+
+### Create Spec (same as /sf new)
+
+Use `/sf new "{todo description}"` logic:
+1. Generate SPEC-XXX ID
+2. Create spec with todo context
+3. Set priority from todo
+4. Update STATE.md
+
+### Remove Todo
+
+Delete todo block from TODO.md.
+
+</fallback>
+
+<success_criteria>
+- [ ] Initialization verified
+- [ ] TODO.md exists and has items
+- [ ] Target todo identified (by ID or number)
+- [ ] Todo details extracted
+- [ ] Spec-creator agent spawned with context
+- [ ] SPEC-XXX.md created
+- [ ] Priority inherited from todo
+- [ ] Todo removed from TODO.md
+- [ ] Clear result with next step
+</success_criteria>

package/commands/sf/priority.md

@@ -0,0 +1,198 @@
+---
+name: sf:priority
+description: Interactive prioritization of specifications and to-dos
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - AskUserQuestion
+---
+
+<purpose>
+Interactively prioritize specifications and to-do items. Allows reordering, setting priority levels, and optionally suggests technically optimal order based on dependencies.
+</purpose>
+
+<context>
+@.specflow/STATE.md
+@.specflow/todos/TODO.md
+</context>
+
+<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: Load All Items
+
+### Load Specifications
+
+```bash
+ls -1 .specflow/specs/SPEC-*.md 2>/dev/null
+```
+
+For each spec, extract:
+- ID
+- Title
+- Priority
+- Status
+
+### Load Todos
+
+Read `.specflow/todos/TODO.md` and extract:
+- ID
+- Description
+- Priority
+
+## Step 3: Display Current Prioritization
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PRIORITIZATION
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+## Specifications
+
+| # | ID       | Title              | Priority | Status   |
+|---|----------|--------------------|----------|----------|
+| 1 | SPEC-003 | Auth middleware    | high     | running  |
+| 2 | SPEC-004 | User profile       | medium   | audited  |
+| 3 | SPEC-005 | Settings page      | low      | draft    |
+
+## To-Dos
+
+| # | ID       | Description        | Priority |
+|---|----------|--------------------|----------|
+| 4 | TODO-001 | Add caching        | high     |
+| 5 | TODO-002 | Refactor auth      | medium   |
+| 6 | TODO-003 | Update docs        | —        |
+
+---
+
+**Options:**
+```
+
+## Step 4: Prompt for Action
+
+Use AskUserQuestion with options:
+
+1. **Set priority** — Change priority for specific item
+   - Format: `SPEC-004=high` or `TODO-001=low`
+
+2. **Reorder specs** — Enter new order for specifications
+   - Format: `2,1,3` (by current # position)
+
+3. **Technical order** — Auto-suggest based on dependencies
+   - Analyzes specs for dependency hints
+
+4. **Done** — Exit prioritization
+
+```
+**Commands:**
+- Set priority: `SPEC-004=high` or `TODO-001=low`
+- Reorder specs: `2,1,3` (by # position)
+- Technical order: `tech`
+- Cancel: `q` or `done`
+
+Your choice:
+```
+
+## Step 5: Handle Actions
+
+### Set Priority
+
+If input matches pattern `{ID}={priority}`:
+
+1. Validate priority (high | medium | low)
+2. Update frontmatter in spec file OR priority line in TODO.md
+3. Display confirmation
+4. Return to Step 3
+
+### Reorder Specifications
+
+If input matches pattern `N,N,N`:
+
+1. Validate all numbers exist
+2. Recalculate priorities based on position:
+   - Position 1-2: high
+   - Position 3-4: medium
+   - Position 5+: low
+3. Update each spec's frontmatter
+4. Update STATE.md Queue table
+5. Display confirmation
+6. Return to Step 3
+
+### Technical Order
+
+If input is `tech`:
+
+1. Analyze specs for dependency hints:
+   - Look for "depends on", "requires", "after" in Context
+   - Look for file references that overlap
+2. Suggest order based on:
+   - Dependencies (prerequisites first)
+   - Complexity (smaller first if no deps)
+   - Type (bugfix > refactor > feature)
+
+```
+**Suggested Technical Order:**
+
+| # | ID       | Title              | Reason              |
+|---|----------|--------------------|---------------------|
+| 1 | SPEC-005 | Settings page      | Smallest, no deps   |
+| 2 | SPEC-003 | Auth middleware    | Required by SPEC-004|
+| 3 | SPEC-004 | User profile       | Depends on auth     |
+
+Apply this order? [Y/n]
+```
+
+If confirmed, apply reordering.
+
+### Done/Cancel
+
+If input is `q`, `done`, or `cancel`:
+Exit prioritization.
+
+## Step 6: Display Final State
+
+After changes:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ PRIORITIZATION UPDATED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+**Changes made:**
+- SPEC-004: medium → high
+- SPEC-005: low → medium
+
+---
+
+Use `/sf next` to work on highest priority task.
+```
+
+</workflow>
+
+<success_criteria>
+- [ ] Initialization verified
+- [ ] All specs loaded with current priorities
+- [ ] All todos loaded with current priorities
+- [ ] Combined numbered list displayed
+- [ ] Set priority command works
+- [ ] Reorder command works
+- [ ] Technical order suggestion available
+- [ ] Changes persisted to files
+- [ ] STATE.md Queue updated after spec reorder
+- [ ] Clear feedback on changes
+</success_criteria>