spec-driven-delivery

Plugin spec-driven-delivery from marketplace dev-process in pdtl/dev-process. Commands read from the repo's manifest — 4 days ago.

Skills (8)

• issue-round

  The feedback loop for a product that exists and is being used — turn raw hands-on testing notes into a triaged, dispositioned round document, then into a phase of tasks. Capture, triage with evidence, human decides, promote, build, close. Triggers on "review the inbox", "triage these issues", "issue

• phase-gate

  The phase-boundary ritual — the checks that only work if something schedules them. Run before opening a phase's PR and before starting the next phase. Catches drift between the plan and the built tree, duplicate domain nouns, deferrals whose trigger has fired, gates that have gone blind, and defects

• project-bootstrap

  Set a new project up for spec-driven delivery — scaffold the docs/ artifacts, a lean CLAUDE.md, the working agreement, and the empty ledgers, so the pipeline and its gates have somewhere to write from day one. Triggers on "bootstrap this project", "set up the process", "new project setup", "scaffold

• spec-architect

  Transforms a refined spec into a technical implementation plan covering stack, architecture, data model, folder structure, and risks. Use after the spec is solid and before any code is written. Triggers on phrases like "create the plan", "architect this", "design the architecture", "turn this spec i

• spec-refiner

  Refines draft user stories and acceptance criteria into specs that are unambiguous, complete, and testable. Use when the user shares draft requirements, user stories, features, or acceptance criteria and wants them reviewed and rewritten. Triggers on phrases like "review this spec", "refine these re

• task-breakdowner

  Breaks a spec and architecture plan into discrete, ordered, testable implementation tasks. Use after the plan is approved and before implementation begins. Triggers on phrases like "create tasks", "break this into tasks", "task breakdown", "turn this plan into a task list", or when the user has both

• task-close

  Close a single task properly — gates by exit code, verify in the product not just the suite, tick the box, write the changelog line, log any compromise as a decision with a revisit trigger, and commit. Triggers on "close the task", "finish this task", "task is done", "commit this task", "wrap up T<n

• visual-pass

  Iterate on look and feel without regressing behaviour — checkpoint the functional layer, write an aesthetic brief, move every visual value into tokens, then change only tokens. Use when functionality is solid and the work is styling, theming, reskinning, spacing, typography, or a design refresh. Tri

Similar plugins