Automate a phased software workflow from requirements analysis to task planning.
npx skills add https://github.com/sycsky/Soncho --skill spec-workflow-sycsky
Please help me install this Agent Skill. Skill: spec-workflow Source: https://github.com/sycsky/Soncho/tree/main/.codebuddy/rules/tcb/rules/spec-workflow-skill Command: npx skills add https://github.com/sycsky/Soncho --skill spec-workflow-sycsky
This Skill provides a structured, phase-driven workflow that guides teams through requirement analysis, technical design, and task planning, ensuring disciplined development and clear handoffs.
Begin Phase 1 by drafting the Requirements Document using EARS in specs/spec_name/requirements.md and obtaining user confirmation before proceeding.
High-intent search queries and answers about installing and using this skill.
EARS-based requirements design standardizes acceptance criteria to structure software development workflows. You need it when developing complex features or multi-module architectures to enforce disciplined requirements analysis before technical design.
Start a phase-driven workflow by drafting the Requirements Document using EARS in specs/spec_name/requirements.md. You must obtain explicit user confirmation of the requirements before proceeding to technical design and task planning.
Yes, this workflow applies to projects involving UI design and database considerations. It specifically integrates UI-design rule references for frontend-related requirements to govern the phased development process.
The best way to track progress is using built-in task tracking via specs and tasks files. This monitors feature development across enforced phase-by-phase workflows with mandatory user confirmations before phase transitions.
Yes, the workflow enforces phase-by-phase transitions with mandatory user confirmations. This ensures disciplined development from requirement analysis through technical design to task planning for clear handoffs.
Avoid a phase-driven workflow for simple, single-module updates not involving complex architectures or database considerations. It is designed for multi-module integrations requiring structured requirement analysis and task planning.
qlawmarqGenerate testable EARS-format requirements from project descriptions and steering context.
blueskies1818Write implementation plans with step-by-step instructions and test cases for software tasks.
tamziOrchestrate the Paperclip release process from canary to stable.
OmexITConvert PRD or design docs into epics, tickets, and acceptance criteria.
