skills.rest
study-yang
study-yangCOMMUNITY
Explore all skills by this author →
GitHub

spec-workflow

Generates requirements, design, and task documents for multi-module feature development.

Updated May 14, 2026
Search Tags:#requirements#acceptance criteria#technical design#feature planning#task planning#ears#spec workflow
One-click install
npx skills add https://github.com/study-yang/Vieb-Coding-- --skill spec-workflow-study-yang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/study-yang/Vieb-Coding--/tree/main/%E5%BE%AE%E4%BF%A1%E5%B0%8F%E7%A8%8B%E5%BA%8F-%E5%BF%AB%E8%AE%B0/.codebuddy/skills/spec-workflow
Command: npx skills add https://github.com/study-yang/Vieb-Coding-- --skill spec-workflow-study-yang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Medium-to-large changes often start coding before requirements and acceptance criteria are explicit, leading to rework and misaligned outcomes. This Skill enforces a structured requirements-design-tasks workflow with staged user confirmation before implementation. ## Core Features & Use Cases - Requirements Phase: Produces specs/<spec_name>/requirements.md with user stories and EARS-style acceptance criteria. - Design Phase: Produces design.md covering architecture, data models, APIs, security, and testing strategy. - Task Planning & Execution: Produces tasks.md with an actionable checklist traceable back to requirements, updated as work progresses. - Use Case: When asked to build a new multi-module booking feature, the agent first writes EARS acceptance criteria, confirms the design with you, then implements against a tracked task list. ## Quick Start Ask the agent to plan the new feature using the spec workflow before writing any code.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I plan a large feature before writing code?▼

Use a spec workflow that splits the work into three phases: requirements with EARS acceptance criteria, a design document covering architecture and data models, and a task checklist. Confirm each phase with the user before moving to the next.

What are EARS acceptance criteria?▼

EARS (Easy Approach to Requirements Syntax) writes acceptance criteria as: While <precondition>, when <trigger>, the <system> shall <response>. This format makes requirements testable and unambiguous before implementation begins.

When should I skip the full spec workflow?▼

Skip it for small bug fixes with clear scope, one-file documentation updates, straightforward config changes, and tiny refactors where the user already gave exact implementation instructions. The workflow targets medium-to-large, multi-module work.

How do spec tasks stay traceable to requirements?▼

Each task in tasks.md links back to its source requirement using a _Requirement: N annotation. Task status is updated during execution, preserving traceability from every code change to a task to a requirement.

Does the spec workflow handle UI design work?▼

Yes, it directs the agent to pull in a companion ui-design skill early when the change includes end-user pages or visual decisions, and a data-model-creation skill for advanced data modeling needs.

Related Skills

Explore More Software Engineering Skills→
anthropicsanthropics
23.4k

write-spec

Generate structured PRDs and feature specifications from problem statements.

Official
Advanced
TencentCloudBaseTencentCloudBase
1.1k

spec-workflow

Generates requirements, design, and task documents for multi-module feature development.

Official
Intermediate
shinnytechshinnytech

postgresql-table-design

Design PostgreSQL database schemas with data types, indexing, and constraints.

Official
Advanced
busboom-software-studiobusboom-software-studio
1

oop

Apply small targeted changes directly on master with test suite runs.

Official
Intermediate