generated from Paul.Kim/tpl-superclaude
Initial commit
This commit is contained in:
100
.claude/commands/planning/1-mrd/1-start-session.md
Normal file
100
.claude/commands/planning/1-mrd/1-start-session.md
Normal file
@ -0,0 +1,100 @@
|
||||
---
|
||||
allowed-tools: [Bash, Read, Write, Glob]
|
||||
description: Starts a new or updated MRD (Market Requirements Document) research session.
|
||||
---
|
||||
|
||||
# Start MRD Research Session
|
||||
|
||||
## Context
|
||||
- **User Request:** $ARGUMENTS
|
||||
- **MRD Directory:** `.taskmaster/docs/mrd/`
|
||||
- **Existing Sessions:** !`ls -ld .taskmaster/docs/mrd/*/ 2>/dev/null || echo "No existing sessions found"`
|
||||
|
||||
## Goal
|
||||
To initialize a new or updated Market Requirements Document (MRD) research session, set up the dedicated workspace, and present the first research task to the user.
|
||||
|
||||
## Process
|
||||
1. **Determine Session Index:**
|
||||
- Scan the `.taskmaster/docs/mrd/` directory to find the highest existing session index.
|
||||
- Assign the next sequential number for the new session.
|
||||
|
||||
2. **Create Session Directory:**
|
||||
- Create a new directory named `[index]-[session_name]` inside `.taskmaster/docs/mrd/`.
|
||||
- Example: `.taskmaster/docs/mrd/001-mvp-launch/`
|
||||
|
||||
3. **Handle Update Session (if `--from` is provided):**
|
||||
- Copy all `0*_*.md` user research files from the base session directory to the new session directory.
|
||||
- Generate a `_00_update_kickoff_report.md` file. This report will compare the goals of the base session and the new session, highlighting key assumptions that need to be re-validated.
|
||||
|
||||
4. **Initialize Session State:**
|
||||
- Create a `_session-state.json` file in the new session directory.
|
||||
- Initialize it with session details (index, name, status: 'initialized', etc.).
|
||||
|
||||
5. **Interactive Hypothesis Definition:**
|
||||
- This step is a structured conversation to build the foundational `01_initial_hypothesis.md`.
|
||||
|
||||
- **For a new session:**
|
||||
- The AI will ask a series of clarifying questions to build the hypothesis, such as:
|
||||
1. "What is the core problem you are trying to solve?"
|
||||
2. "Who is the primary target audience for this product?"
|
||||
3. "At a high level, what is your proposed solution?"
|
||||
4. "What is the unique value proposition? Why will users choose it over alternatives?"
|
||||
- After gathering the user's answers, the AI will synthesize them into a coherent initial hypothesis.
|
||||
- The AI saves this synthesized content into the `01_initial_hypothesis.md` file.
|
||||
|
||||
- **For an update session (`--from` is used):**
|
||||
- The AI first presents the key findings from the generated `_00_update_kickoff_report.md`.
|
||||
- It then asks for the user's input on the re-validation points. For example: "The report suggests we need to re-validate our target audience. Has your understanding of the target customer changed? If so, how?"
|
||||
- The user's feedback is incorporated to refine the session's starting assumptions, which can be noted in the kickoff report or a new hypothesis file.
|
||||
|
||||
6. **Assign First Task and Generate Research Prompt:**
|
||||
- Based on the session's goal and initial hypothesis, the AI selects the most logical first research task from the examples below.
|
||||
- It clearly presents this task to the user, specifying the filename for the output.
|
||||
- **Crucially**, it must also generate a detailed, self-contained research prompt that can be used by any external agent or tool. This prompt should be presented to the user in a structured format.
|
||||
|
||||
**Research Prompt Generation Template:**
|
||||
The AI will use the newly created `01_initial_hypothesis.md` to construct a prompt like this:
|
||||
```
|
||||
### Research Prompt: [Objective of the Task]
|
||||
|
||||
**1. Project Context:**
|
||||
- **Product/Idea:** [Synthesized from 01_initial_hypothesis.md - e.g., "A platform connecting eco-friendly suppliers with small businesses."]
|
||||
- **Core Problem:** [From hypothesis - e.g., "Small businesses struggle to find and verify sustainable suppliers."]
|
||||
- **Target Audience:** [From hypothesis - e.g., "Owners of small to medium-sized retail businesses."]
|
||||
- **Proposed Solution:** [From hypothesis - e.g., "A curated, searchable marketplace with a built-in verification system."]
|
||||
|
||||
**2. Research Objective:**
|
||||
- [A clear goal for this specific research task, e.g., "To deeply understand the competitive landscape for our proposed solution."]
|
||||
|
||||
**3. Key Research Questions:**
|
||||
- [A list of 3-5 specific questions. For competitor analysis, it could be:]
|
||||
- Who are the top 3 direct and indirect competitors?
|
||||
- What are their pricing models and key features?
|
||||
- What are their primary strengths and weaknesses (SWOT)?
|
||||
- What market segment do they primarily target?
|
||||
|
||||
**4. Expected Deliverables:**
|
||||
- A summary of findings.
|
||||
- Detailed answers to each key research question.
|
||||
- A concluding analysis of opportunities and threats for our product.
|
||||
```
|
||||
|
||||
**First Research Task Examples:**
|
||||
- **Task:** "Define the target market size, segments, and create detailed user personas."
|
||||
- **Filename:** `02_market_and_persona.md`
|
||||
- **Task:** "Validate the core problem this product aims to solve and outline the proposed solution's unique value proposition."
|
||||
- **Filename:** `02_problem_and_solution.md`
|
||||
- **Task:** "Identify the top 3-5 direct and indirect competitors and analyze their strengths, weaknesses, and market positioning."
|
||||
- **Filename:** `02_competitive_landscape.md`
|
||||
- **Task:** "Brainstorm a list of potential core features that address the initial hypothesis and align with the target user's needs."
|
||||
- **Filename:** `02_initial_feature_ideas.md`
|
||||
- **Task:** "Define the key success metrics and Key Performance Indicators (KPIs) that will be used to measure the product's success."
|
||||
- **Filename:** `02_success_metrics.md`
|
||||
|
||||
- After presenting the task and the detailed prompt, the AI will conclude with: "Once you have completed your research and saved it to the specified file, please run the `/planning/mrd/2-analyze-research-data` command to proceed."
|
||||
|
||||
## Example Usage
|
||||
- **Start a new session:**
|
||||
`/planning/mrd/1-start-session --name="mvp-launch"`
|
||||
- **Start a session based on a previous one:**
|
||||
`/planning/mrd/1-start-session --name="enterprise-expansion" --from="mvp-launch"`
|
||||
91
.claude/commands/planning/1-mrd/2-analyze-research-data.md
Normal file
91
.claude/commands/planning/1-mrd/2-analyze-research-data.md
Normal file
@ -0,0 +1,91 @@
|
||||
---
|
||||
allowed-tools: [Read, Write, Glob]
|
||||
description: Analyzes user-submitted research data, provides insights, and suggests the next research step.
|
||||
---
|
||||
|
||||
# Analyze Research Data
|
||||
|
||||
## Context
|
||||
- **User Request:** $ARGUMENTS
|
||||
- **Session Name/Index:** Passed via `--name` argument.
|
||||
- **Session State File:** `_session-state.json` within the specified session directory.
|
||||
|
||||
## Goal
|
||||
To analyze the latest research file(s) submitted by the user within a specific MRD session, generate a summary of insights, and propose the next logical research task to continue the workflow.
|
||||
|
||||
## Process
|
||||
1. **Identify Target Session:**
|
||||
- Use the `--name` argument to locate the correct session directory (e.g., `.taskmaster/docs/mrd/001-mvp-launch/`).
|
||||
|
||||
2. **Read Session State:**
|
||||
- Read the `_session-state.json` file to understand the current context.
|
||||
- Identify the `lastAnalyzedFile` to determine which new files need to be processed.
|
||||
|
||||
3. **Find and Analyze New Research:**
|
||||
- Scan the session directory for any `0*_*.md` files created or modified after `lastAnalyzedFile`.
|
||||
- Read the content of the new research file(s).
|
||||
|
||||
4. **Generate AI Summary:**
|
||||
- Analyze the research content to extract key findings, patterns, opportunities, and threats.
|
||||
- Create or update a corresponding summary file named `_summary_[topic].md` (e.g., `_summary_market_and_persona.md`). This provides a digestible, AI-driven analysis for the user.
|
||||
|
||||
5. **Update Session State with Intelligent Next Action:**
|
||||
- Update the `_session-state.json` file:
|
||||
- Set `status` to `analysis_in_progress`.
|
||||
- Update `lastAnalyzedFile` to the name of the file just analyzed.
|
||||
- **Formulate the `nextAction`:**
|
||||
- The AI must first review all existing `0*_*` research files in the session directory to understand which topics from the "Standard Research Topics" list below have already been covered.
|
||||
- Based on the analysis of the current file and the list of completed topics, the AI will determine the next logical, uncovered research area.
|
||||
- It will then formulate a clear, actionable `nextAction` string.
|
||||
|
||||
**Standard Research Topics (in logical order):**
|
||||
1. **Initial Hypothesis (`01_initial_hypothesis.md`)**: Core problem, target audience, proposed solution.
|
||||
2. **Market & Persona Analysis (`02_market_and_persona.md`)**: Market size, segments, user demographics, needs, and pain points.
|
||||
3. **Competitive Landscape (`03_competitor_analysis.md`)**: Direct/indirect competitors, SWOT analysis, market positioning.
|
||||
4. **Value Proposition & Solution (`04_value_proposition.md`)**: Detailed breakdown of the solution, unique selling points, feature ideas.
|
||||
5. **Pricing & Business Model (`05_pricing_analysis.md`)**: Revenue streams, pricing strategies, cost analysis.
|
||||
6. **Go-to-Market Strategy (`06_go_to_market.md`)**: Marketing channels, sales process, initial customer acquisition plan.
|
||||
7. **Success Metrics & KPIs (`07_success_metrics.md`)**: How to measure product success.
|
||||
|
||||
6. **Report to User with Context and Next Research Prompt:**
|
||||
- Present a concise summary of the analysis from the current research file.
|
||||
- Clearly state the next logical research task and the filename for the output.
|
||||
- **Crucially**, generate a new, updated, self-contained research prompt for this next task. This prompt must synthesize all relevant context from the *entire session* so far (i.e., from `01_...` up to the latest `_summary_...` file).
|
||||
|
||||
**Updated Research Prompt Generation Template:**
|
||||
The AI will use all existing session files (`0*_*` and `_summary_*`) to construct a prompt like this:
|
||||
```
|
||||
### Research Prompt: [Objective of the NEXT Task]
|
||||
|
||||
**1. Project Context (Updated):**
|
||||
- **Product/Idea:** [e.g., "A platform connecting eco-friendly suppliers with small businesses."]
|
||||
- **Key Findings So Far:**
|
||||
- [Insight from summary_market_and_persona.md: e.g., "Identified a key persona 'Eco-conscious Cafe Owner' who values supply chain transparency."]
|
||||
- [Insight from summary_competitor_analysis.md: e.g., "Major competitors focus on large enterprises, leaving a gap in the SMB market."]
|
||||
- [Latest insight...]
|
||||
|
||||
**2. Research Objective:**
|
||||
- [A clear goal for the NEXT research task, e.g., "To define a compelling value proposition and initial feature set based on our market and competitor analysis."]
|
||||
|
||||
**3. Key Research Questions:**
|
||||
- [A list of 3-5 specific questions for the next task. For value proposition, it could be:]
|
||||
- Based on the key findings, what is our unique value proposition?
|
||||
- What core features must we build to deliver this value to our target persona?
|
||||
- How can we differentiate ourselves from the identified competitors?
|
||||
|
||||
**4. Expected Deliverables:**
|
||||
- A clear statement of the value proposition.
|
||||
- A prioritized list of core features.
|
||||
- An explanation of the differentiation strategy.
|
||||
```
|
||||
|
||||
- **Conclude with a clear call to action:**
|
||||
- Instruct the user to run the same `/planning/mrd/2-analyze-research-data` command after creating the next research file.
|
||||
- **Crucially**, emphasize that they must use the **current session name or index** for the `--name` parameter, as the command always analyzes the latest progress within the *current session*.
|
||||
- **Example Conclusion:** "Once you have completed this research and saved it to `04_value_proposition.md`, please run `/planning/mrd/2-analyze-research-data --name"` again to analyze the new data."
|
||||
|
||||
## Example Usage
|
||||
- **Analyze the latest research in a session:**
|
||||
`/planning/mrd/2-analyze-research-data --name="mvp-launch"`
|
||||
- **Analyze by index:**
|
||||
`/planning/mrd/2-analyze-research-data --name="1"`
|
||||
45
.claude/commands/planning/1-mrd/3-generate-mrd-document.md
Normal file
45
.claude/commands/planning/1-mrd/3-generate-mrd-document.md
Normal file
@ -0,0 +1,45 @@
|
||||
---
|
||||
allowed-tools: [Read, Write, Glob]
|
||||
description: Generates the final MRD document by consolidating all research and analysis from a session.
|
||||
---
|
||||
|
||||
# Generate MRD Document
|
||||
|
||||
## Context
|
||||
- **User Request:** $ARGUMENTS
|
||||
- **Session Name/Index:** Passed via `--name` argument.
|
||||
- **All Session Files:** All `0*_*.md` (user research) and `_summary_*.md` (AI analysis) files within the target session directory.
|
||||
|
||||
## Goal
|
||||
To synthesize all research findings and AI-generated analyses from a completed MRD session into a single, coherent, and well-structured Market Requirements Document (MRD).
|
||||
|
||||
## Process
|
||||
1. **Identify Target Session:**
|
||||
- Use the `--name` argument to locate the correct session directory.
|
||||
|
||||
2. **Aggregate All Session Data:**
|
||||
- Read the content of all user research files (`0*_*.md`) within the directory.
|
||||
- Read the content of all AI-generated summary files (`_summary_*.md`).
|
||||
|
||||
3. **Synthesize and Structure Content:**
|
||||
- Comprehensively analyze the aggregated information.
|
||||
- Logically map the findings to the standard sections of an MRD template (e.g., Market Problem, Target Audience, Competitive Landscape, Requirements).
|
||||
- Rewrite and rephrase the content to ensure a consistent tone and narrative flow throughout the document.
|
||||
|
||||
4. **Generate Final MRD File:**
|
||||
- Create the final document named `mrd_[session_name].md`.
|
||||
- Populate it with the structured, synthesized content.
|
||||
|
||||
5. **Finalize Session State:**
|
||||
- Update the `_session-state.json` file by setting the `status` to `finalized`. This marks the session as complete.
|
||||
|
||||
6. **Notify User and Suggest Next Step:**
|
||||
- Inform the user that the MRD document has been successfully generated and provide the file path.
|
||||
- Proactively suggest the next logical step in the SDLC, which is to define a product roadmap.
|
||||
- Example: "Your MRD is complete. Would you like to proceed with defining the product roadmap using `/planning/roadmap/1-define-roadmap`?"
|
||||
|
||||
## Example Usage
|
||||
- **Generate MRD for a session:**
|
||||
`/planning/mrd/3-generate-mrd-document --name="mvp-launch"`
|
||||
- **Generate by index:**
|
||||
`/planning/mrd/3-generate-mrd-document --name="1"`
|
||||
46
.claude/commands/planning/1-mrd/4-compare-mrd-versions.md
Normal file
46
.claude/commands/planning/1-mrd/4-compare-mrd-versions.md
Normal file
@ -0,0 +1,46 @@
|
||||
---
|
||||
allowed-tools: [Read, Write, Glob]
|
||||
description: Compares two different MRD versions (sessions) and generates a strategic change report.
|
||||
---
|
||||
|
||||
# Compare MRD Versions
|
||||
|
||||
## Context
|
||||
- **User Request:** $ARGUMENTS
|
||||
- **Base Session:** Identified by the `--base` argument (name or index).
|
||||
- **Compare Session:** Identified by the `--compare` argument (name or index).
|
||||
- **Final MRD Documents:** The `market-requirements-document_*.md` file from each of the two specified session directories.
|
||||
|
||||
## Goal
|
||||
To provide a clear, actionable comparison report that highlights the strategic evolution between two different MRD versions. This helps stakeholders quickly understand changes in market perception, target audience, competitive landscape, and overall strategy over time.
|
||||
|
||||
## Process
|
||||
1. **Identify Target Sessions:**
|
||||
- Locate the directories for the base and compare sessions using the provided arguments.
|
||||
|
||||
2. **Read Final MRD Documents:**
|
||||
- From each session directory, read the final `market-requirements-document_*.md` file.
|
||||
|
||||
3. **Perform Comparative Analysis:**
|
||||
- Systematically compare the two documents, section by section.
|
||||
- Identify and extract key differences, such as:
|
||||
- Changes in target market or user personas.
|
||||
- Shifts in the competitive landscape.
|
||||
- Updates to key performance indicators (KPIs) or success metrics.
|
||||
- Evolution of core product requirements.
|
||||
- Modifications in pricing or business model assumptions.
|
||||
|
||||
4. **Generate Comparison Report:**
|
||||
- Create a new Markdown file named `mrd_comparison_report_[base]_vs_[compare].md`.
|
||||
- Structure the report to clearly present the side-by-side comparison and a summary of the most significant strategic changes.
|
||||
|
||||
5. **Notify User with Key Insights:**
|
||||
- Inform the user that the comparison report has been generated and provide the file path.
|
||||
- Present a high-level summary of the most critical findings.
|
||||
- Example: "The comparison is complete. The most significant change is the shift in target market from SMBs to Enterprise customers. You can find the detailed report at..."
|
||||
|
||||
## Example Usage
|
||||
- **Compare two sessions by name:**
|
||||
`/planning/mrd/4-compare-mrd-versions --base="mvp-launch" --compare="enterprise-expansion"`
|
||||
- **Compare by index:**
|
||||
`/planning/mrd/4-compare-mrd-versions --base="1" --compare="2"`
|
||||
Reference in New Issue
Block a user