prd-stepperlisted

Execute the NEXT (or a named) story in a PRD tracker file end-to-end — read the story spec from the JSON, mark in_progress, decide spawn-vs-inline based on complexity, run required gates, update the tracker with completed_date and implementation_notes. Companion to `prd-creation`. Use when the user says "continue with <story-id>", "next PRD story", "execute <story>", "step through the PRD", "what's next on the PRD", or "let's do the next one". This skill governs execution once a PRD tracker JSON exists, however it originated — whether created directly by `prd-creation` or handed off from some other planning process. Batching multiple PRD stories in one session, when the user opts in, is a legitimate variant of this same mechanism, not a different one.
cobuchan/compounding-operator · ★ 0 · Code & Development · score 72

Install: claude install-skill cobuchan/compounding-operator

# PRD Stepper — Execute One Story End-to-End `prd-creation` defines the work; `prd-stepper` does the work. Given a PRD tracker JSON (or the active one referenced in `scratchpad.md`), this skill executes one story to completion — including dependency checks, agent spawning, gate enforcement, and tracker updates. ## When to invoke - User says: "continue with AUTH-002", "next story", "next PRD story", "execute the next story", "step through the PRD", "what's next on the PRD", "let's do the next one". - User says: "go ahead with <story-id>" — interpret as: execute that specific story. - Proactively after closing a story: ask "shall I continue with the next one?" if the next story's dependencies are met. ## What it does ### Step 1 — Locate the PRD tracker If the user didn't name a PRD file: 1. Read `scratchpad.md` for an "Active Plan" or "Current PRD" reference. 2. If multiple PRDs exist in `docs/plans/`, ask which one (use `AskUserQuestion`). 3. If no PRD exists, route the user to `prd-creation` instead. The tracker is the `.json` file (e.g. `docs/plans/auth-rework-prd.json`); the `.md` is the narrative and may be useful context but is not the source of truth for status. ### Step 2 — Pick the story - If the user named one (`AUTH-001`, `PDF-002`, etc.), use that. - Otherwise pick the first story in declared order where: - `status` ∈ {`pending`, `in_progress`} (resume in-progress before starting new) - all `depends_on` stories are `implemented` - `blocked_by` is nul