project:plan
Project Plan
Breaks a project vision into individual specifications with clear boundaries, dependencies between them, and an optimal execution order. Produces a dependency graph and identifies shared interfaces that multiple specs will consume.
When to use
Use this skill when the user needs to:
- Break a large system into manageable, independent specs
- Define dependencies and execution order across specs
- Identify shared interfaces and contracts between modules
Instructions
Step 1: Read Project Vision
- Look for
.projects/<project-name>/vision.md - If the vision document does not exist, use the
AskUserQuestiontool to suggest runningproject:initfirst, with options like "Run project:init first", "I'll provide context manually" - Extract: goals, stakeholders, technical constraints, shared architectural decisions, system boundary
More from ikatsuba/skills
spec:design
Technical Design - generates architecture diagrams, interfaces, and data flow based on requirements and chosen research solutions. Use when designing how a feature will be built.
18git:amend
Amend Commit - modifies the last commit with staged changes or new message
15spec:requirements
Requirements Analysis - gathers requirements through structured questions and produces a requirements document with testable acceptance criteria. Use when starting a new feature spec or documenting requirements.
14spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
14git:commit
Smart Commit - stages all changes and creates a conventional commit
13spec:do-all
Execute All Tasks - runs all pending tasks from the tasks document, with parallel subtask execution when safe
9