Propose and write ordered slices for end-to-end verification into .goodplan/slices/.
npx skills add https://github.com/ian97531/goodplan --skill create-slices
Please help me install this Agent Skill. Skill: create-slices Source: https://github.com/ian97531/goodplan/tree/main/skills/create-slices Command: npx skills add https://github.com/ian97531/goodplan --skill create-slices
Interactive planning for Claude-based projects to define and order slices that deliver end-to-end workflows, improving clarity and traceability across epics.
Start by identifying your idea and run /define-slices to draft the initial slice plan.
High-intent search queries and answers about installing and using this skill.
Planning end-to-end slices involves proposing and writing an ordered set of verifiable workflows through interactive dialogue. This process guides sequencing and goal-definition by loading existing architecture and decisions to shape slice boundaries.
Sequencing slices to verify functionality requires structuring each slice to deliver a complete end-to-end flow that can be tested by running the code. This ensures every slice builds upon previous work to validate the epic's overall architecture.
Managing epic slices requires the gp tool version 1.0.0 or higher and uses the .goodplan directory layout. When an active epic exists, slices are written to the epic's slices directory; otherwise, they default to .goodplan/slices/.
You can define slice boundaries without an active epic by writing the proposed ordered slices directly to the .goodplan/slices/ directory. The planning dialogue still loads references and architecture to shape these boundaries effectively.
Architecture directly shapes slice planning by providing the structural context needed to define boundaries and sequencing. The planning process loads architecture references and existing decisions to ensure each slice aligns with the overall system design.
Slice boundaries are important for workflow planning because they ensure each slice delivers a verifiable end-to-end flow. Properly scoped boundaries improve clarity and traceability across epics by breaking down complex architecture into manageable, testable units.
marcusgollAutomate epic scoping through structured questioning to populate epic-spec.md.
dayvidphamCoordinate vertical slice planning, worker assignment, and progress tracking.
NoizefieldConvert DSP plugin concept briefs into architecture.md and plan.md design documents.
kivo360Track and audit project changes across files, code, and repository history.
