spec-workflow

Standardize software engineering workflows with requirement analysis, technical design, and task planning.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/dang0705/planting --skill spec-workflow-dang0705
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/dang0705/planting/tree/main/.agents/skills/spec-workflow
Command: npx skills add https://github.com/dang0705/planting --skill spec-workflow-dang0705

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured approach to software engineering workflows, ensuring high-quality requirement analysis, technical design, and task planning.

Core Features & Use Cases

  • Structured Development Workflow: Follow a standard process for requirement analysis, technical design, and task planning.
  • Enhanced Collaboration: Use EARS syntax for requirement descriptions and UI design rules for frontend pages.
  • Task Tracking: Keep task status updated in tasks.md and execute tasks independently while maintaining quality.
  • Use Case: When developing new features or complex architecture designs, this Skill helps ensure a consistent and high-quality outcome.

Quick Start

Initialize a new spec by creating a specs/spec_name/requirements.md file with detailed requirements.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
What is a structured software engineering workflow for new feature development?

A structured software engineering workflow standardizes new feature development by enforcing requirement analysis, technical design, and task planning. This approach ensures high-quality outcomes for complex architectures and multi-module integrations.

How do I write software requirements using EARS syntax?

To write software requirements using EARS syntax, you structure requirement descriptions within a `specs/spec_name/requirements.md` file. EARS syntax provides a standardized approach for enhanced collaboration and clear requirement analysis.

How do I track task status during a technical design workflow?

You track task status during a technical design workflow by updating a `tasks.md` file. This allows developers to execute tasks independently while maintaining development quality and monitoring progress.

Can I use this structured workflow for multi-module integration designs?

Yes, this structured workflow supports multi-module integration designs. It is specifically built to handle new features, complex architecture designs, and multi-module integrations while maintaining consistent, high-quality outputs.

Do I need UI design rules for frontend requirement analysis?

Yes, UI design rules are required for frontend pages within this requirement analysis workflow. Integrating UI design rules ensures that technical designs meet structured development standards for frontend implementations.