break-spec

Decomposes approved specs into phased vertical slices with lifecycle artifact handling.

10|Updated May 12, 2026
One-click install
npx skills add https://github.com/sandsower/beislid --skill break-spec-sandsower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: break-spec
Source: https://github.com/sandsower/beislid/tree/main/skills/break-spec
Command: npx skills add https://github.com/sandsower/beislid --skill break-spec-sandsower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved spec or PRD into an actionable implementation plan is error-prone: teams either build horizontal layers that never ship, or decompose work that should not be split. This Skill converts an approved spec or Work Contract into phased vertical slices with explicit scope gating. ## Core Features & Use Cases - Vertical slice phasing: Splits a feature into end-to-end phases that cut through UI, API, data, and tests, starting with a walking skeleton. - Scope classification gates: Routes multi_slice, project, atomic, single_pr, and unknown classifications differently, blocking decomposition until low-confidence classifications are approved. - Lifecycle actions: Runs configured break_spec_approved artifact and CLI actions from .beislid/workflow.md, writing structure files like plans/<feature>-structure.md with approval prompts and policy checks. - Use Case: After a settings revamp spec is approved, ask the agent to break it down; it identifies durable architectural decisions, phases the work into demoable slices, labels each phase HITL or AFK, and hands the structure off to blueprint. ## Quick Start Ask the agent to break the approved spec for the current ticket into phased vertical slices and write the structure artifact.

Frequently Asked Questions about break-spec

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

FAQPage Schema
How do I break a spec into implementation phases?▼

Provide the approved spec or Work Contract and ask for a breakdown. The skill loads the spec from plans/ paths or session context, identifies durable architectural decisions, then slices the work into vertical phases that each cut through UI, API, data, and tests.

What is a vertical slice in feature planning?▼

A vertical slice is a thin end-to-end phase delivering testable functionality across all layers rather than a horizontal layer like pure infrastructure setup. The first phase is the walking skeleton, and later phases widen the path.

When should a spec not be decomposed into slices?▼

Specs classified as atomic or single_pr should not be decomposed without explicit user approval, and unknown classifications route back to spec refinement. Project-scope work needs milestones and ownership boundaries approved before slice planning.

Does break-spec write planning files automatically?▼

Only when a break_spec_approved lifecycle action is configured in .beislid/workflow.md, or after explicit approval in standalone mode. Artifact writes prompt before overwriting existing files and default to plans/<feature>-structure.md.

What happens after the structure is approved?▼

The approved structure is handed off to the blueprint skill for the selected phase, along with any written lifecycle artifact path. Direct handoff to implement happens only when the user confirms the design is already approved.