skills.rest
baiyongping
baiyongpingCOMMUNITY
Explore all skills by this author →
GitHub

spec-workflow

Orchestrate a phase-gated software development workflow from requirements to task planning.

Updated Dec 24, 2025
Search Tags:#workflow#design#requirements#specifications#engineering#task-management#EARS
One-click install
npx skills add https://github.com/baiyongping/cowork-platform --skill spec-workflow-baiyongping
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/baiyongping/cowork-platform/tree/main/.claude/skills/spec-workflow
Command: npx skills add https://github.com/baiyongping/cowork-platform --skill spec-workflow-baiyongping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent feature development workflows, missing governance, and fragmented documentation across phases, which leads to delays, scope creep, and misaligned outcomes.

Core Features & Use Cases

  • Enforces a phase-gated, requirement-to-task workflow tailored for software engineering projects.
  • Supports EARS-based requirement drafting, design-phase alignment, and task breakdown with clear acceptance criteria.
  • Applies to feature development, architecture redesigns, multi-module integrations, and project planning with traceable artifacts.

Quick Start

Provide your project goals and confirm each phase before proceeding to the next.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I structure a software development workflow from requirements to task planning?▼

A structured software development workflow orchestrates the process from requirements to task planning by enforcing phase-by-phase design, requirement elicitation, and task breakdown with user confirmations at each stage to ensure traceability.

What is the best way to write requirements for feature development to avoid scope creep?▼

To avoid scope creep in feature development, draft requirements using EARS syntax and enforce phase-gated alignments, ensuring clear acceptance criteria and saving artifacts under specs/spec_name for traceable documentation.

How do I break down architecture design into tasks with clear acceptance criteria?▼

Break down architecture design into tasks by applying a phase-by-phase workflow that requires explicit user confirmations before proceeding, generating task breakdowns with clear acceptance criteria saved as traceable artifacts.

Can I use a phase-gated workflow for multi-module integration projects?▼

Yes, a phase-gated workflow applies to multi-module integration projects, architecture redesigns, and feature development, aligning phases and breaking down tasks while saving traceable artifacts under specs/spec_name.

Does this workflow approach support UI-design references for frontend engineering?▼

Yes, the workflow enforces UI-design references specifically when frontend engineering work is involved, ensuring that phase-by-phase design and task execution align with interface requirements.

Why do I need phase confirmations in a task-management workflow?▼

Phase confirmations are required in a task-management workflow to prevent inconsistent feature development and fragmented documentation, ensuring governance and alignment before proceeding to autonomous execution and task tracking.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
abdullahbeamabdullahbeam
2

execute-project

Automate project execution with progress tracking and task validation.

Community
Advanced
stericisherestericishere
1

(workflow) phase-2-design

Generate frontend design prompts and architecture proposals from PRDs.

Community
Advanced
xxyjxxyj

msx:spec

Generate EARS-formatted specification documents for AI model changes.

Community
Advanced