Where does this skill sit in the Lore development workflow?

It sits between /prep-plan and /implement, acting as a quality and granularity checkpoint that transforms a general plan into a specific task list.

How does the skill ensure task quality?

It employs a rejection gate for vague plans and a semantic gap analysis to identify ambiguous scope, unclear ownership, or missing validation data before generating tasks.

Does it integrate with existing documentation?

Yes, it automatically parses spec files and project goals to link specific requirement IDs to each task's justification section.

When should I use Plan Breakdown instead of direct implementation?

Use it for complex plans where tight scope control, validation checklists, and requirement traceability help prevent implementation errors or missed requirements.

Can I customize the generated tasks?

Yes, after generation, you can approve the tasks, edit the files directly to adjust scope or validation, or reject the breakdown to refine the original plan.

Plan Breakdown

Name: Plan Breakdown
Author: rjroy

byrjroy

•

Productivity & Workflow

Decomposes complex development plans into granular, validated task files for streamlined implementation and requirement traceability.

Plan Breakdown bridges the gap between high-level planning and code execution by transforming development plans into structured, actionable task files. Each generated task includes specific implementation details, concrete validation criteria, and direct traceability to original requirements or project goals. By enforcing logical boundaries and surfacing potential semantic gaps before coding begins, it ensures a more predictable and high-quality implementation workflow within the Lore development ecosystem, allowing developers to review task granularity before committing to changes.

Key Features

012 GitHub stars

02Concrete validation criteria generation to provide a clear definition of done.

03Automated task decomposition based on logical changes and concern separation.

04Requirement traceability linking every task back to its original spec or goal.

05Research-backed insights using lore-researcher to inform task splitting.

06Integrated gap analysis to surface semantic ambiguities or contradictions early.

Use Cases

01Breaking down a multi-file architectural change into a sequence of verifiable commits.

02Creating a reviewable implementation roadmap for complex features before execution.

03Ensuring every code change maps directly to a specific product requirement for compliance.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rjroy/vibe-garden plan-breakdown

For use in Claude.ai and ChatGPT

Download Skill