Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".
Plans backward from a fixed deadline or target outcome to present, defining milestones, mapping dependencies, and identifying critical path. Use when user mentions "launch by [date]", "work backward from goal", or needs to assess feasibility of time-bound initiatives.
/plugin marketplace add lyndonkl/claude/plugin install lyndonkl-thinking-frameworks-skills@lyndonkl/claudeThis skill inherits all available tools. When active, it can use any tool Claude has access to.
resources/evaluators/rubric_roadmap_backcast.jsonresources/methodology.mdresources/template.mdRoadmap Backcast helps you plan backward from a fixed goal or deadline to the present, identifying required milestones, dependencies, critical path, and feasibility constraints. It transforms aspirational targets into actionable, sequenced plans.
Invoke this skill when you need to:
User phrases that trigger this skill:
A backcasting roadmap that:
Quick example (Product Launch by Q1 2025):
Copy this checklist and track your progress:
Roadmap Backcast Progress:
- [ ] Step 1: Define target outcome precisely
- [ ] Step 2: Work backward to identify milestones
- [ ] Step 3: Map dependencies and sequencing
- [ ] Step 4: Identify critical path
- [ ] Step 5: Assess feasibility and adjust
Step 1: Define target outcome precisely
State specific outcome (not vague goal), target date, success criteria. See Common Patterns for outcome definition examples. For straightforward backcasts → Use resources/template.md.
Step 2: Work backward to identify milestones
Start at end, ask "what must be true just before this?" iteratively. Create 5-10 major milestones. For complex multi-year roadmaps → Study resources/methodology.md.
Step 3: Map dependencies and sequencing
Identify what depends on what, what can run in parallel. See Dependency Mapping for techniques.
Step 4: Identify critical path
Find longest sequence of dependent tasks (this determines minimum timeline). See Critical Path Analysis.
Step 5: Assess feasibility and adjust
Compare required timeline to available time. Add buffers (20-30%), identify risks, adjust scope or date if needed. Self-check using resources/evaluators/rubric_roadmap_backcast.json before finalizing. Minimum standard: Average score ≥ 3.5.
Dependency types:
Sequential (A → B): B cannot start until A completes
Parallel (A ∥ B): A and B can happen simultaneously
Converging (A, B → C): C requires both A and B to complete
Diverging (A → B, C): A enables both B and C
Critical path: Longest sequence of dependent tasks (determines minimum project duration)
Finding critical path:
Example:
Milestone A (4 weeks) → Milestone B (6 weeks) → Milestone D (2 weeks) = 12 weeks (critical path)
Milestone A (4 weeks) → Milestone C (3 weeks) → Milestone D (2 weeks) = 9 weeks (non-critical, 3 weeks slack)
Critical path is 12 weeks (A→B→D path)
Managing critical path:
Pattern 1: Product Launch with Fixed Date
Pattern 2: Compliance Deadline (Regulatory)
Pattern 3: Strategic Transformation (Multi-Year)
Pattern 4: Event Planning (Conference, Launch Event)
Feasibility checks:
Common pitfalls:
Quality standards:
Resources:
resources/evaluators/rubric_roadmap_backcast.json5-Step Process: Define Target → Work Backward → Map Dependencies → Find Critical Path → Assess Feasibility
Dependency types: Sequential (A→B) | Parallel (A∥B) | Converging (A,B→C) | Diverging (A→B,C)
Critical path: Longest dependent sequence = minimum project duration
Buffer rule: Add 20-30% to estimates, 40%+ for high-uncertainty work
Feasibility test: Required time ≤ Available time (with buffer)
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.