work-kit-cli 0.2.7 → 0.3.0

package/skills/full-kit/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: full-kit
-description: "Full pipeline for feature development. Runs all phases and sub-stages in order. Usage: /full-kit <description> to start, /full-kit to continue."
+description: "Full pipeline for feature development. Runs all phases and steps in order. Usage: /full-kit <description> to start, /full-kit to continue."
 user-invocable: true
 argument-hint: "[--gated] [description]"
 allowed-tools: Agent, Bash, Read, Write, Edit, Glob, Grep
 ---
 
-You are the **Work Orchestrator (Full Mode)**. You run the complete lifecycle of a feature through every phase and sub-stage. No shortcuts.
+You are the **Work Orchestrator (Full Mode)**. You run the complete lifecycle of a feature through every phase and step. No shortcuts.
 
 Best for: large features, new systems, or when you want maximum rigor.
 
@@ -14,7 +14,7 @@ Best for: large features, new systems, or when you want maximum rigor.
 
 Before starting, verify the CLI is installed:
 ```bash
-npx work-kit-cli doctor
+work-kit doctor
 ```
 
 If `work-kit` is not found, ask the user to install it:
@@ -37,7 +37,7 @@ Do not proceed until `doctor` reports all checks passed.
    ```bash
    git worktree add worktrees/<slug> -b feature/<slug>
    cd worktrees/<slug>
-   npx work-kit-cli init --mode full --description "<description>"
+   work-kit init --mode full --description "<description>"
    ```
    If the user passed `--gated` (e.g., `/full-kit --gated add user avatar`), add `--gated` to the init command. Strip `--gated` from the description text.
 2. Parse the JSON response and follow the action
@@ -45,34 +45,34 @@ Do not proceed until `doctor` reports all checks passed.
 
 ## Continuing Work (`/full-kit` with no args)
 
-1. Run `npx work-kit-cli bootstrap` to detect session state
+1. Run `work-kit bootstrap` to detect session state
 2. Parse the JSON response:
    - If `active: false` — no session found, ask the user for a description and start new work
    - If `recovery` is set — report the recovery suggestion to the user before continuing
-   - If `active: true` — report current state (slug, phase, sub-stage) to the user
+   - If `active: true` — report current state (slug, phase, step) to the user
 3. `cd` into the worktree directory
-4. Run `npx work-kit-cli next` to get the next action
+4. Run `work-kit next` to get the next action
 5. Follow the execution loop below
 
 ## Execution Loop
 
 The CLI manages all state transitions, prerequisites, and loopbacks. Follow this loop:
 
-1. Run `npx work-kit-cli next` to get the next action
+1. Run `work-kit next` to get the next action
 2. Parse the JSON response
 3. Follow the action type:
-   - **`spawn_agent`**: Use the Agent tool with the provided `agentPrompt`. Pass `skillFile` path for reference. After the agent completes: `npx work-kit-cli complete <phase>/<sub-stage> --outcome <outcome>`
-   - **`spawn_parallel_agents`**: Spawn all agents in the `agents` array in parallel using the Agent tool. Wait for all to complete. Then spawn `thenSequential` if provided. After all complete: `npx work-kit-cli complete <onComplete target>`
-   - **`wait_for_user`**: Report the message to the user and stop. Wait for them to say "proceed" before running `npx work-kit-cli next` again. (Only appears in `--gated` mode.)
-   - **`loopback`**: Report the loopback to the user, then run `npx work-kit-cli next` to continue from the target.
+   - **`spawn_agent`**: Use the Agent tool with the provided `agentPrompt`. Pass `skillFile` path for reference. After the agent completes: `work-kit complete <phase>/<step> --outcome <outcome>`
+   - **`spawn_parallel_agents`**: Spawn all agents in the `agents` array in parallel using the Agent tool. Wait for all to complete. Then spawn `thenSequential` if provided. After all complete: `work-kit complete <onComplete target>`
+   - **`wait_for_user`**: Report the message to the user and stop. Wait for them to say "proceed" before running `work-kit next` again. (Only appears in `--gated` mode.)
+   - **`loopback`**: Report the loopback to the user, then run `work-kit next` to continue from the target.
    - **`complete`**: Done — run wrap-up if not already done.
    - **`error`**: Report the error and suggestion to the user. Stop.
-4. After each agent completes: `npx work-kit-cli complete <phase>/<sub-stage> --outcome <outcome>`
-5. Then `npx work-kit-cli next` again to continue
+4. After each agent completes: `work-kit complete <phase>/<step> --outcome <outcome>`
+5. Then `work-kit next` again to continue
 
 ## Phase Prerequisites
 
-Prerequisites are enforced by the CLI (`npx work-kit-cli validate <phase>`). You don't need to check manually — the `next` command handles it.
+Prerequisites are enforced by the CLI (`work-kit validate <phase>`). You don't need to check manually — the `next` command handles it.
 
 | Phase    | Requires                          |
 |----------|-----------------------------------|
@@ -90,12 +90,12 @@ Each phase runs as a **fresh agent** (sub-agent spawned by the orchestrator). Th
 ```
 Orchestrator (main agent — you)
 │
-├── Agent: Plan (single agent, all 8 sub-stages)
+├── Agent: Plan (single agent, all 8 steps)
 │   ├── reads: ## Description, ## Criteria, codebase
 │   ├── runs: Clarify → Investigate → ... → Audit
 │   └── writes: ### Plan: Final (Blueprint, Architecture, Scope, Constraints)
 │
-├── Agent: Build (single agent, all 8 sub-stages)
+├── Agent: Build (single agent, all 8 steps)
 │   ├── reads: ### Plan: Final, ## Criteria
 │   ├── runs: Setup → Migration → ... → Commit
 │   └── writes: ### Build: Final (PR, files changed, test status, deviations)
@@ -116,7 +116,7 @@ Orchestrator (main agent — you)
 │   ├── then: Handoff (reads all 4 results → ship decision)
 │   └── writes: ### Review: Final (decision, issues, concerns)
 │
-├── Agent: Deploy (single agent, all 3 sub-stages)
+├── Agent: Deploy (single agent, all 3 steps)
 │   ├── reads: ### Review: Final, ### Build: Final
 │   ├── runs: Merge → Monitor → Remediate
 │   └── writes: ### Deploy: Final (merge/deploy status)
@@ -145,7 +145,7 @@ Orchestrator (main agent — you)
 
 ### Phase Handoff via Final Sections
 
-Each phase writes a `### <Phase>: Final` section — a self-contained summary of that phase's output. The next phase's agent reads **only** the Final sections it needs, not the sub-stage working notes.
+Each phase writes a `### <Phase>: Final` section — a self-contained summary of that phase's output. The next phase's agent reads **only** the Final sections it needs, not the step working notes.
 
 ```
 state.md grows like this:
@@ -168,14 +168,14 @@ state.md grows like this:
 For each phase:
 1. **Check prerequisites** — verify the required prior phase is marked complete in state.md
 2. **Spawn a fresh agent** for the phase — pass it the phase skill file and the relevant Final sections from state.md
-3. The agent reads each sub-stage file when directed (e.g., `.claude/skills/wk-plan/stages/clarify.md`)
-4. The agent updates `.work-kit/state.md` after each sub-stage completes
+3. The agent reads each step file when directed (e.g., `.claude/skills/wk-plan/steps/clarify.md`)
+4. The agent updates `.work-kit/state.md` after each step completes
 5. The agent writes the `### <Phase>: Final` section before exiting
 6. After the agent completes, summarize results to the user and wait for confirmation
 
 ## Loop-Back Rules
 
-Some sub-stages can route backwards based on their outcome:
+Some steps can route backwards based on their outcome:
 
 - **Plan Audit** → "revise" → re-run Blueprint
 - **Build Refactor** → "broken" → re-run Core
@@ -183,7 +183,7 @@ Some sub-stages can route backwards based on their outcome:
 - **Deploy Merge** → "fix_needed" → re-run Build (from Core)
 - **Deploy Remediate** → "fix_and_redeploy" → re-run Build (from Core)
 
-On loop-back: add a `## Loop-back context` section to state.md with what needs to change and why, then resume at the target sub-stage.
+On loop-back: add a `## Loop-back context` section to state.md with what needs to change and why, then resume at the target step.
 
 ## Completion
 

package/skills/pause-kit/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: pause-kit
+description: "Pause the active work-kit session. Use when stepping away mid-flight. Usage: /pause-kit [reason]"
+user-invocable: true
+argument-hint: "[reason]"
+allowed-tools: Bash, Read
+---
+
+You are pausing the active work-kit session so it can be resumed cleanly later.
+
+## Steps
+
+1. Run `work-kit bootstrap` to confirm a session is active. If no session is active, tell the user there is nothing to pause and stop.
+2. `cd` into the worktree path reported by bootstrap.
+3. Run:
+   ```bash
+   work-kit pause${ARGUMENTS:+ --reason "$ARGUMENTS"}
+   ```
+4. Parse the JSON response.
+5. Report the message to the user. Tell them they can run `/resume-kit` (or `work-kit resume`) when ready.
+
+## Notes
+
+- Pausing only flips state to `paused` and records `pausedAt` — no files are deleted, no git operations happen.
+- The orchestrator (`/full-kit`, `/auto-kit`) refuses to advance a paused session until it is resumed.

package/skills/resume-kit/SKILL.md

@@ -0,0 +1,28 @@
+---
+name: resume-kit
+description: "Resume a paused work-kit session and continue where it left off. Usage: /resume-kit"
+user-invocable: true
+allowed-tools: Bash, Read, Agent, Write, Edit, Glob, Grep
+---
+
+You are resuming a paused work-kit session.
+
+## Steps
+
+1. Run `work-kit bootstrap` to find the active session. If `active: false`, tell the user there is no session and stop.
+2. `cd` into the worktree path reported by bootstrap.
+3. Run:
+   ```bash
+   work-kit resume
+   ```
+4. Parse the JSON. If `action: "resumed"`, report the slug, phase, and step to the user.
+5. Continue the orchestrator loop (same as `/full-kit` / `/auto-kit`):
+   ```bash
+   work-kit next
+   ```
+   Then follow the action returned (`spawn_agent`, `spawn_parallel_agents`, `wait_for_user`, etc.) using the Agent tool.
+
+## Notes
+
+- `resume` is idempotent: if the session was already in-progress, it just reports the current location.
+- A paused session keeps all state — phases, steps, loopbacks, timing — exactly as they were.

package/skills/wk-bootstrap/SKILL.md

@@ -7,13 +7,13 @@ allowed-tools: Bash, Read
 
 # Session Bootstrap
 
-Run `npx work-kit-cli bootstrap` to detect work-kit state.
+Run `work-kit bootstrap` to detect work-kit state.
 
 ## If active work exists
 
-- Report current state to the user: slug, phase, sub-stage, status
+- Report current state to the user: slug, phase, step, status
 - If recovery is suggested: follow the recovery instruction
-- Otherwise: run `npx work-kit-cli next` to continue the workflow
+- Otherwise: run `work-kit next` to continue the workflow
 
 ## If no active work
 
@@ -24,6 +24,6 @@ Run `npx work-kit-cli bootstrap` to detect work-kit state.
 ## If session is stale
 
 - Report the staleness warning to the user
-- Run `npx work-kit-cli status` to get full diagnostics
-- If the state is recoverable, run `npx work-kit-cli next` to resume
+- Run `work-kit status` to get full diagnostics
+- If the state is recoverable, run `work-kit next` to resume
 - If the state is corrupted, suggest starting fresh

package/skills/wk-build/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: build
-description: "Run the Build phase — 8 sub-stages from Setup to Commit. Follows the Blueprint from Plan."
+description: "Run the Build phase — 8 steps from Setup to Commit. Follows the Blueprint from Plan."
 user-invocable: false
 allowed-tools: Bash, Read, Write, Edit, Glob, Grep
 ---
 
 You are the **Lead Developer**. Execute the implementation plan from the Blueprint precisely.
 
-## Sub-stages (in order)
+## Steps (in order)
 
 1. **Setup** — Create branch, install deps, scaffold
 2. **Migration** — Database schema changes
@@ -20,12 +20,12 @@ You are the **Lead Developer**. Execute the implementation plan from the Bluepri
 
 ## Execution
 
-For each sub-stage:
-1. Read the sub-stage file (e.g., `.claude/skills/wk-build/stages/setup.md`)
+For each step:
+1. Read the step file (e.g., `.claude/skills/wk-build/steps/setup.md`)
 2. Reference the Blueprint in `.work-kit/state.md` — follow its steps for this layer
 3. Write actual code, run actual commands
 4. Update `.work-kit/state.md` with outputs
-5. Proceed to the next sub-stage
+5. Proceed to the next step
 
 ## Key Principle
 
@@ -33,7 +33,7 @@ For each sub-stage:
 
 ## Recording
 
-Throughout every sub-stage, capture three things in the shared state.md sections:
+Throughout every step, capture three things in the shared state.md sections:
 
 - **`## Decisions`** — Whenever you choose between real alternatives, append: `**<context>**: chose <X> over <Y> — <why>`. Skip obvious choices.
 - **`## Deviations`** — Whenever you diverge from the Blueprint, append: `**<Blueprint step>**: <what changed> — <why>`. Every deviation needs a reason.
@@ -44,7 +44,7 @@ These feed into the final work-kit log summary. If you don't record them here, t
 
 ### Always
 - Follow the Blueprint step order unless a dependency requires reordering
-- Run the test suite after every sub-stage that changes code
+- Run the test suite after every step that changes code
 - Record every deviation from the Blueprint in the ## Deviations section
 - Match existing codebase patterns found during Plan/Investigate
 - Commit .work-kit/ files separately from feature code
@@ -53,7 +53,7 @@ These feed into the final work-kit log summary. If you don't record them here, t
 - Redesigning any part of the Blueprint (adapt minimally, don't redesign)
 - Adding dependencies not specified in the Blueprint
 - Changing the data model beyond what Architecture specified
-- Skipping the Red (failing tests) sub-stage
+- Skipping the Red (failing tests) step
 
 ### Never
 - Write implementation code before writing failing tests (Red comes before Core)
@@ -78,11 +78,11 @@ This phase runs as a **fresh agent**. Read only these sections from `.work-kit/s
 - `## Criteria` — what "done" looks like
 - `## Description` — original request for context
 
-Do NOT read the Plan sub-stage working notes (Clarify, Investigate, Sketch, etc.) — they're consumed by Plan: Final.
+Do NOT read the Plan step working notes (Clarify, Investigate, Sketch, etc.) — they're consumed by Plan: Final.
 
 ## Final Output
 
-After all sub-stages are done, append a `### Build: Final` section to state.md. This is the **only section the Test agent reads**.
+After all steps are done, append a `### Build: Final` section to state.md. This is the **only section the Test agent reads**.
 
 ```markdown
 ### Build: Final

package/skills/wk-build/{stages → steps}/commit.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Create clean commits, push branch, create PR."
+description: "Build step: Create clean commits, push branch, create PR."
 ---
 
 # Commit

package/skills/wk-build/{stages → steps}/core.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Make failing tests pass — service layer, API, business logic (TDD green phase)."
+description: "Build step: Make failing tests pass — service layer, API, business logic (TDD green phase)."
 ---
 
 # Core — Make Tests Pass
@@ -42,8 +42,8 @@ description: "Build sub-stage: Make failing tests pass — service layer, API, b
 ## Rules
 
 - Write the **minimum** code to pass tests — no gold-plating
-- Don't refactor yet — that's the Refactor sub-stage
-- Don't build UI yet — that's the UI sub-stage
+- Don't refactor yet — that's the Refactor step
+- Don't build UI yet — that's the UI step
 - If a test expectation seems wrong, fix the test only if the Blueprint supports it
 - Match existing code patterns exactly — naming, file structure, error handling
 

package/skills/wk-build/{stages → steps}/integration.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Wire everything together, verify full data flow end-to-end."
+description: "Build step: Wire everything together, verify full data flow end-to-end."
 ---
 
 # Integration
@@ -49,4 +49,4 @@ description: "Build sub-stage: Wire everything together, verify full data flow e
 |--------|---------|
 | "Unit tests passing means integration is fine" | Unit tests mock boundaries. Integration failures live at the boundaries — where your code meets the database, API, or UI layer. |
 | "I already verified data flow during Core" | Core verified that individual pieces work. Integration verifies they work together. A function that passes its unit test can still send the wrong data shape to the next function. |
-| "Integration testing is the Test phase's job" | The Test phase runs automated suites. This sub-stage verifies that the pieces you just built actually connect. Finding a wiring bug here takes 5 minutes; finding it in Test takes 30. |
+| "Integration testing is the Test phase's job" | The Test phase runs automated suites. This step verifies that the pieces you just built actually connect. Finding a wiring bug here takes 5 minutes; finding it in Test takes 30. |

package/skills/wk-build/{stages → steps}/migration.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Generate and verify database schema changes."
+description: "Build step: Generate and verify database schema changes."
 ---
 
 # Migration

package/skills/wk-build/{stages → steps}/red.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Write failing tests BEFORE implementation (TDD red phase)."
+description: "Build step: Write failing tests BEFORE implementation (TDD red phase)."
 ---
 
 # Red — Write Failing Tests

package/skills/wk-build/{stages → steps}/refactor.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Improve code quality while keeping all tests green (TDD refactor phase)."
+description: "Build step: Improve code quality while keeping all tests green (TDD refactor phase)."
 ---
 
 # Refactor

package/skills/wk-build/{stages → steps}/setup.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Branch creation, dependency installation, scaffolding."
+description: "Build step: Branch creation, dependency installation, scaffolding."
 ---
 
 # Setup

package/skills/wk-build/{stages → steps}/ui.md

@@ -1,5 +1,5 @@
 ---
-description: "Build sub-stage: Implement UI components, pages, and interactions."
+description: "Build step: Implement UI components, pages, and interactions."
 ---
 
 # UI

package/skills/wk-deploy/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: deploy
-description: "Run the Deploy phase (optional) — 3 sub-stages: Merge, Monitor, Remediate."
+description: "Run the Deploy phase (optional) — 3 steps: Merge, Monitor, Remediate."
 user-invocable: false
 allowed-tools: Bash, Read, Write, Edit, Glob, Grep
 ---
 
 You are the **Release Engineer**. Get this PR merged and deployed safely.
 
-## Sub-stages (in order)
+## Steps (in order)
 
 1. **Merge** — Get the PR merged safely
 2. **Monitor** — Watch for deployment issues
@@ -15,11 +15,11 @@ You are the **Release Engineer**. Get this PR merged and deployed safely.
 
 ## Execution
 
-For each sub-stage:
-1. Read the sub-stage file (e.g., `.claude/skills/wk-deploy/stages/merge.md`)
+For each step:
+1. Read the step file (e.g., `.claude/skills/wk-deploy/steps/merge.md`)
 2. Follow its instructions
 3. Update `.work-kit/state.md` with outputs
-4. Proceed to next sub-stage
+4. Proceed to next step
 
 ## Key Principle
 
@@ -63,7 +63,7 @@ This phase runs as a **fresh agent**. Read only these sections from `.work-kit/s
 
 ## Final Output
 
-After all sub-stages are done, append a `### Deploy: Final` section to state.md. This is what **Wrap-up reads**.
+After all steps are done, append a `### Deploy: Final` section to state.md. This is what **Wrap-up reads**.
 
 ```markdown
 ### Deploy: Final

package/skills/wk-deploy/{stages → steps}/merge.md

@@ -1,5 +1,5 @@
 ---
-description: "Deploy sub-stage: Get the PR merged safely."
+description: "Deploy step: Get the PR merged safely."
 ---
 
 # Merge

package/skills/wk-deploy/{stages → steps}/monitor.md

@@ -1,5 +1,5 @@
 ---
-description: "Deploy sub-stage: Monitor deployment after merge."
+description: "Deploy step: Monitor deployment after merge."
 ---
 
 # Monitor

package/skills/wk-deploy/{stages → steps}/remediate.md

@@ -1,5 +1,5 @@
 ---
-description: "Deploy sub-stage: Handle deployment outcome — confirm success or manage failure."
+description: "Deploy step: Handle deployment outcome — confirm success or manage failure."
 ---
 
 # Remediate

package/skills/wk-plan/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: plan
-description: "Run the Plan phase — 8 sub-stages from Clarify to Audit."
+description: "Run the Plan phase — 8 steps from Clarify to Audit."
 user-invocable: false
 allowed-tools: Bash, Read, Write, Edit, Glob, Grep
 ---
 
-You are the **Planning Lead**. Work through 8 focused sub-stages to produce a complete, executable Blueprint.
+You are the **Planning Lead**. Work through 8 focused steps to produce a complete, executable Blueprint.
 
-## Sub-stages (in order)
+## Steps (in order)
 
 1. **Clarify** — Understand the request, define acceptance criteria, clarify requirements
 2. **Investigate** — Read codebase, trace paths, map blast radius
@@ -20,20 +20,20 @@ You are the **Planning Lead**. Work through 8 focused sub-stages to produce a co
 
 ## Execution
 
-For each sub-stage:
-1. Read the sub-stage file (e.g., `.claude/skills/wk-plan/stages/clarify.md`)
+For each step:
+1. Read the step file (e.g., `.claude/skills/wk-plan/steps/clarify.md`)
 2. Follow its instructions completely
-3. Write outputs to `.work-kit/state.md` under a section for that sub-stage
-4. Update `**Phase:** plan` and `**Sub-stage:** <current>` in state.md
-5. Proceed to the next sub-stage
+3. Write outputs to `.work-kit/state.md` under a section for that step
+4. Update `**Phase:** plan` and `**Step:** <current>` in state.md
+5. Proceed to the next step
 
 ## Continuity
 
-Maintain context across all sub-stages — each builds on the previous. Reference prior outputs explicitly. Don't re-discover what you already found.
+Maintain context across all steps — each builds on the previous. Reference prior outputs explicitly. Don't re-discover what you already found.
 
 ## Recording
 
-Throughout every sub-stage, capture two things in the shared state.md sections:
+Throughout every step, capture two things in the shared state.md sections:
 
 - **`## Decisions`** — Whenever you choose between real alternatives, append: `**<context>**: chose <X> over <Y> — <why>`. Skip obvious choices.
 
@@ -49,7 +49,7 @@ If **Audit** returns "revise":
 
 ## Final Output
 
-After all sub-stages are done, append a `### Plan: Final` section to state.md. This is the **only section the Build agent reads** — it must be self-contained.
+After all steps are done, append a `### Plan: Final` section to state.md. This is the **only section the Build agent reads** — it must be self-contained.
 
 ```markdown
 ### Plan: Final
@@ -57,10 +57,10 @@ After all sub-stages are done, append a `### Plan: Final` section to state.md. T
 **Verdict:** ready | revised_with_caveats
 
 **Blueprint:**
-<the full ordered implementation plan from Blueprint sub-stage — copy it here>
+<the full ordered implementation plan from Blueprint step — copy it here>
 
 **Architecture:**
-<data model, API surface, components, service layer — from Architecture sub-stage>
+<data model, API surface, components, service layer — from Architecture step>
 
 **Criteria:**
 <reference to ## Criteria section>

package/skills/wk-plan/{stages → steps}/architecture.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Define technical design — data model, API surface, component structure."
+description: "Plan step: Define technical design — data model, API surface, component structure."
 ---
 
 # Architecture

package/skills/wk-plan/{stages → steps}/audit.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Audit the Blueprint for gaps, contradictions, and coverage."
+description: "Plan step: Audit the Blueprint for gaps, contradictions, and coverage."
 ---
 
 # Audit
@@ -9,7 +9,7 @@ description: "Plan sub-stage: Audit the Blueprint for gaps, contradictions, and
 
 ## Instructions
 
-1. Re-read ALL prior sub-stage outputs (Clarify through Blueprint)
+1. Re-read ALL prior step outputs (Clarify through Blueprint)
 2. Check for:
    - **Gaps:** Steps missing that are needed to satisfy criteria
    - **Contradictions:** Blueprint says X but Architecture says Y

package/skills/wk-plan/{stages → steps}/blueprint.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Produce a full ordered step-by-step implementation plan."
+description: "Plan step: Produce a full ordered step-by-step implementation plan."
 ---
 
 # Blueprint
@@ -9,7 +9,7 @@ description: "Plan sub-stage: Produce a full ordered step-by-step implementation
 
 ## Instructions
 
-1. Synthesize ALL prior sub-stage outputs (Clarify → Architecture) into one executable plan
+1. Synthesize ALL prior step outputs (Clarify → Architecture) into one executable plan
 2. Order steps by dependency — what must be done first
 3. Each step must specify:
    - What to do (create file, modify function, run command)

package/skills/wk-plan/{stages → steps}/clarify.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Understand the request, define acceptance criteria, and clarify requirements."
+description: "Plan step: Understand the request, define acceptance criteria, and clarify requirements."
 ---
 
 # Clarify

package/skills/wk-plan/{stages → steps}/investigate.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Read codebase systematically, trace paths, map blast radius."
+description: "Plan step: Read codebase systematically, trace paths, map blast radius."
 ---
 
 # Investigate

package/skills/wk-plan/{stages → steps}/scope.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Define in/out scope, estimate complexity, refine criteria."
+description: "Plan step: Define in/out scope, estimate complexity, refine criteria."
 ---
 
 # Scope

package/skills/wk-plan/{stages → steps}/sketch.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Produce a rough directional plan based on investigation findings."
+description: "Plan step: Produce a rough directional plan based on investigation findings."
 ---
 
 # Sketch

package/skills/wk-plan/{stages → steps}/ux-flow.md

@@ -1,5 +1,5 @@
 ---
-description: "Plan sub-stage: Define user-facing flows, screens, interactions, edge cases."
+description: "Plan step: Define user-facing flows, screens, interactions, edge cases."
 ---
 
 # UX Flow