Menu
Breaks high-level goals into an incremental, prioritised plan using the plan template.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Intelligently routes requests to the correct context instructions and documentation files. Use this skill to determine which AGENT.md, guide, or technical instruction file is most relevant for a user's request.
Scaffold API mocking infrastructure using Mountebank and Testcontainers for reliable integration testing.
Manage full-stack observability using Logfire (logging/tracing) and OpenObserve (storage/visualization).
Interface for managing the Temporal Database and AI system (ReDB + GGUF embeddings).
Spec-Driven Development workflow using VibesPro conventions
| name | planning-and-slicing |
| description | Breaks high-level goals into an incremental, prioritised plan using the plan template. |
| metadata | {"id":"ce.skill.planning-and-slicing","tags":["planning","architecture","context-min"],"inputs":{"files":["plan-template.md","PRODUCT.md","ARCHITECTURE.md"],"concepts":["milestones"],"tools":["toolset:read"]},"outputs":{"artifacts":[],"files":["PLAN.md"],"actions":["produce-plan"]},"dependsOn":{"artifacts":[],"files":["plan-template.md"]},"related":{"artifacts":["ce.prompt.create-plan"],"files":[]}} |
Use this skill to convert agreed requirements into an actionable plan that can be executed in incremental steps.
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.
List goals and requirements. Start by restating the goals and summarising the confirmed requirements. Group related requirements together.
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.
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.
Document risks and assumptions. Capture potential risks (technical, operational, dependency) and assumptions. Define mitigation strategies where possible.
Define acceptance criteria. For each milestone, specify what constitutes success. Use measurable outcomes to guide implementation and review.
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.
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.
