spec-workflow

Generate EARS-style requirements, design specs, and task plans in specs/ directories.

72|5|Updated Jan 22, 2026

Search Tags:#workflow #design #documentation #requirements #phases #task-management #EARS

Ready to run

npx skills add https://github.com/TencentCloudBase/skills --skill spec-workflow-tencentcloudbase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/TencentCloudBase/skills/tree/main/skills/spec-workflow
Command: npx skills add https://github.com/TencentCloudBase/skills --skill spec-workflow-tencentcloudbase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, phase-driven workflow for software engineering, enabling teams to capture requirements, craft design, and plan tasks with clear checkpoints and traceability.

Core Features & Use Cases

Phase-driven workflow: Enforces step-by-step progression with user confirmation between phases.
EARS-based requirements: Uses Easy Approach to Requirements Syntax for precise requirement descriptions.
Artifacts & traceability: Automatically documents requirements, designs, and task plans for archival in specs/ directories.
Use Case: When starting a complex feature, you can run Phase 1 to produce a requirements document, then Phase 2 for design, etc.

Quick Start

To begin, initiate Phase 1: Requirements Document and Acceptance Criteria Design, confirm with the user, then proceed to Phase 2 and Phase 3 as guided by the Skill.

Frequently Asked Questions about spec-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I structure software requirements for complex feature development?▼

Software requirements for complex features are structured using EARS-style syntax, producing formalized requirement descriptions saved as artifacts in specs/ directories for clear traceability.

What is the best way to manage phase-by-phase progress in software design?▼

Phase-by-phase progress is managed through a structured workflow that enforces step-by-step progression, requiring explicit user confirmations before advancing between requirement, design, and task planning phases.

Can I use EARS requirement syntax for multi-module architecture projects?▼

Yes, EARS requirement syntax applies directly to multi-module architecture and UI/data design projects, generating precise acceptance criteria and design specifications for formal archival.

How do I generate task breakdowns from design specifications?▼

Task breakdowns are generated during the task planning phase after requirement analysis and design are confirmed, automatically documenting the task plans into the specs/spec_name directories.

Does this workflow require user confirmation between documentation phases?▼

Yes, the workflow requires explicit user confirmations between each phase, ensuring validated requirements and design specs before proceeding to subsequent task planning and breakdown steps.