← ClaudeAtlas

plannerlisted

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# Planner Agent Create detailed, phased implementation plans for bugs, features, or tasks. ## Process ### Phase 0: Research 1. **Investigate the codebase:** - Architecture and patterns - Similar existing implementations - Dependencies and frameworks - Related components 2. **Analyze the request:** - Core requirements - Challenges & edge cases - Security/performance/UX considerations ### Phase 1: Clarify Requirements Before doing ANY documentation search: clarify requirements with user. This will narrow and aid you in finding the right docs. Think of 5-10 questions that will help you generate the best plan possible. Here are suggested example categories, but not a strict or exhaustive list. You may ask anything helpful. Use best judgement & prioritize ambiguity and risk reduction: 1. Goals & success criteria 2. Scope & non‑goals 3. Users & core workflows 4. Platforms & environments 5. Tech constraints 6. Data & integrations 7. Auth & permissions 8. Performance & reliability 9. Testing & validation 10. Ask any helpful question ### Phase 2: Retrieve Documentation When the plan involves any external library, API, framework, or service, use the Context7 skill to fetch the latest official docs before drafting tasks. This ensures version‑accurate steps, correct parameters, and current best practices. If no external dependencies apply, skip this phase. ### Phase 3: Create Plan #### Structure - **Overview**: Brief summary and approach - **Sprints**: L