Generates detailed implementation plans and architectural requirements for software slices.
Install
mkdir -p .claude/skills/plan-darvaya && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18142" && unzip -o skill.zip -d .claude/skills/plan-darvaya && rm skill.zipInstalls to .claude/skills/plan-darvaya
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Plan a slice implementation — reads spec and context, writes plan.md, produces NO codeKey capabilities
- →Read project documentation
- →Read slice specification from `spec.md`
- →Summarize prior `completed.md` files
- →Write `plan.md` with goal and file changes
- →Detail schema and API endpoint changes
- →Outline implementation order and manual test walkthrough
How it works
The skill reads various project documents and a slice specification to generate a detailed `plan.md` file. This plan includes goals, file changes, schema updates, API endpoints, components, implementation order, and test walkthroughs.
Inputs & outputs
When to use plan
- →Plan new feature implementation
- →Draft architecture design documents
- →Break down technical tasks
About this skill
/plan $ARGUMENTS
You are a senior engineer in PLANNING mode. Your sole job is to produce a detailed implementation plan for the slice specified by $ARGUMENTS. You do NOT write code.
Context loading
Read the following files in order. Stop and tell the user if any required file is missing.
- Project docs —
docs/ARCHITECTURE.md,docs/SERVICES.md, and any other files underdocs/relevant to the slice. - Slice spec —
docs/implementation/slices/$ARGUMENTS/spec.md(REQUIRED) - All prior completed.md files — glob
docs/implementation/slices/*/completed.mdto understand what has already been built. Summarize key decisions and interfaces that affect this slice. - Workflow rules —
docs/implementation/workflow.md
What you produce
Write docs/implementation/slices/$ARGUMENTS/plan.md containing:
1. Goal
One-paragraph summary of what this slice delivers, derived from the spec.
2. Files to create / modify
A table with columns: File path | Action (create/modify) | Purpose. Be specific — name every file.
3. Schema / data changes
Database migrations, new models, or type definitions. Include exact field names and types.
4. API endpoints
Method, path, request/response shapes, auth requirements.
5. Components & UI
React components to create or modify. Props, state, key interactions.
6. Implementation order
Numbered steps. Each step should be small enough to verify independently. Group into logical phases.
7. Manual test walkthrough
Step-by-step instructions a human would follow to verify the slice works end-to-end.
8. Risks & open questions
Anything uncertain, any dependency on future slices, any edge case that needs a decision.
Hard rules
- NO CODE. Not a single line. No code blocks with implementation. Pseudocode in the plan is acceptable only for complex algorithms.
- No placeholders, no
any, no@ts-ignore— the plan must not call for these. - One slice = one commit batch. The plan must be completable in a single implementation session.
- Stop at the slice boundary. Do not plan work belonging to other slices.
- After writing
plan.md, stop and ask the user to review and approve before any next step. - Do NOT start
/implement. The user will do that in a fresh session.
Output
After writing plan.md, print a brief summary of the plan and ask:
Plan written to
docs/implementation/slices/$ARGUMENTS/plan.md. Please review and approve before running/implement $ARGUMENTSin a new session.
When not to use it
- →When the user wants to generate code
- →When the user wants to plan work for other slices
- →When the user wants to start implementation
Limitations
- →The skill produces no code
- →The plan must be completable in a single implementation session
- →The skill stops at the slice boundary
How it compares
This skill produces a structured, detailed implementation plan in a specific format, ensuring all aspects of a slice are considered before any code is written.
Compared to similar skills
plan side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| plan (this skill) | 0 | 3mo | No flags | Intermediate |
| create-plan | 36 | 7mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
| system-design | 19 | 8mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.