create-slices

Propose and write ordered slices for end-to-end verification into .goodplan/slices/.

Updated Aug 27, 2026

Search Tags:#workflow #planning #architecture #claude #epics #slices #gp

Ready to run

npx skills add https://github.com/ian97531/goodplan --skill create-slices

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interactive planning for Claude-based projects to define and order slices that deliver end-to-end workflows, improving clarity and traceability across epics.

Core Features & Use Cases

Interactive dialogue that proposes, iterates, and writes an ordered set of slices.
Ensures each slice delivers a complete end-to-end flow that can be verified by running the code.
When an active epic exists, writes slices to the epic's slices/ directory; otherwise uses .goodplan/slices/.

Quick Start

Start by identifying your idea and run /define-slices to draft the initial slice plan.

Frequently Asked Questions about create-slices

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

FAQPage Schema

How do I plan end-to-end slices for an epic workflow?▼

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.

What is the best way to sequence slices to verify functionality?▼

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.

Do I need a specific environment to manage epic slices?▼

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/.

Can I define slice boundaries without an active epic?▼

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.

How does architecture influence slice planning?▼

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.

Why are slice boundaries important for workflow planning?▼

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.