Agent skill · product strategy · aiskillstore
project-planning
Generate initial project planning documents (PVS, ADR, Tech Spec, Roadmap) from a project concept description. Use when starting a new project, when docs/planning/ contains placeholder files, or when user requests project planning document generation.
Why this skill is useful
Generates project planning documents with specific templates and guidelines that the AI wouldn't reliably create on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Project Planning Skill Generate four essential planning documents to guide AI-assisted development. These documents maintain context coherence across coding sessions and prevent architectural drift. When to Use This Skill User describes a project concept and asks for planning documents Files in docs/planning/ show "Awaiting Generation" status User invokes /plan command with project description Starting development on a new feature requiring architectural decisions Output Documents Document Location Purpose ---------- ---------- --------- Project Vision & Scope docs/planning/project-vision.md What & Why - problem, solution, scope Technical Spec docs/planning/tech-spec.md How - architecture, data model, APIs Development Roadmap docs/planning/roadmap.md When - phased implementation plan Architecture Decision Record docs/planning/adr/adr-001-.md Key technical decisions with rationale Generation Process Step 1: Gather Project Context Before generating, collect: 1. Project description from user input 2. Technical constraints from pyproject.toml and existing code 3. Cookiecutter choices reflected in project structure Step 2: Generate Documents in Order Generate documents sequentially, as later documents reference earlier ones: 1. Project Vision & Scope - Establishes what we're building and why 2. Architecture Decision Record - Key technical choices based on PVS 3. Technical Implementation Spec - Detailed how-to based on ADRs 4. Development Roadmap - Implementation plan based on all above Step 3: Expert Review via Consensus After generating each document, use the zen-mcp-server consensus tool to get expert review: Review each document in order: 1. PVS → Must be READY before generating ADR 2. ADR → Must be READY before generating Tech Spec 3. Tech Spec → Must be READY before generating Roadmap 4. Roadmap → Must be READY before completing If any document NEEDS REVISION, incorporate feedback and re-review before proceeding. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/project-planning