planning-and-slicing

GodSpeedAI's avatarfrom GodSpeedAI

Breaks high-level goals into an incremental, prioritised plan using the plan template.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026
[Project Management]

When & Why to Use This Skill

The Planning and Slicing skill empowers Claude to transform high-level objectives into structured, actionable project roadmaps. By leveraging standardized templates, it systematically decomposes complex goals into prioritized milestones and granular tasks, ensuring architectural consistency and mitigating delivery risks through incremental progress tracking.

Use Cases

  • Software Development Roadmapping: Decomposing a complex feature request into a series of small, testable milestones for incremental deployment and continuous delivery.
  • Project Scoping and Documentation: Automatically converting raw product requirements into a detailed PLAN.md that includes risk assessment, resource allocation, and clear acceptance criteria.
  • Architectural Alignment: Ensuring new project plans remain consistent with existing system constraints by analyzing PRODUCT.md and ARCHITECTURE.md before execution.
  • Risk Mitigation: Identifying technical and operational dependencies early in the planning phase to define effective mitigation strategies.
nameplanning-and-slicing
description'Breaks high-level goals into an incremental, prioritised plan using the plan template.'
idce.skill.planning-and-slicing
tags[planning, architecture, context-min]
files[]
concepts[milestones]
tools[toolset:read]
artifacts[ce.prompt.create-plan]
actions[produce-plan]

Planning and Slicing Skill

Use this skill to convert agreed requirements into an actionable plan that can be executed in incremental steps.

Steps

  1. Load templates and context. Read plan-template.md to understand the structure of a plan (goals, requirements, milestones, risks, tools, acceptance criteria). Load PRODUCT.md and ARCHITECTURE.md to ensure alignment with product vision and system constraints.

  2. List goals and requirements. Start by restating the goals and summarising the confirmed requirements. Group related requirements together.

  3. Identify milestones. Break the work into logical milestones or slices. Each milestone should deliver user value, be testable and small enough to complete within a short time frame. Order milestones based on dependencies and risk.

  4. Assign tasks and resources. For each milestone, outline the tasks needed (design, implementation, testing, documentation). Note which files or modules will be touched and which skills or prompts will be used.

  5. Document risks and assumptions. Capture potential risks (technical, operational, dependency) and assumptions. Define mitigation strategies where possible.

  6. Define acceptance criteria. For each milestone, specify what constitutes success. Use measurable outcomes to guide implementation and review.

  7. Record the plan. Fill out a new plan document based on plan-template.md, inserting the structured information in the appropriate sections. Save the plan as PLAN.md or return it to the user for storage.

  8. Review with stakeholders. Present the plan to the user or team for feedback. Iterate until consensus is reached before moving to implementation.

Careful planning and slicing lead to predictable delivery and reduce the likelihood of scope overruns or architectural misalignment.