← ClaudeAtlas

project-plannerlisted

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.
428alexander9/claude-skills-marketplace · ★ 1 · AI & Automation · score 57
Install: claude install-skill 428alexander9/claude-skills-marketplace
# Project Planner Skill 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 - **Traceabili