specdacular 0.7.0 → 0.7.1

package/commands/specd/phase/prepare.md

@@ -1,75 +0,0 @@
----
-name: specd:phase:prepare
-description: Discuss gray areas and optionally research patterns for a phase
-argument-hint: "[feature-name] [phase-number]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Task
-  - AskUserQuestion
----
-
-<objective>
-Prepare a phase for execution by discussing gray areas and optionally researching implementation patterns. Combines discussion and research into a single flow.
-
-**Discussion always happens.** Research is offered as an optional step at the end.
-
-**Updates:**
-- `.specd/features/{name}/plans/phase-{NN}/CONTEXT.md` — Phase-specific discussion resolutions
-- `.specd/features/{name}/DECISIONS.md` — Accumulates decisions with dates/rationale
-- `.specd/features/{name}/plans/phase-{NN}/RESEARCH.md` — Phase research (if opted in)
-
-**Why merged?** Discussing a phase often reveals what needs researching. Single command, natural flow.
-</objective>
-
-<execution_context>
-@~/.claude/specdacular/workflows/prepare-phase.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (expects: feature-name phase-number)
-
-**Load feature context:**
-@.specd/features/{name}/FEATURE.md
-@.specd/features/{name}/CONTEXT.md
-@.specd/features/{name}/DECISIONS.md
-@.specd/features/{name}/ROADMAP.md
-
-**Load phase context:**
-@.specd/features/{name}/plans/phase-{NN}/*.md (plan files)
-
-**Load codebase context (if available):**
-@.specd/codebase/PATTERNS.md
-@.specd/codebase/STRUCTURE.md
-@.specd/codebase/MAP.md
-</context>
-
-<process>
-1. **Validate** — Feature exists, phase exists in ROADMAP.md
-2. **Load Context** — Phase details from ROADMAP.md, plans in phase, feature DECISIONS.md
-3. **Show Phase State** — Present phase overview and existing context
-4. **Identify Gray Areas** — Phase-type-specific concerns
-5. **Probe Gray Areas** — 4 questions per area, then move on
-6. **Record Discussion** — Save to phase CONTEXT.md, update DECISIONS.md
-7. **Offer Research** — "Would you like to research implementation patterns?"
-8. If yes: **Spawn Research Agents** — 3 parallel agents for phase-specific research
-9. If yes: **Synthesize Research** — Combine into phase RESEARCH.md
-10. If yes: **Record Research Decisions** — Technology choices to DECISIONS.md
-11. **Commit and Complete** — Points to `/specd:phase:plan` or `/specd:phase:execute`
-</process>
-
-<success_criteria>
-- [ ] Feature and phase validated
-- [ ] Phase context loaded (plans, goals, files to create/modify)
-- [ ] Phase-type-specific gray areas identified
-- [ ] User-selected areas discussed
-- [ ] Decisions recorded with date, context, rationale
-- [ ] Phase CONTEXT.md created/updated with resolved questions
-- [ ] Research completed (if user opted in)
-- [ ] Committed to git
-- [ ] User knows next steps: `/specd:phase:plan` or `/specd:phase:execute`
-</success_criteria>

package/commands/specd/phase/renumber.md

@@ -1,66 +0,0 @@
----
-name: specd:phase:renumber
-description: Renumber phases to clean integer sequence
-argument-hint: "[feature-name]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-
-<objective>
-Renumber all phases to a clean integer sequence after decimal phases have been inserted.
-
-**What it does:**
-1. Validate — Feature exists with plans and ROADMAP.md
-2. Collect phases — List all phase directories, build old->new mapping
-3. Preview — Show renumbering plan, ask user to confirm
-4. Rename directories — Process highest-to-lowest to avoid collisions
-5. Update plan frontmatter — Fix phase references in plan files
-6. Update ROADMAP.md — Rewrite phase headers, remove `(INSERTED)` markers
-7. Update STATE.md — Rewrite phase references everywhere
-8. Update config.json — Set `phases_count` to new total
-9. Show summary
-</objective>
-
-<execution_context>
-@~/.claude/specdacular/workflows/renumber-phases.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (expects: feature-name)
-
-**Load feature context:**
-@.specd/features/{name}/ROADMAP.md
-@.specd/features/{name}/STATE.md
-@.specd/features/{name}/config.json
-@.specd/features/{name}/plans/ (all phase directories and plan files)
-</context>
-
-<process>
-1. **Validate** — Feature exists with plans directory and ROADMAP.md
-2. **Collect Phases** — Build sorted list and renumbering mapping
-3. **Preview** — Show mapping, confirm with user
-4. **Rename Directories** — Highest target number down to avoid collisions
-5. **Update Plan Frontmatter** — Fix phase/depends_on in plan YAML
-6. **Update ROADMAP.md** — Rewrite headers, remove `(INSERTED)` markers
-7. **Update STATE.md** — Rewrite all phase references
-8. **Update config.json** — Set `phases_count` to integer count
-9. **Completion** — Show summary of changes
-</process>
-
-<success_criteria>
-- [ ] Feature validated with plans and ROADMAP.md
-- [ ] All phase directories collected and sorted correctly
-- [ ] Renumbering mapping shown to user and confirmed
-- [ ] Directories renamed without collisions (highest-to-lowest)
-- [ ] Plan file frontmatter updated (phase, depends_on)
-- [ ] ROADMAP.md headers and references updated, `(INSERTED)` markers removed
-- [ ] STATE.md phase references updated everywhere
-- [ ] config.json `phases_count` updated
-- [ ] Summary shown to user
-</success_criteria>

package/commands/specd/phase/research.md

@@ -1,65 +0,0 @@
----
-name: specd:phase:research
-description: Research implementation patterns for a phase
-argument-hint: "[feature-name] [phase-number]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Task
-  - AskUserQuestion
----
-
-<objective>
-Research implementation patterns for a specific phase before executing it. Spawns parallel research agents focused on the phase's scope.
-
-**Output:** `.specd/features/{name}/plans/phase-{NN}/RESEARCH.md` with phase-specific guidance.
-
-**Why phase-level research?** Instead of researching the entire feature upfront, investigate each phase's specifics right before executing it. Smaller scope, more focused, fresher context.
-
-**Note:** This is also available as part of `/specd:phase:prepare`. Use this standalone command when you want to research without discussing first.
-</objective>
-
-<execution_context>
-@~/.claude/specdacular/workflows/research-phase.md
-</execution_context>
-
-<context>
-Arguments: $ARGUMENTS (expects: feature-name phase-number)
-
-**Load feature context:**
-@.specd/features/{name}/FEATURE.md
-@.specd/features/{name}/DECISIONS.md
-@.specd/features/{name}/ROADMAP.md
-@.specd/features/{name}/RESEARCH.md (if exists, feature-level research)
-
-**Load phase context:**
-@.specd/features/{name}/plans/phase-{NN}/CONTEXT.md (if exists)
-@.specd/features/{name}/plans/phase-{NN}/*.md (plan files)
-
-**Load codebase context:**
-@.specd/codebase/PATTERNS.md
-@.specd/codebase/STRUCTURE.md
-@.specd/codebase/MAP.md
-</context>
-
-<process>
-1. **Validate** — Feature and phase exist
-2. **Load Context** — Phase goals, files to create/modify, previous phase research
-3. **Spawn Research Agents** — 3 parallel agents for phase-specific research
-4. **Synthesize** — Combine into `plans/phase-{NN}/RESEARCH.md`
-5. **Record Decisions** — Technology choices to DECISIONS.md
-6. **Commit**
-</process>
-
-<success_criteria>
-- [ ] Feature and phase validated
-- [ ] Phase context loaded (goals, files, type)
-- [ ] Research agents spawned (codebase, patterns, pitfalls)
-- [ ] Results synthesized into phase RESEARCH.md
-- [ ] Decisions recorded in DECISIONS.md
-- [ ] Committed to git
-</success_criteria>

package/commands/specd/phase/review.md

@@ -1,80 +0,0 @@
----
-name: specd:phase:review
-description: Review executed plans against actual code and identify deviations
-argument-hint: "[feature-name] [phase-number]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-
-<objective>
-Review executed plans for a phase, comparing intended changes against actual code. Surfaces deviations, captures decisions, and generates corrective plans when needed.
-
-**What it does:**
-1. Load context — STATE.md, plans, DECISIONS.md, codebase docs
-2. Filter plans — Only review plans with status Complete (DEC-006)
-3. Inspect each plan — Compare creates/modifies frontmatter against actual files
-4. Present findings — Per-plan status table with expandable details (DEC-005)
-5. Gather user input — Ask about satisfaction, additional issues (DEC-001)
-6. Record decisions — New decisions to DECISIONS.md
-7. Generate correctives — Corrective plans if issues found (DEC-003)
-8. Update state — Review Cycles in STATE.md (DEC-004)
-9. Commit and suggest next steps
-</objective>
-
-<execution_context>
-@~/.claude/specdacular/workflows/review-phase.md
-</execution_context>
-
-<context>
-Feature name: $ARGUMENTS (first argument)
-Phase number: $ARGUMENTS (second argument)
-
-**Load ALL feature context:**
-@.specd/features/{name}/STATE.md — Progress tracking, completed plans
-@.specd/features/{name}/DECISIONS.md — Existing decisions
-@.specd/features/{name}/RESEARCH.md — Implementation notes (if exists)
-@.specd/features/{name}/ROADMAP.md — Phase overview
-@.specd/features/{name}/CHANGELOG.md — Existing deviations (if exists)
-
-**Load plan files for the phase:**
-@.specd/features/{name}/plans/phase-{NN}/*.md — All plan files
-
-**Load codebase context:**
-@.specd/codebase/PATTERNS.md — Code patterns
-@.specd/codebase/STRUCTURE.md — File locations
-@.specd/codebase/MAP.md — System overview
-</context>
-
-<process>
-1. **Validate** — Feature exists, phase exists, has execution history
-2. **Load Context** — Read all feature, plan, and codebase docs
-3. **Filter Plans** — Get only completed plans for this phase
-4. **Inspect Phase** — Compare each plan's intent against actual code
-5. **Present Findings** — Per-plan status table + deviation details
-6. **Gather User Input** — Ask about satisfaction, additional issues
-7. **Record Decisions** — Save new decisions to DECISIONS.md
-8. **Generate Correctives** — Create corrective plans if needed
-9. **Update State** — Update Review Cycles section in STATE.md
-10. **Update Changelog** — Log deviations to CHANGELOG.md
-11. **Commit and Next** — Commit changes, suggest next steps
-</process>
-
-<success_criteria>
-- [ ] Feature and phase validated with execution history
-- [ ] All completed plans inspected against actual code
-- [ ] Per-plan status table displayed (✅/⚠️/❌/⏸️)
-- [ ] Deviations surfaced with planned vs actual comparison
-- [ ] User input captured (satisfaction, additional issues)
-- [ ] New decisions recorded in DECISIONS.md
-- [ ] Corrective plans generated if issues identified
-- [ ] Review Cycles section updated in STATE.md
-- [ ] Deviations logged in CHANGELOG.md
-- [ ] Changes committed
-- [ ] Next steps suggested
-</success_criteria>