sw-plan

Transform approved solution designs into ordered implementation-ready specifications and work plans with testable acceptance criteria.

9|1|Updated Feb 9, 2026

Search Tags:#planning #specification #acceptance criteria #agile #design to code #work breakdown

Ready to run

npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sw-plan
Source: https://github.com/Obsidian-Owl/specwright/tree/main/skills/sw-plan
Command: npx skills add https://github.com/Obsidian-Owl/specwright --skill sw-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms high-level designs into detailed, actionable specifications and work plans, ensuring every aspect of a feature is clearly defined and testable before implementation begins.

Core Features & Use Cases

Decomposition: Breaks down large designs into manageable, independently buildable work units.
Spec Generation: Creates clear, testable acceptance criteria for each work unit, including boundary conditions and error cases.
Plan Creation: Develops a task breakdown and file change map for the implementation phase.
Use Case: After a product designer approves a new feature's mockups and requirements, this Skill can automatically generate the detailed technical specifications and a phased rollout plan for the engineering team.

Quick Start

Use the sw-plan skill to break down the design in design.md into work units and generate acceptance criteria.

Frequently Asked Questions about sw-plan

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

FAQPage Schema

How do I break down a software design into actionable work units?▼

To break down a software design into actionable work units, you need to decompose approved designs into ordered, independently buildable tasks with testable acceptance criteria. This ensures every requirement is grounded in the original design artifacts.

How do I generate testable acceptance criteria for an agile specification?▼

Generating testable acceptance criteria for an agile specification involves creating clear boundaries and error cases for each decomposed work unit. This ensures all implementation requirements are clearly defined and testable before development begins.

What is the best way to create an implementation-ready work plan from a design?▼

Creating an implementation-ready work plan from a design requires transforming approved solution designs into a task breakdown and file change map. This grounds all requirements in design artifacts before handoff to the implementation phase.

Can I automatically generate technical specifications from approved mockups and requirements?▼

Yes, you can automatically generate technical specifications from approved mockups and requirements by transforming high-level designs into detailed, actionable specs. This develops a phased rollout plan and work breakdown for the engineering team.

Do I need an approved solution design before creating a technical work breakdown?▼

Yes, an approved solution design is required before creating a technical work breakdown. The decomposition process grounds all ordered work units and acceptance criteria in the original design artifacts to ensure accurate implementation handoff.