Create comprehensive implementation plan for a feature
Creates comprehensive implementation plans with Linear issue hierarchies, acceptance criteria, and workflow guidance.
/plugin marketplace add greyhaven-ai/claude-code-config/plugin install linear@grey-haven-pluginsfeature description or requirementsCreate comprehensive implementation plan: $ARGUMENTS
<ultrathink> Think deeply about requirements. Break down into actionable plan. Every detail for successful implementation. </ultrathink> <megaexpertise type="technical-architect"> The assistant should use structured planning with Linear integration and complete issue hierarchy with clear acceptance criteria. </megaexpertise> <context> Planning implementation for: $ARGUMENTS Need detailed, actionable plan with measurable outcomes </context> <requirements> - Extract all requirements (functional, non-functional, constraints) - Consider edge cases and error scenarios - Create Linear issue hierarchy - Define acceptance criteria - Include time estimates with buffer - Map dependencies - Assess risks </requirements> <actions> 1. Analyze requirements thoroughly → extract explicit and implicit needs 2. Check for existing projects → mcp_linear.list_projects(teamId, includeArchived=false) 3. Create or use project → mcp_linear.create_project(name="[Feature] $ARGUMENTS", description="Implementation tracking") 4. Create comprehensive issues within project: - Architecture & Design Issue: Technical design, data models, API contracts - Core Implementation Issue: Complete functionality with detailed breakdown - Error Handling Issue: Comprehensive scenarios and recovery strategies - Testing Strategy Issue: Unit, integration, e2e test plans - Documentation Issue: API docs, user guides, technical documentation - Performance Issue: Benchmarks, optimization strategies, monitoring - Security Issue: Auth implementation, validation, data protection 5. Each issue includes: - Detailed scope and requirements - Acceptance criteria checklist - Time estimate with buffer - Dependencies clearly mapped - Technical implementation notes - Links to project for context 6. Generate workflow: - Branch names per issue (using Linear's git branch names) - Implementation order with dependencies - Commit templates with magic words (use actual team ID like ENG, DES, CVIREC): - "Refs [TEAM]-123" for progress commits (links without closing) - "Fixes [TEAM]-123" for completing issues (auto-closes on merge) - Branch names should include issue ID for auto-linking - PR checklist with Linear integration 7. Output summary: project URL, issue list with IDs, implementation order, risk assessment, success metrics </actions>This plan guides entire implementation. The assistant should be thorough, specific, actionable and include all technical details and considerations.
Take a deep breath in, count 1... 2... 3... and breathe out. The assistant is now centered and should not hold back but give it their all.