--- title: "spec-workflow" description: "Spec-driven development workflows for requirements, design, bug fixes, quick specs, task planning, and execution." canonical: https://agentpluginsdirectory.com/plugins/spec-workflow last-updated: 2026-09-21 --- # spec-workflow Spec-driven development workflows for requirements, design, bug fixes, quick specs, task planning, and execution. - Slug: spec-workflow - Publisher: Bao Dang - Repository: https://github.com/dtgbao/agent-skills - Manifest: plugins/spec-workflow/plugin.json - Version: 2.0.6 - License: MIT - Category (editorial): productivity - Skills: 9 (spec-bugfix, spec-design, spec-execute, spec-new, spec-quick, spec-requirements, spec-status, spec-tasks, steering-setup) - MCP servers: 0 - Stars: 0 - Repository created: 2026-07-02 - Repository last pushed: 2026-09-06 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/spec-workflow - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What spec-workflow does, in the publisher's words A plugin for spec-driven development, with four entry workflows routed through a single unified command: Every phase's logic lives in a skill (skills/ /SKILL.md). Each command (commands/.md) is a thin pointer that just tells Claude to read and follow the matching skill, commands exist purely for discoverable, predictable /name invocation; all the actual instructions live in one place. Add this repository as a marketplace, then install the plugin: - requirements.md opens with a Glossary defining the system and its key nouns (Application, Client, Protected_Route,...), so every acceptance criterion can say "THE SHALL..." instead of a vague "the system." In Design-First, the glossary reuses component names design.md already established. - design.md includes a Correctness Properties section when the feature has universal invariants worth property-based testing (e.g. rate limits, parsers, validators): each property states a "for any X, Y must hold" guarantee and traces back to requirement numbers. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/dtgbao/agent-skills/HEAD/plugins/spec-workflow/README.md ## Skills - spec-bugfix: Start the Bugfix Analysis phase for a bug, phase 1 of 3 (Bugfix Analysis → Design → Tasks). Use when the user reports a bug, asks to "fix this issue", "debug X", or wants a tracked bugfix spec. Produces bugfix.md capturing current (defective), expected (correct), and unchanged (must-not-regress) b… - spec-design: Produce a technical design: either derived from an approved requirements.md, started fresh as a Design-First entry point, or as the root-cause/fix design for a bugfix spec. Use when the user asks to design a feature, says "let's do the design phase", "/spec-design", "design a system that...", or w… - spec-execute: Implement one task (or the next available task) from an approved tasks.md. Use when the user says "/spec-execute", "implement task N", "start the next task", or "work on the spec" for a feature that already has an approved tasks.md. - spec-new: Start a new spec and pick the right workflow for it. Use when the user wants to start a new feature or fix, says "start a spec", "new feature", "let's build X", "I found a bug", or is unsure which spec workflow to use. Recommends Requirements-First, Design-First, Bugfix, or Quick Spec based on the… - spec-quick: Generate requirements.md, design.md, and tasks.md for a feature in one continuous pass with no approval gates between phases. Use when the user says "/spec-quick", "quick spec", wants to move fast on a small well-understood feature, or explicitly doesn't want to review each phase separately. - spec-requirements: Start Requirements-First on a new feature, revise an existing requirements.md, or derive requirements from an already-approved design.md (Design-First phase 2). Use when the user wants to plan a new feature, says "create a spec for X", "let's spec out X", or asks to update/revise requirements for a… - spec-status: Show the status of specs created with this workflow, which artifacts each has, task completion progress, and which workflow (Requirements-First, Design-First, Bugfix, or Quick Spec) it's using. Use when the user asks "what's the status of my specs", "show spec progress", "/spec-status", or names a… - spec-tasks: Convert an approved requirements.md+design.md, or bugfix.md+design.md, into a discrete, dependency-ordered implementation task list. Use when the user wants to plan tasks for a spec'd feature or bugfix, says "/spec-tasks" or "break this into tasks", or wants to revise an existing tasks.md. Requires… - steering-setup: Set up or refresh persistent project context for this spec-driven workflow. Use when the user asks to "set up steering", "initialize project context for specs", starts using this workflow for the first time in a repo, or when product/tech/structure context seems stale. Creates docs/steering/product… Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.