spec-workflow_skill

Overview

This skill implements a standard software engineering workflow for requirement analysis, technical design, task planning, and execution. It enforces a phased process (Requirements → Design → Task Breakdown → Execution) with mandatory user confirmation at the end of each phase. Use it to produce high-quality, traceable specs, designs, and task lists for non-trivial features and architecture work.

How this skill works

The skill first captures and formalizes requirements using the EARS (Easy Approach to Requirements Syntax) format, including UI design rules when frontend work is involved. After requirements are confirmed, it produces a concise technical solution (architecture, tech stack, DB/interface design, tests, security) and then breaks that solution into tracked tasks. Each phase is saved to a dedicated spec folder and requires explicit user confirmation before proceeding.

When to use it

• Developing a new feature from scratch that requires clear acceptance criteria
• Designing complex architecture or multi-module integrations
• Planning projects involving database schema or frontend UI design
• Preparing implementation-ready task breakdowns for engineering teams
• Creating traceable specs and execution plans for serverless or cloud integrations

Best practices

• Always use EARS syntax for acceptance criteria: While <precondition>, when <trigger>, the <system> shall <response>
• Confirm design style and color palette in the requirements phase when UI is involved and reference the UI design rules
• Never skip phases or proceed without explicit user confirmation
• Save and version each artifact in specs/spec_name/{requirements,design,tasks}.md and keep task status updated
• Use the interactiveDialog tool to collect missing information or clarify ambiguous requirements

Example use cases

• Define requirements and acceptance criteria for a new authentication flow with multi-factor support
• Design a microservice integration between a serverless backend and a third-party API, then create implementation tasks
• Plan database schema and frontend pages for a multi-tenant dashboard with color/palette decisions
• Break down a migration project into tracked tasks with clear completion criteria and test strategy