Prompt patterns for creating approaches, roadmaps, and strategies that will be consumed by subsequent prompts. ```xml Create a {plan type} for {topic}. Purpose: {What decision/implementation this enables} Input: {Research or context being used} Output: {topic}-plan.md with actionable phases/steps Research findings: @.prompts/{num}-{topic}-research/{topic}-research.md {Additional context files} {What the plan needs to address} {Constraints to work within} {Success criteria for the planned outcome} Save to: `.prompts/{num}-{topic}-plan/{topic}-plan.md` Structure the plan using this XML format: ```xml

{One paragraph overview of the approach}

{What this phase accomplishes} {Specific actionable task} {Another task} {What's produced} {What must exist before this phase} {Why this confidence level} {External dependencies needed} {Uncertainties that may affect execution} {What was assumed in creating this plan} ``` Create `.prompts/{num}-{topic}-plan/SUMMARY.md` Load template: [summary-template.md](summary-template.md) For plans, emphasize phase breakdown with objectives and assumptions needing validation. Next step typically: Execute first phase. - Plan addresses all requirements - Phases are sequential and logical - Tasks are specific and actionable - Metadata captures uncertainties - SUMMARY.md created with phase overview - Ready for implementation prompts to consume ``` Plans should build on research findings: ```xml Research findings: @.prompts/001-auth-research/auth-research.md Key findings to incorporate: - Recommended approach from research - Constraints identified - Best practices to follow ``` Each phase should be executable by a single prompt: ```xml Create base auth structure and types Create auth module directory Define TypeScript types for tokens Set up test infrastructure ``` Help the next Claude understand how to proceed: ```xml This phase modifies files from phase 1. Reference the types created in phase 1. Run tests after each major change. ``` For breaking down how to build something: ```xml Create implementation roadmap for user authentication system. Purpose: Guide phased implementation with clear milestones Input: Authentication research findings Output: auth-plan.md with 4-5 implementation phases Research: @.prompts/001-auth-research/auth-research.md - Break into independently testable phases - Each phase builds on previous - Include testing at each phase - Consider rollback points ``` For choosing between options: ```xml Create decision framework for selecting database technology. Purpose: Make informed choice between PostgreSQL, MongoDB, and DynamoDB Input: Database research findings Output: database-plan.md with criteria, analysis, recommendation Structure as decision framework: ```xml {List} {List} 8/10 6/10 {Selected option} {Why this choice} {What could go wrong} {How to address risks} Clear winner based on requirements - Expected data volume: 10M records - Team has SQL experience ``` ``` For defining workflows or methodologies: ```xml Create deployment process for production releases. Purpose: Standardize safe, repeatable deployments Input: Current infrastructure research Output: deployment-plan.md with step-by-step process Structure as process: ```xml {High-level flow} Run full test suite Create database backup Notify team in #deployments Tests passing Backup verified Team notified N/A - no changes yet - CI/CD pipeline configured - Database backup system - Slack webhook for notifications - Blue-green vs rolling deployment? - Automated rollback triggers? ``` ``` Load: [metadata-guidelines.md](metadata-guidelines.md)