Agent skill · writing content · aiskillstore
project-planner
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.
Why this skill is useful
Generates structured project planning documents that provide specific templates and guidelines for software project requirements and design.
What it needs
About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Project Planner Skill 执行环境 路径类型 说明 --------- ------ 使用方式 此技能提供模板和指导，无需本地脚本执行 调用场景 当用户需要项目规划、需求文档、系统设计时自动激活 输出格式 Markdown 文档（requirements.md, design.md, tasks.md） 路径说明 无本地路径依赖：此技能生成文档模板，不涉及本地脚本执行 生成的文档：保存在执行命令时的当前目录（process.cwd()） 项目上下文：基于当前工作目录确定项目根目录 This skill provides templates and guidance for generating comprehensive project planning documents that serve as blueprints for AI-assisted implementation. Quick Start When a user wants to start a new project, generate three core documents: 1. Requirements Document - User stories with acceptance criteria 2. Design Document - Technical architecture and component specifications 3. Implementation Plan - Hierarchical task breakdown with requirement tracing Why Explicit Architectural Planning Works Setting clear roles, responsibilities, and deliverables upfront dramatically improves project outcomes: Benefits of Upfront Definition 1. Component Clarity - Defining all system components first prevents scope creep and ensures complete coverage 2. Data Flow Visibility - Mapping data movement early reveals integration complexities and performance bottlenecks 3. Integration Planning - Identifying all touchpoints upfront prevents surprise dependencies during implementation 4. Clear Boundaries - Explicitly stating what's in/out of scope focuses effort and prevents feature drift 5. Measurable Success - Specific goals and constraints enable objective progress tracking The Architect Mindset When acting as a Project Architect, approach planning with: Systems Thinking - See the whole before diving into parts Interface-First Design - Define contracts between components before internals Traceability Focus - Every requirement maps to design elements and tasks Constraint Awareness - Acknowledge limitations upfront to guide decisions Deliverable Orientation - Know exactly what artifacts you're producing Document Generation Workflow 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/project-planner--782cf1