Surveyverse Implementation Workflow

Announce at start: "Running implementation-workflow Stage N — [stage name]."

This skill governs implementation plan work for surveycore (and other surveyverse packages). Three stages, always in order:

1. Stage 1 — Draft: Write the implementation plan from the finalized spec
2. Stage 2 — Review: Adversarial batch pass; saves all issues to a file
3. Stage 3 — Resolve: Interactively work through issues and log decisions

After the plan is approved, hand off to:

• /r-implement — section-by-section with manual oversight between sections
• /auto-ship — fully autonomous: implements, commits, PRs, monitors CI, and merges each section without manual handoffs

digraph impl_stages {
    rankdir=LR;
    S1 [label="Stage 1\nDraft Plan", shape=box];
    S2 [label="Stage 2\nAdversarial Review", shape=box];
    S3 [label="Stage 3\nResolve + Log", shape=box];
    done [label="→ /r-implement\nor /auto-ship", shape=doublecircle];

    S1 -> S2;
    S2 -> S3 [label="issues found"];
    S2 -> done [label="clean"];
    S3 -> S2 [label="new issues\ndiscovered"];
    S3 -> done [label="all resolved"];
}

Stage Routing

Determine which stage the user wants from context. If unclear, use the AskUserQuestion tool:

question: "Which stage of the implementation workflow do you want to run?"
header: "Stage"
multiSelect: false
options:
  - label: "Stage 1 — Draft the plan"
    description: "Write the implementation plan from the finalized spec."
  - label: "Stage 2 — Adversarial review"
    description: "Full batch pass over the plan; saves all issues to a file."
  - label: "Stage 3 — Resolve issues"
    description: "Interactively work through the review file issue by issue."

Then read the corresponding reference file before doing anything else:

Task Granularity (Stage 1)

Each task in the plan should be one action (2–5 minutes). TDD sub-steps must be explicit steps, not collapsed into one: write the failing test → run to confirm failure → write minimal code → run to confirm passing → commit. This granularity lets r-implement work through tasks without ambiguity about what "done" means for each step.

Common Shortcuts to Resist

Rules in Context

Every stage works alongside — never instead of — these rule files:

File Locations

The {id} matches the feature branch identifier (e.g., phase-2, survey-srs).

Implementation plan:  plans/impl-{id}.md
Plan review:          plans/plan-review-{id}.md
Decisions log:        plans/decisions-{id}.md