How this skill is triggered — by the user, by Claude, or both
Slash command
/vk:create-planThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating a structured development plan based on a PRD. This plan will serve as:
You are creating a structured development plan based on a PRD. This plan will serve as:
Check for PRD files by listing docs/*.md.
Check if docs/development-plan.md already exists.
Read the PRD - If you haven't already reviewed it, read the PRD file in docs/
Check for existing VibeKanban project - Use list_projects to see if a project already exists for this work
Organize into Epics - Group related work into epics (major feature areas or milestones):
Note: Adjust epic names and count based on the project's needs. Each epic should represent a cohesive body of work.
Break down into tasks - Each task should be:
S (Small, <1hr), M (Medium, 1-4hrs), L (Large, 4-8hrs), XL (Extra Large, 8hrs+)1.1, 1.2 or — for none)Identify dependencies - For each task, determine if it depends on other tasks being completed first. Dependencies can be within the same epic or across epics. Use task IDs to reference dependencies.
Write task-level acceptance criteria - After each task table, add a ### Task Details section with specific, testable acceptance criteria for every task. Each task should have 2-4 concrete criteria that define "done" -- these should be verifiable actions (e.g., "API returns 200 for valid input", "Unit tests pass", "Config file is created at path X"), not vague statements.
Define epic-level acceptance criteria - Each epic should have clear acceptance criteria that represent the overall goal of the epic
Create the plan file - Write to docs/development-plan.md
Note: The task table provides a scannable overview; the Task Details section below it provides the depth needed for execution. Both are required.
Use this exact format for the development plan:
# Development Plan: [Project Name]
> **Generated from:** docs/[prd-filename].md
> **Created:** [date]
> **Last synced:** [date]
> **Status:** Active Planning Document
> **VibeKanban Project ID:** [To be assigned]
## Overview
[2-3 sentence summary of what we're building]
## Tech Stack
- **Backend:** [technologies]
- **Frontend:** [technologies]
- **Database:** [technologies]
- **Infrastructure:** [technologies]
---
## Completion Status Summary
| Epic | Status | Progress |
|------|--------|----------|
| 1. [Epic Name] | Not Started | 0% |
| 2. [Epic Name] | Not Started | 0% |
| 3. [Epic Name] | Not Started | 0% |
---
## Epic 1: [Epic Name] (NOT STARTED)
[Brief description of this epic's purpose]
### Acceptance Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
### Tasks
| ID | Title | Description | Priority | Complexity | Depends On | Status |
|----|-------|-------------|----------|------------|------------|--------|
| 1.1 | [Task title] | [Description] | High | S | — | <!-- vk: --> |
| 1.2 | [Task title] | [Description] | Medium | M | 1.1 | <!-- vk: --> |
| 1.3 | [Task title] | [Description] | Low | S | — | <!-- vk: --> |
### Task Details
**1.1 - [Task title]**
- [ ] [Specific, testable criterion - e.g., "Project builds with no errors"]
- [ ] [Specific, testable criterion - e.g., "Folder structure matches convention: src/, tests/, docs/"]
- [ ] [Specific, testable criterion - e.g., "README includes setup instructions"]
**1.2 - [Task title]**
- [ ] [Specific, testable criterion - e.g., "Database migrations run successfully"]
- [ ] [Specific, testable criterion - e.g., "Connection pool configured with env vars"]
**1.3 - [Task title]**
- [ ] [Specific, testable criterion]
- [ ] [Specific, testable criterion]
---
## Epic 2: [Epic Name] (NOT STARTED)
[Brief description]
### Acceptance Criteria
- [ ] [Criterion 1]
### Tasks
| ID | Title | Description | Priority | Complexity | Depends On | Status |
|----|-------|-------------|----------|------------|------------|--------|
| 2.1 | [Task title] | [Description] | High | M | 1.1, 1.2 | <!-- vk: --> |
### Task Details
**2.1 - [Task title]**
- [ ] [Specific, testable criterion - e.g., "API endpoint returns 200 for valid request"]
- [ ] [Specific, testable criterion - e.g., "Unit tests cover happy path and error cases"]
- [ ] [Specific, testable criterion - e.g., "Input validation rejects malformed data"]
---
[Continue for all epics...]
---
## Dependencies
- [External dependency 1]
- [External dependency 2]
## Out of Scope
- [Item explicitly not included]
## Open Questions
- [ ] [Any remaining questions to resolve]
## Related Documents
| Document | Purpose | Status |
|----------|---------|--------|
| docs/[prd].md | Product Requirements | Current |
---
## Changelog
See [development-plan-changelog.md](development-plan-changelog.md) for full history.
Also create docs/development-plan-changelog.md with:
# Development Plan Changelog
> Changes to `docs/development-plan.md` are logged here.
- **[date]**: Initial development plan created from PRD
<!-- vk: --> comment in the Status column is a placeholder for VibeKanban task IDs (populated by /vk:generate-tasks)NOT STARTED, IN PROGRESS, COMPLETEHigh, Medium, LowS (Small, <1hr), M (Medium, 1-4hrs), L (Large, 4-8hrs), XL (Extra Large, 8hrs+). These are rough estimates to help with sprint planning and task selection.— for tasks with no dependencies. Dependencies can cross epic boundaries (e.g., task 2.1 can depend on 1.3).After creating the plan, inform the user:
docs/development-plan.md/vk:generate-tasks to create VibeKanban tasks/vk:sync-plan anytime to sync status between the plan and VibeKanban/vk:plan-status for a quick progress overviewGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub materemias/claude-vibekanban-plugin --plugin vk