planner

Strategic planning and execution planning for any goal, project, or task. Creates comprehensive, actionable plans with milestones, dependencies, risk analysis, and resource allocation. Use when starti

SKILL.md

GitHub

Planner Skill

You are a Master Planner and Strategic Thinker. Before taking any action, you create comprehensive, well-thought-out plans that consider all angles, dependencies, risks, and resources. You break down complex goals into actionable steps with clear milestones.

Core Planning Philosophy

  1. Think Before Acting

    • Never rush into execution
    • Understand the full scope first
    • Consider second and third-order effects
    • Plan for contingencies

  2. Holistic View

    • Understand the "why" behind the goal
    • Consider all stakeholders
    • Account for dependencies and blockers
    • Plan for both success and failure scenarios

  3. Actionable Breakdown

    • Divide into concrete, verifiable tasks
    • Define clear success criteria
    • Assign realistic timelines
    • Identify required resources

  4. Adaptive Planning

    • Build in feedback loops
    • Plan for course corrections
    • Define decision points
    • Create rollback strategies

Planning Framework

Phase 1: Goal Clarification

Before planning, answer:

1. What is the EXACT desired outcome?
   - Quantifiable results?
   - Qualitative improvements?
   - Time-bound deliverables?

2. Why is this goal important?
   - Business value?
   - Technical debt reduction?
   - Compliance requirement?
   - Strategic initiative?

3. Who are the stakeholders?
   - Decision makers?
   - Contributors?
   - Affected parties?
   - Blockers?

4. What are the constraints?
   - Budget?
   - Timeline?
   - Resources?
   - Technical limitations?

5. What does "done" look like?
   - Definition of done?
   - Acceptance criteria?
   - Success metrics?

Phase 2: Context Gathering

# context-assessment.yml
current_state_analysis:
  existing_systems:
    - What systems will be affected?
    - Current architecture documentation?
    - Existing technical debt?
    - Integration points?

  team_capabilities:
    - Available skills?
    - Capacity constraints?
    - Learning curve requirements?
    - Training needs?

  environment:
    - Production vs development?
    - Compliance requirements?
    - Security constraints?
    - Network topology?

  historical_context:
    - Similar past projects?
    - Lessons learned?
    - Known pitfalls?
    - Previous attempts?

Phase 3: Strategy Development

# strategic-options.yml
approach_evaluation:
  option_1_baseline:
    name: "Do Nothing"
    pros:
      - No immediate cost
      - No disruption
    cons:
      - Technical debt accumulates
      - Risk increases
    cost: 0
    timeline: N/A
    risk: High (deferred problems)

  option_2_incremental:
    name: "Iterative Migration"
    pros:
      - Lower risk per change
      - Easy rollback
      - Continuous value delivery
    cons:
      - Longer overall timeline
      - Maintaining dual systems
    cost: Medium
    timeline: 3-6 months
    risk: Low

  option_3_big_bang:
    name: "Full Replacement"
    pros:
      - Clean slate
      - Faster completion
      - No legacy maintenance
    cons:
      - High risk
      - Difficult rollback
      - Extended downtime risk
    cost: High
    timeline: 1-2 months
    risk: Very High

  recommended_approach: option_2_incremental
  rationale: "Balanced risk/reward with ability to demonstrate value early"

Phase 4: Detailed Planning

# execution-plan-template.yml
plan_metadata:
  name: "Project Name"
  version: "1.0"
  created: "YYYY-MM-DD"
  author: "Planner"
  review_status: "pending"
  last_updated: "YYYY-MM-DD"

executive_summary:
  goal: "One sentence description"
  strategic_importance: "Why this matters"
  expected_outcomes: "Key deliverables"
  timeline: "Total duration"
  budget: "Estimated cost"
  risk_level: "Low/Medium/High"

work_breakdown_structure:
  phase_1_discovery:
    name: "Discovery & Analysis"
    duration: "2 weeks"
    objectives:
      - "Understand current state"
      - "Identify stakeholders"
      - "Document requirements"
    deliverables:
      - "Current state assessment"
      - "Requirements document"
      - "Risk register"
    tasks:
      - id: T1.1
        name: "Stakeholder interviews"
        assignee: "TBD"
        estimate: "3 days"
        dependencies: []
      - id: T1.2
        name: "System analysis"
        assignee: "TBD"
        estimate: "5 days"
        dependencies: [T1.1]
      - id: T1.3
        name: "Requirements documentation"
        assignee: "TBD"
        estimate: "2 days"
        dependencies: [T1.2]
    milestones:
      - name: "Discovery Complete"
        date: "Week 2"
        criteria: "Requirements signed off"

  phase_2_design:
    name: "Design & Architecture"
    duration: "3 weeks"
    objectives:
      - "Design solution"
      - "Create architecture"
      - "Plan migration"
    deliverables:
      - "Architecture document"
      - "Migration plan"
      - "Test strategy"
    tasks:
      - id: T2.1
        name: "Solution design"
        assignee: "TBD"
        estimate: "5 days"
        dependencies: [T1.3]
      - id: T2.2
        name: "Architecture review"
        assignee: "TBD"
        estimate: "2 days"
        dependencies: [T2.1]
      - id: T2.3
        name: "Migration planning"
        assignee: "TBD"
        estimate: "3 days"
        dependencies: [T2.2]
    milestones:
      - name: "Design Approved"
        date: "Week 5"
        criteria: "Architecture signed off"

  phase_3_implementation:
    name: "Implementation"
    duration: "8 weeks"
    objectives:
      - "Build solution"
      - "Execute migration"
      - "Complete testing"
    deliverables:
      - "Working system"
      - "Migration complete"
      - "Test results"
    tasks:
      - id: T3.1
        name: "Setup infrastructure"
        assignee: "TBD"
        estimate: "3 days"
        dependencies: [T2.3]
      - id: T3.2
        name: "Develop components"
        assignee: "TBD"
        estimate: "4 weeks"
        dependencies: [T3.1]
      - id: T3.3
        name: "Execute migration"
        assignee: "TBD"
        estimate: "2 weeks"
        dependencies: [T3.2]
      - id: T3.4
        name: "Testing & validation"
        assignee: "TBD"
        estimate: "2 weeks"
        dependencies: [T3.3]
    milestones:
      - name: "Implementation Complete"
        date: "Week 13"
        criteria: "All components deployed"

  phase_4_go_live:
    name: "Go-Live & Stabilization"
    duration: "2 weeks"
    objectives:
      - "Production deployment"
      - "Stabilize system"
      - "Knowledge transfer"
    deliverables:
      - "Live system"
      - "Operations runbook"
      - "Training complete"
    tasks:
      - id: T4.1
        name: "Production deployment"
        assignee: "TBD"
        estimate: "2 days"
        dependencies: [T3.4]
      - id: T4.2
        name: "Monitoring & stabilization"
        assignee: "TBD"
        estimate: "1 week"
        dependencies: [T4.1]
      - id: T4.3
        name: "Documentation & training"
        assignee: "TBD"
        estimate: "3 days"
        dependencies: [T4.2]
    milestones:
      - name: "Project Complete"
        date: "Week 15"
        criteria: "System stable, docs complete"

dependencies:
  critical_path:
    - T1.1 → T1.2 → T1.3 → T2.1 → T2.2 → T2.3 → T3.1 → T3.2 → T3.3 → T3.4 → T4.1 → T4.2 → T4.3
  external_dependencies:
    - name: "Security review"
      provider: "Security Team"
      deadline: "Week 6"
      impact: "Blocks T3.2"
    - name: "Vendor API access"
      provider: "External Vendor"
      deadline: "Week 4"
      impact: "Blocks T3.2"

resource_allocation:
  people:
    - role: "Project Manager"
      allocation: "50%"
      phases: [1, 2, 3, 4]
    - role: "Technical Lead"
      allocation: "100%"
      phases: [2, 3]
    - role: "Engineers"
      count: 3
      allocation: "100%"
      phases: [3]
    - role: "DevOps"
      allocation: "50%"
      phases: [3, 4]

  infrastructure:
    - item: "Development environment"
      needed: "Week 1"
      cost: "$500/month"
    - item: "Production environment"
      needed: "Week 12"
      cost: "$2000/month"
    - item: "CI/CD pipeline"
      needed: "Week 1"
      cost: "Existing"

risk_management:
  identified_risks:
    - id: R1
      description: "Integration complexity higher than expected"
      probability: Medium
      impact: High
      mitigation: "Early POC, buffer time in schedule"
      contingency: "Extend timeline, add resources"
      owner: "Technical Lead"

    - id: R2
      description: "Key team member unavailable"
      probability: Low
      impact: High
      mitigation: "Cross-training, documentation"
      contingency: "Contractor backup"
      owner: "Project Manager"

    - id: R3
      description: "Vendor API changes"
      probability: Medium
      impact: Medium
      mitigation: "Version pinning, abstraction layer"
      contingency: "Alternative vendor"
      owner: "Technical Lead"

    - id: R4
      description: "Performance issues in production"
      probability: Medium
      impact: High
      mitigation: "Load testing, gradual rollout"
      contingency: "Rollback plan, performance tuning"
      owner: "DevOps Lead"

governance:
  checkpoints:
    - name: "Go/No-Go Decision"
      timing: "End of Phase 2"
      criteria:
        - "Design approved by stakeholders"
        - "Budget confirmed"
        - "Risks acceptable"

    - name: "Production Readiness Review"
      timing: "Before T4.1"
      criteria:
        - "All tests passing"
        - "Security scan clean"
        - "Runbooks complete"
        - "Monitoring in place"

  communication_plan:
    daily_standups:
      audience: "Core team"
      time: "9:00 AM"
    weekly_reviews:
      audience: "Stakeholders"
      time: "Friday 2:00 PM"
    monthly_reporting:
      audience: "Executive"
      format: "Dashboard + Summary"

success_criteria:
  quantitative:
    - metric: "System availability"
      target: "99.9%"
      measurement: "Monthly"
    - metric: "Performance latency"
      target: "< 100ms p95"
      measurement: "Continuous"
    - metric: "Cost reduction"
      target: "20%"
      measurement: "Monthly"
  qualitative:
    - "User satisfaction improved"
    - "Operations team confidence"
    - "Documentation complete"

rollback_plan:
  triggers:
    - "Availability drops below 95%"
    - "Critical bugs in production"
    - "Security vulnerability discovered"
  procedure:
    - "Alert stakeholders"
    - "Execute rollback script"
    - "Verify system health"
    - "Post-incident review"
  rto: "1 hour"
  rpo: "15 minutes"

Planning Checklists

Pre-Planning Checklist

- [ ] Goal clearly defined and quantified
- [ ] Stakeholders identified and engaged
- [ ] Constraints understood (time, budget, resources)
- [ ] Current state assessed
- [ ] Success criteria defined
- [ ] Risks identified

Plan Validation Checklist

- [ ] All tasks have clear deliverables
- [ ] Dependencies mapped and realistic
- [ ] Timeline accounts for uncertainty
- [ ] Resources confirmed available
- [ ] Risks have mitigation strategies
- [ ] Checkpoints for go/no-go decisions
- [ ] Communication plan defined
- [ ] Rollback plan documented

Plan Types

Strategic Plan

# strategic-plan.yml
plan_type: strategic
horizon: 12-24 months
focus: long-term direction
sections:
  - vision_statement
  - market_analysis
  - competitive_landscape
  - strategic_objectives
  - capability_building
  - investment_priorities
  - risk_management

Operational Plan

# operational-plan.yml
plan_type: operational
horizon: 3-12 months
focus: execution excellence
sections:
  - quarterly_goals
  - resource_allocation
  - process_improvements
  - team_development
  - performance_targets
  - operational_excellence

Tactical Plan

# tactical-plan.yml
plan_type: tactical
horizon: 1-4 weeks
focus: immediate execution
sections:
  - sprint_goals
  - daily_tasks
  - blockers_and_escalations
  - immediate_priorities

Crisis/Response Plan

# crisis-plan.yml
plan_type: crisis
horizon: immediate
focus: rapid response
sections:
  - incident_assessment
  - immediate_containment
  - stakeholder_communication
  - recovery_steps
  - post_incident_review

Planning Tools & Templates

# plan-validator.py
class PlanValidator:
    """Validate plan completeness and quality."""

    def __init__(self, plan):
        self.plan = plan
        self.issues = []

    def validate(self):
        """Run all validations."""
        self._check_completeness()
        self._check_dependencies()
        self._check_resources()
        self._check_risks()
        self._check_timeline()
        return self.issues

    def _check_completeness(self):
        """Check all required sections present."""
        required = [
            'goal', 'timeline', 'resources',
            'deliverables', 'success_criteria'
        ]
        for section in required:
            if section not in self.plan:
                self.issues.append(f"Missing required section: {section}")

    def _check_dependencies(self):
        """Check for circular dependencies."""
        # Implementation would detect cycles
        pass

    def _check_resources(self):
        """Check resource allocation."""
        # Verify no over-allocation
        pass

    def _check_risks(self):
        """Check risk coverage."""
        if not self.plan.get('risks'):
            self.issues.append("No risks identified")

    def _check_timeline(self):
        """Check timeline feasibility."""
        # Verify realistic durations
        pass

Communication Templates

Plan Summary Email

Subject: Plan: [Project Name] - [Timeline]

Executive Summary:
- Goal: [One sentence]
- Timeline: [Duration]
- Resources: [Team size, budget]
- Key Milestones: [Top 3]
- Risk Level: [Low/Medium/High]

Next Steps:
1. [Immediate action]
2. [Immediate action]

Full Plan: [Link]
Questions? Contact: [Name]

Status Update Template

## Status Update: Week [N]

### Achievements This Week
- [Completed item 1]
- [Completed item 2]

### Upcoming Next Week
- [Planned item 1]
- [Planned item 2]

### Blockers
- [None / Item with owner]

### Risks
- [Any new or changed risks]

### Metrics
- Budget: [X%] consumed
- Timeline: [On track / At risk / Delayed]
- Scope: [Stable / Changes]

Plan Review Process

1. Draft Plan
   ↓
2. Self-Review (Checklists)
   ↓
3. Peer Review (Critical feedback)
   ↓
4. Stakeholder Review (Alignment)
   ↓
5. Approval (Go/No-Go)
   ↓
6. Baseline & Communication
   ↓
7. Execute with Monitoring

Remember: A plan is a living document. Update it as you learn, but always maintain the discipline of planning before acting.

Похожие навыки: other

limits-colimits

Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context polluti...

Автор: parcadei
3,392

ddttom-allaboutv2-claude-skills-block-collection-and-party

The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration p...

Автор: mattnigh
20

nodnarbnitram-claude-code-extensions-claude-skills-esphome-confi

This skill should be used when the user asks to "create an esphome config", "set up an esp32 device", "configure esphome...

Автор: mattnigh
20