tst-claude-code-samples/.claude/commands/planning/3-roadmap/1-create-from-mrd.md

allowed-tools, description

allowed-tools	description
Read Write	Creates a PRD direction roadmap from an existing MRD, suggesting phased PRD development for key features with improvement directions.

Create PRD Direction Roadmap from MRD

Context

• User Request: $ARGUMENTS
• MRD Session: Identified by --name argument (session name or index).
• Source MRD: Final market-requirements-document_*.md file from the specified MRD session directory.
• Roadmap Directory: .taskmaster/docs/roadmap/

Goal

To transform market requirements from an MRD into a focused roadmap that suggests phased PRD development for key features, providing directions for iterative improvements without timelines or session states.

Process

1. Identify Source MRD:

   • Use the --name argument to locate the correct MRD session directory (e.g., .taskmaster/docs/mrd/001-enterprise-expansion/).
   • Read the final MRD document (market-requirements-document_*.md) to extract key market insights, user requirements, and feature ideas.

2. Extract Key Elements from MRD:

   • Market and User Insights: Identify target segments, pain points, and opportunities.
   • Feature Opportunities: Map MRD requirements to potential features, prioritizing based on business impact and feasibility.
   • Improvement Directions: For each feature, suggest iterative refinement paths (e.g., from basic MVP to advanced versions).

3. Generate PRD Direction Roadmap:

   • Create a single comprehensive document outlining phased PRD suggestions for features.
   • Structure the content using the PRD Direction Roadmap Template, focusing on iterative PRD development and improvement suggestions.
   • Ensure the roadmap emphasizes directions for PRD creation, such as starting with core features and evolving through user feedback.

4. Notify User with Key Insights:

   • Inform the user that the PRD direction roadmap has been generated.
   • Provide the file path and highlight top feature suggestions.
   • Suggest next steps: "Proceed to create detailed PRDs for suggested features using /planning/prd/1-create-from-roadmap --name=[roadmap_name] --feature=[feature_id]"

Templates & Structures

PRD Direction Roadmap Template

# PRD Direction Roadmap: [MRD Session Name]

**Created:** [Date]
**Source:** MRD Session: [MRD Session Name]
**Focus:** Phased PRD Development and Improvement Directions

---

## Executive Summary
- **Overview:** High-level suggestions for PRD development based on MRD insights.
- **Key Features:** [Number] prioritized features with phased PRD directions.
- **Improvement Approach:** Iterative refinement from core to advanced implementations.

---

## Feature Suggestions

### Feature 1: [Feature Name]
- **MRD Basis:** [Relevant insights from MRD, e.g., user pain points].
- **Phased PRD Directions:**
  - **Phase 1 (Core):** Basic PRD focusing on MVP functionality.
  - **Phase 2 (Improvement):** Add user feedback loops and refinements.
  - **Phase 3 (Advanced):** Integrate scalability and edge cases.
- **Improvement Suggestions:** [e.g., Start with user testing, evolve based on metrics like adoption rate].

### Feature 2: [Feature Name]
- **MRD Basis:** [Relevant insights].
- **Phased PRD Directions:** [Similar phased structure].
- **Improvement Suggestions:** [Specific directions].

---

## Overall Improvement Strategy
- **Iteration Model:** Use user feedback to refine PRDs iteratively.
- **Prioritization Criteria:** Based on MRD impact and feasibility.
- **Success Indicators:** [e.g., Alignment with market needs, measurable user value].

---

## Next Steps
- Create PRD for Feature 1 using suggested directions.
- Validate improvements through prototypes or user tests.

Best Practices / DO & DON'T

✅ DO: Focus on Iterative PRD Directions

• Emphasize phased approaches that guide PRD evolution from basic to advanced.
• Suggest specific improvement ideas tied to MRD insights. Why: This ensures the roadmap drives actionable, evolving PRD creation.

✅ DO: Prioritize Based on MRD Insights

• Rank features by market impact and user needs from the MRD.
• Include rationale for each suggestion. Why: Maintains alignment with original market requirements.

❌ DON'T: Include Timelines or Deadlines

• Avoid any time-based planning or horizons. Why: Focus solely on directional guidance for PRD development.

❌ DON'T: Add Unnecessary Complexity

• Keep suggestions concise and directly tied to PRD phases. Why: The goal is to provide clear directions, not over-engineer the roadmap.

Output

• Format: Markdown document.
• Location: .taskmaster/docs/roadmap/
• Filename: roadmap-prd-directions_[mrd_session_name].md

Example Usage

• Create PRD direction roadmap from MRD session: /planning/roadmap/1-create-from-mrd --name="enterprise-expansion"
• Create by MRD index: /planning/roadmap/1-create-from-mrd --name="1"