spec-to-code

Plugin spec-to-code from marketplace my-agents in Procionegobbo/my-agents. Commands read from the repo's manifest — 29 days ago.

Skills (5)

• create-feature-builder

  Generate a repo-tailored <stack>-feature-builder agent for the STORIES pipeline. Use when the user asks to add a feature-builder, support a new stack, or scaffold the implementation agent for this repo.

• run-feature

  Take one spec all the way to STORIES/COMPLETED/: creates its stories (if not already created) and then runs every resulting <stack>-feature-builder, in dependency order, each through its independent code-reviewer gate — without the user invoking run-stage once per story. Use when the user wants a wh

• run-stage

  Run a spec-to-code pipeline stage (spec-builder, story-creator, or any <stack>-feature-builder) together with its independent review gate. Use whenever the user asks to run one of those agents, to review a spec/story/implementation, or to take a feature through the STORIES pipeline — including when

• status

  Report the current state of the STORIES/ pipeline for this project: every spec, its stage (draft or completed), how many stories are pending in TODO/ vs done in COMPLETED/, and any unresolved Review Notes left by spec-reviewer / story-reviewer. Read-only — no files are run, moved or written. Use whe

• stories-init

  Create the STORIES/ workspace the spec-to-code pipeline needs (SPECS/, TODO/, COMPLETED/ with .gitkeep files, and an empty COMPLETED.md), adding only what is missing. Use once per project, or when the STORIES folder is absent or incomplete.

Subagents (6)

• code-reviewer

  Reviewer for a story implementation: re-runs the test suite, checks every acceptance criterion is met and covered by a real test, and returns VERDICT: APPROVED or CHANGES_REQUESTED. Never edits code. Spawned by the run-stage skill as a feature-builder's blocking gate; can also be run standalone.

• laravel-feature-builder

  Pipeline producer for Laravel: implements one story from STORIES/TODO/ end-to-end with tests, then closes it out to STORIES/COMPLETED/. Launch it through the run-stage skill, which adds the blocking code-reviewer gate; invoking it directly closes the story out on self-review only.

• spec-builder

  Pipeline producer: expands a rough draft in STORIES/SPECS/ into a complete, implementation-ready spec, using the codebase as precedent. Launch it through the run-stage skill, which adds the spec-reviewer gate; invoking it directly skips the independent review.

• spec-reviewer

  Read-only reviewer: audits a spec in STORIES/SPECS/ against a fixed rubric and returns VERDICT: APPROVED or CHANGES_REQUESTED. Never edits. Spawned by the run-stage skill as spec-builder's review gate; can also be run standalone on an existing spec.

• story-creator

  Pipeline producer: slices a completed spec from STORIES/SPECS/ into ordered, INVEST-compliant stories in STORIES/TODO/ (<spec-name>-<NNN>-<story>.md, Gherkin criteria, spec reference). Launch it through the run-stage skill, which adds the story-reviewer gate; invoking it directly skips the independe

• story-reviewer

  Read-only reviewer: audits the stories for one spec (coverage, INVEST, drift from the spec, numbering, dependencies) and returns VERDICT: APPROVED or CHANGES_REQUESTED. Never edits. Spawned by the run-stage skill as story-creator's review gate; can also be run standalone.

Hooks (1)

• PreToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/allow_story_closeout.py"