spec-workflow

Guide requirements, design, and task planning for multi-module changes.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/mbpz/poetry-atlas-mp --skill spec-workflow-mbpz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/mbpz/poetry-atlas-mp/tree/main/.agents/skills/cloudbase/references/spec-workflow
Command: npx skills add https://github.com/mbpz/poetry-atlas-mp --skill spec-workflow-mbpz

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps manage medium-to-large changes by ensuring explicit requirements, technical design, and task planning before implementation, especially for complex and multi-module work.

Core Features & Use Cases

  • Structured Development Process: Guides through a 4-phase process including requirements, design, tasks, and execution.
  • Explicit Requirements: Assists in defining user stories and acceptance criteria in EARS style.
  • Design Documentation: Encourages detailed architecture and module boundary documentation.
  • Task Planning: Facilitates breaking down designs into specific, reviewable tasks.

Quick Start

Use the spec-workflow Skill to initiate a medium-to-large change by creating a requirements document for your project.

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I manage requirements and technical design for complex multi-module development?

Manage multi-module development by guiding the creation of explicit requirements, architecture documentation, and task plans. It structures work into requirements, design, tasks, and execution phases to clarify complex changes.

When do I need structured task planning for a software project?

Structured task planning is needed for medium-to-large changes with unclear acceptance criteria or architecture-heavy requests. It ensures explicit documentation and task breakdown before implementation begins.

How to write user stories and acceptance criteria for development workflows?

Write user stories and acceptance criteria using EARS style within the requirements phase. This approach defines explicit conditions for complex changes before technical design and task planning.

Can I use this for small code changes or bug fixes?

This targets medium-to-large changes requiring multi-module work and architecture documentation. Small changes with clear parameters do not need this explicit requirements and design planning process.

What is the best way to document architecture and module boundaries before implementation?

Document architecture and module boundaries during the design phase of the workflow. This phase encourages detailed documentation to support breaking down designs into specific, reviewable tasks.

Does spec-workflow require any specific project management dependencies?

No dependencies are required to use spec-workflow. It operates independently using included scripts and references to facilitate the structured development process.