spec-workflow

To structure a software development workflow, this skill implements requirement analysis, technical design, and task planning. It uses EARS syntax to establish clear, testable acceptance criteria for complex architecture and multi-module integration projects.

EARS syntax is a standardized method for writing testable software requirements. You should use it during the requirement analysis phase of a structured workflow to ensure high-quality, unambiguous acceptance criteria for new features or database schema changes.

To plan technical design and task breakdown, this skill facilitates detailed architecture planning and breaks down complex features into actionable tasks with status tracking. It guides the agent through solution design and implementation steps for multi-module integrations.

Yes, you can use this structured workflow for projects involving database schema changes and UI design. It applies to complex architecture designs and references UI design rules when necessary to guide the agent through requirement analysis and technical design.

No external dependencies are required to run this task planning workflow. It operates independently using its internal references component to guide the structured software engineering process from initial requirement analysis through to actionable task tracking.

Using a structured development workflow ensures thorough requirement analysis and robust technical design, preventing scope creep. Unlike ad-hoc methods, it standardizes task planning and execution using EARS syntax to maintain high-quality acceptance criteria.