skills.rest
lxb031018
lxb031018COMMUNITY
Explore all skills by this author →
GitHub

spec-workflow

Standardize requirement analysis, technical design, and task planning with EARS acceptance criteria.

2|1|Updated Apr 3, 2026
Search Tags:#architecture#specification#requirements#acceptance criteria#technical design#task planning
One-click install
npx skills add https://github.com/lxb031018/qintu --skill spec-workflow-lxb031018
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/lxb031018/qintu/tree/main/.codebuddy/skills/spec-workflow
Command: npx skills add https://github.com/lxb031018/qintu --skill spec-workflow-lxb031018

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents implementation from starting before requirements and acceptance criteria are explicit, reducing rework and misalignment during complex feature or architecture changes.

Core Features & Use Cases

  • Requirements definition with EARS acceptance criteria: Turn unclear goals into testable user stories and “shall” statements for the system.
  • Structured design for cross-module changes: Establish architecture, module boundaries, and supporting decisions (data/API/security/testing) before coding.
  • Task planning with traceability: Break the design into reviewable, executable tasks mapped back to each requirement, and only execute after confirmation.

Quick Start

Ask the AI to create specs/<spec_name>/requirements.md with EARS-style acceptance criteria for your new feature.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I write EARS acceptance criteria for complex software requirements?▼

EARS acceptance criteria standardize requirement analysis by translating unclear goals into testable "shall" statements. This structured approach prevents implementation from starting before requirements are explicit, reducing rework during complex feature changes.

What is the best way to plan technical design for cross-module integrations?▼

Technical design for cross-module integrations requires establishing architecture and module boundaries before coding. Structured design standardizes supporting decisions for data, API, security, and testing to ensure alignment during multi-step product changes.

How do I break down technical design into executable tasks mapped to requirements?▼

Breaking down technical design into executable tasks requires traceability to map each task back to its original requirement. This structured task planning enforces explicit user confirmation gates before execution to prevent misalignment.

When do I need a phased output workflow for software architecture changes?▼

A phased output workflow is needed for multi-step product changes, cross-module integrations, and UI or database-heavy efforts. It enforces staged confirmation across requirements, design, and tasks before execution to reduce rework.

Does spec-workflow work for UI and database-heavy feature development?▼

Spec-workflow is designed for UI and database-heavy efforts by enforcing a phased output of requirements, design, and tasks. It applies EARS acceptance criteria and explicit confirmation gates to manage complex software workflows.

Related Skills

Explore More Software Engineering Skills→
fhltafhlta

guildops-prd-discovery

Transforms GuildOps feature concepts into structured, Spec Kit-ready PRDs with ambiguity checklist and template.

Community
Intermediate
AYin-ZAYin-Z
1

spec-workflow

Formalize feature work with requirements, design, and task planning phases.

Community
Advanced
Sheldon-92Sheldon-92
3

Architecture

Review system architecture for structural patterns, data flow, and module boundaries.

Community
Advanced
mcauduro0mcauduro0
1

agile-product-owner

Generate user stories and plan sprints with Python scripts.

Community
Intermediate