---

name: writing-plans category: knowledge-documentation/planning-architecture version: 1.0.0 description: Create detailed implementation strategies and architecture documentation author: obra/superpowers verified: true tags: [planning, architecture, documentation, strategy]

Writing Plans

Good plans prevent miscommunication, identify risks early, and ensure everyone understands what they're building and why.

Make steps atomic (small and focused), include definition of done for each step, and plan for iteration rather than attempting everything at once.

<best_practices> Break down complex tasks until each step takes hours, not days Include specific acceptance criteria for each step Think about error cases, not just happy path Consider performance, security, and maintainability Buffer time for unknown unknowns Plan tests alongside implementation, not after </best_practices>

<anti_patterns> Skip the "why" - context matters No alternative analysis - first idea isn't always best Unrealistic timelines - buffer time for the unknown Ignore risks - what could go wrong? Testing as afterthought - plan tests upfront No rollback plan - assume you'll need it </anti_patterns>

Copy  <section>Technical Approach</section>
  <content>
    - Architecture: Frontend Stripe Elements + Backend webhook handler
    - Components: Checkout form, payment service, webhook handler
    - Data Flow: User → Stripe → Webhook → App → Database
    - Alternatives: PayPal (higher fees), Stripe Checkout (less customizable)
    - Decision: Stripe Elements for maximum control
  </content>

  <section>Implementation Steps</section>
  <content>
    Phase 1: Foundation (Days 1-2)
    - [ ] Set up Stripe account and test keys
    - [ ] Create payment service base class
    - [ ] Set up webhook endpoint
    - Deliverable: Bare-bones payment infrastructure

    Phase 2: Core Features (Days 3-5)
    - [ ] Build checkout form with Stripe Elements
    - [ ] Implement payment intent creation
    - [ ] Handle webhook events (success, failure)
    - [ ] Update database with payment status
    - Deliverable: Working checkout flow

    Phase 3: Integration & Polish (Days 6-7)
    - [ ] Add error handling and user feedback
    - [ ] Implement idempotency for webhooks
    - [ ] Add logging and monitoring
    - [ ] Security review and testing
    - Deliverable: Production-ready payment feature
  </content>
</plan_structure>

<integration_notes> When planning with Claude, use phrases like:

• "Help me create a plan for [feature]"
• "Break down this implementation into steps"
• "What are the risks with this approach?"
• "Create an architecture doc for [system]"

Claude will:

• Structure comprehensive plans
• Identify potential issues
• Suggest alternatives
• Break down complex tasks
• Ensure nothing is forgotten
• Create clear, actionable steps </integration_notes>

<output_format> Required sections:

1. Executive Summary (overview, goals, metrics)
2. Technical Approach (architecture, components, alternatives)
3. Implementation Steps (phased, with checkboxes)
4. Testing Strategy (unit, integration, manual)
5. Risk Assessment (risks, mitigations, rollback)

Optional sections: 6. Iteration Planning (MVP, future iterations) 7. Edge Cases to Handle 8. Success Criteria Definition </output_format>

<related_skills> systematic-debugging test-driven-development deep-research </related_skills>