merge doc fixes and fix merge conflicts
This commit is contained in:
Brian Madison
@@ -19,34 +19,35 @@ If the project includes a significant user interface, a separate Frontend Archit
|
||||
|
||||
1. Review the PRD and brainstorming brief for any mentions of:
|
||||
|
||||
- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
|
||||
- Existing projects or codebases being used as a foundation
|
||||
- Boilerplate projects or scaffolding tools
|
||||
- Previous projects to be cloned or adapted
|
||||
- Starter templates (e.g., Create React App, Next.js, Vue CLI, Angular CLI, etc.)
|
||||
- Existing projects or codebases being used as a foundation
|
||||
- Boilerplate projects or scaffolding tools
|
||||
- Previous projects to be cloned or adapted
|
||||
|
||||
2. If a starter template or existing project is mentioned:
|
||||
|
||||
- Ask the user to provide access via one of these methods:
|
||||
- Link to the starter template documentation
|
||||
- Upload/attach the project files (for small projects)
|
||||
- Share a link to the project repository (GitHub, GitLab, etc.)
|
||||
- Analyze the starter/existing project to understand:
|
||||
- Pre-configured technology stack and versions
|
||||
- Project structure and organization patterns
|
||||
- Built-in scripts and tooling
|
||||
- Existing architectural patterns and conventions
|
||||
- Any limitations or constraints imposed by the starter
|
||||
- Use this analysis to inform and align your architecture decisions
|
||||
- Ask the user to provide access via one of these methods:
|
||||
- Link to the starter template documentation
|
||||
- Upload/attach the project files (for small projects)
|
||||
- Share a link to the project repository (GitHub, GitLab, etc.)
|
||||
- Analyze the starter/existing project to understand:
|
||||
- Pre-configured technology stack and versions
|
||||
- Project structure and organization patterns
|
||||
- Built-in scripts and tooling
|
||||
- Existing architectural patterns and conventions
|
||||
- Any limitations or constraints imposed by the starter
|
||||
- Use this analysis to inform and align your architecture decisions
|
||||
|
||||
3. If no starter template is mentioned but this is a greenfield project:
|
||||
|
||||
- Suggest appropriate starter templates based on the tech stack preferences
|
||||
- Explain the benefits (faster setup, best practices, community support)
|
||||
- Let the user decide whether to use one
|
||||
- Suggest appropriate starter templates based on the tech stack preferences
|
||||
- Explain the benefits (faster setup, best practices, community support)
|
||||
- Let the user decide whether to use one
|
||||
|
||||
4. If the user confirms no starter template will be used:
|
||||
- Proceed with architecture design from scratch
|
||||
- Note that manual setup will be required for all tooling and configuration
|
||||
|
||||
- Proceed with architecture design from scratch
|
||||
- Note that manual setup will be required for all tooling and configuration
|
||||
|
||||
Document the decision here before proceeding with the architecture design. In none, just say N/A
|
||||
|
||||
@@ -222,10 +223,12 @@ After presenting all data models, apply `tasks#advanced-elicitation` protocol]]
|
||||
2. Consider the repository structure (monorepo/polyrepo) from PRD
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
@@ -734,15 +737,15 @@ Note: Basic info goes in Coding Standards for dev agent. This detailed section i
|
||||
|
||||
1. If project has UI components:
|
||||
|
||||
- Recommend engaging Design Architect agent
|
||||
- Use "Frontend Architecture Mode"
|
||||
- Provide this document as input
|
||||
- Recommend engaging Design Architect agent
|
||||
- Use "Frontend Architecture Mode"
|
||||
- Provide this document as input
|
||||
|
||||
2. For all projects:
|
||||
|
||||
- Review with Product Owner
|
||||
- Begin story implementation with Dev agent
|
||||
- Set up infrastructure with DevOps agent
|
||||
- Review with Product Owner
|
||||
- Begin story implementation with Dev agent
|
||||
- Set up infrastructure with DevOps agent
|
||||
|
||||
3. Include specific prompts for next agents if needed]]
|
||||
|
||||
|
||||
@@ -9,7 +9,9 @@
|
||||
## Analysis Scope & Methodology
|
||||
|
||||
### Analysis Purpose
|
||||
|
||||
{{Define the primary purpose:
|
||||
|
||||
- New market entry assessment
|
||||
- Product positioning strategy
|
||||
- Feature gap analysis
|
||||
@@ -18,7 +20,9 @@
|
||||
- Competitive threat assessment}}
|
||||
|
||||
### Competitor Categories Analyzed
|
||||
|
||||
{{List categories included:
|
||||
|
||||
- Direct Competitors: Same product/service, same target market
|
||||
- Indirect Competitors: Different product, same need/problem
|
||||
- Potential Competitors: Could enter market easily
|
||||
@@ -26,7 +30,9 @@
|
||||
- Aspirational Competitors: Best-in-class examples}}
|
||||
|
||||
### Research Methodology
|
||||
|
||||
{{Describe approach:
|
||||
|
||||
- Information sources used
|
||||
- Analysis timeframe
|
||||
- Confidence levels
|
||||
@@ -35,7 +41,9 @@
|
||||
## Competitive Landscape Overview
|
||||
|
||||
### Market Structure
|
||||
|
||||
{{Describe the competitive environment:
|
||||
|
||||
- Number of active competitors
|
||||
- Market concentration (fragmented/consolidated)
|
||||
- Competitive dynamics
|
||||
@@ -46,8 +54,9 @@
|
||||
[[LLM: Help categorize competitors by market share and strategic threat level]]
|
||||
|
||||
{{Create a 2x2 matrix:
|
||||
|
||||
- Priority 1 (Core Competitors): High Market Share + High Threat
|
||||
- Priority 2 (Emerging Threats): Low Market Share + High Threat
|
||||
- Priority 2 (Emerging Threats): Low Market Share + High Threat
|
||||
- Priority 3 (Established Players): High Market Share + Low Threat
|
||||
- Priority 4 (Monitor Only): Low Market Share + Low Threat}}
|
||||
|
||||
@@ -58,6 +67,7 @@
|
||||
### {{Competitor Name}} - Priority {{1/2/3/4}}
|
||||
|
||||
#### Company Overview
|
||||
|
||||
- **Founded:** {{Year, founders}}
|
||||
- **Headquarters:** {{Location}}
|
||||
- **Company Size:** {{Employees, revenue if known}}
|
||||
@@ -65,6 +75,7 @@
|
||||
- **Leadership:** {{Key executives}}
|
||||
|
||||
#### Business Model & Strategy
|
||||
|
||||
- **Revenue Model:** {{How they make money}}
|
||||
- **Target Market:** {{Primary customer segments}}
|
||||
- **Value Proposition:** {{Core value promise}}
|
||||
@@ -72,6 +83,7 @@
|
||||
- **Strategic Focus:** {{Current priorities}}
|
||||
|
||||
#### Product/Service Analysis
|
||||
|
||||
- **Core Offerings:** {{Main products/services}}
|
||||
- **Key Features:** {{Standout capabilities}}
|
||||
- **User Experience:** {{UX strengths/weaknesses}}
|
||||
@@ -81,16 +93,19 @@
|
||||
#### Strengths & Weaknesses
|
||||
|
||||
**Strengths:**
|
||||
|
||||
- {{Strength 1}}
|
||||
- {{Strength 2}}
|
||||
- {{Strength 3}}
|
||||
|
||||
**Weaknesses:**
|
||||
|
||||
- {{Weakness 1}}
|
||||
- {{Weakness 2}}
|
||||
- {{Weakness 3}}
|
||||
|
||||
#### Market Position & Performance
|
||||
|
||||
- **Market Share:** {{Estimate if available}}
|
||||
- **Customer Base:** {{Size, notable clients}}
|
||||
- **Growth Trajectory:** {{Trending up/down/stable}}
|
||||
@@ -104,32 +119,34 @@
|
||||
|
||||
[[LLM: Create a detailed comparison table of key features across competitors]]
|
||||
|
||||
| Feature Category | {{Your Company}} | {{Competitor 1}} | {{Competitor 2}} | {{Competitor 3}} |
|
||||
|-----------------|------------------|------------------|------------------|------------------|
|
||||
| **Core Functionality** |
|
||||
| Feature A | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| Feature B | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| **User Experience** |
|
||||
| Mobile App | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} |
|
||||
| Onboarding Time | {{Time}} | {{Time}} | {{Time}} | {{Time}} |
|
||||
| Feature Category | {{Your Company}} | {{Competitor 1}} | {{Competitor 2}} | {{Competitor 3}} |
|
||||
| --------------------------- | ------------------- | ------------------- | ------------------- | ------------------- |
|
||||
| **Core Functionality** |
|
||||
| Feature A | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| Feature B | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} | {{✓/✗/Partial}} |
|
||||
| **User Experience** |
|
||||
| Mobile App | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} | {{Rating/Status}} |
|
||||
| Onboarding Time | {{Time}} | {{Time}} | {{Time}} | {{Time}} |
|
||||
| **Integration & Ecosystem** |
|
||||
| API Availability | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} |
|
||||
| Third-party Integrations | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} |
|
||||
| **Pricing & Plans** |
|
||||
| Starting Price | {{$X}} | {{$X}} | {{$X}} | {{$X}} |
|
||||
| Free Tier | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} |
|
||||
| API Availability | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} | {{Yes/No/Limited}} |
|
||||
| Third-party Integrations | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} | {{Number/Key ones}} |
|
||||
| **Pricing & Plans** |
|
||||
| Starting Price | {{$X}} | {{$X}} | {{$X}} | {{$X}} |
|
||||
| Free Tier | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} | {{Yes/No}} |
|
||||
|
||||
### SWOT Comparison
|
||||
|
||||
[[LLM: Create SWOT analysis for your solution vs. top competitors]]
|
||||
|
||||
#### Your Solution
|
||||
|
||||
- **Strengths:** {{List key strengths}}
|
||||
- **Weaknesses:** {{List key weaknesses}}
|
||||
- **Opportunities:** {{List opportunities}}
|
||||
- **Threats:** {{List threats}}
|
||||
|
||||
#### vs. {{Main Competitor}}
|
||||
|
||||
- **Competitive Advantages:** {{Where you're stronger}}
|
||||
- **Competitive Disadvantages:** {{Where they're stronger}}
|
||||
- **Differentiation Opportunities:** {{How to stand out}}
|
||||
@@ -139,6 +156,7 @@
|
||||
[[LLM: Describe competitor positions on key dimensions]]
|
||||
|
||||
{{Create a positioning description using 2 key dimensions relevant to the market, such as:
|
||||
|
||||
- Price vs. Features
|
||||
- Ease of Use vs. Power
|
||||
- Specialization vs. Breadth
|
||||
@@ -149,7 +167,9 @@
|
||||
### Competitive Advantages Assessment
|
||||
|
||||
#### Sustainable Advantages
|
||||
|
||||
{{Identify moats and defensible positions:
|
||||
|
||||
- Network effects
|
||||
- Switching costs
|
||||
- Brand strength
|
||||
@@ -157,7 +177,9 @@
|
||||
- Regulatory advantages}}
|
||||
|
||||
#### Vulnerable Points
|
||||
|
||||
{{Where competitors could be challenged:
|
||||
|
||||
- Weak customer segments
|
||||
- Missing features
|
||||
- Poor user experience
|
||||
@@ -169,6 +191,7 @@
|
||||
[[LLM: Identify uncontested market spaces]]
|
||||
|
||||
{{List opportunities to create new market space:
|
||||
|
||||
- Underserved segments
|
||||
- Unaddressed use cases
|
||||
- New business models
|
||||
@@ -178,7 +201,9 @@
|
||||
## Strategic Recommendations
|
||||
|
||||
### Differentiation Strategy
|
||||
|
||||
{{How to position against competitors:
|
||||
|
||||
- Unique value propositions to emphasize
|
||||
- Features to prioritize
|
||||
- Segments to target
|
||||
@@ -187,19 +212,25 @@
|
||||
### Competitive Response Planning
|
||||
|
||||
#### Offensive Strategies
|
||||
|
||||
{{How to gain market share:
|
||||
|
||||
- Target competitor weaknesses
|
||||
- Win competitive deals
|
||||
- Capture their customers}}
|
||||
|
||||
#### Defensive Strategies
|
||||
|
||||
{{How to protect your position:
|
||||
|
||||
- Strengthen vulnerable areas
|
||||
- Build switching costs
|
||||
- Deepen customer relationships}}
|
||||
|
||||
### Partnership & Ecosystem Strategy
|
||||
|
||||
{{Potential collaboration opportunities:
|
||||
|
||||
- Complementary players
|
||||
- Channel partners
|
||||
- Technology integrations
|
||||
@@ -208,10 +239,13 @@
|
||||
## Monitoring & Intelligence Plan
|
||||
|
||||
### Key Competitors to Track
|
||||
|
||||
{{Priority list with rationale}}
|
||||
|
||||
### Monitoring Metrics
|
||||
|
||||
{{What to track:
|
||||
|
||||
- Product updates
|
||||
- Pricing changes
|
||||
- Customer wins/losses
|
||||
@@ -219,7 +253,9 @@
|
||||
- Market messaging}}
|
||||
|
||||
### Intelligence Sources
|
||||
|
||||
{{Where to gather ongoing intelligence:
|
||||
|
||||
- Company websites/blogs
|
||||
- Customer reviews
|
||||
- Industry reports
|
||||
@@ -227,7 +263,9 @@
|
||||
- Patent filings}}
|
||||
|
||||
### Update Cadence
|
||||
|
||||
{{Recommended review schedule:
|
||||
|
||||
- Weekly: {{What to check}}
|
||||
- Monthly: {{What to review}}
|
||||
- Quarterly: {{Deep analysis}}}}
|
||||
@@ -236,8 +274,8 @@
|
||||
|
||||
[[LLM: After completing the document, offer advanced elicitation with these custom options for competitive analysis:
|
||||
|
||||
**Competitive Analysis Elicitation Actions**
|
||||
0. Deep dive on a specific competitor's strategy
|
||||
**Competitive Analysis Elicitation Actions** 0. Deep dive on a specific competitor's strategy
|
||||
|
||||
1. Analyze competitive dynamics in a specific segment
|
||||
2. War game competitive responses to your moves
|
||||
3. Explore partnership vs. competition scenarios
|
||||
@@ -248,4 +286,4 @@
|
||||
8. If only we had known about [competitor X's plan]...
|
||||
9. Proceed to next section
|
||||
|
||||
These replace the standard elicitation options when working on competitive analysis documents.]]
|
||||
These replace the standard elicitation options when working on competitive analysis documents.]]
|
||||
|
||||
@@ -29,7 +29,8 @@
|
||||
- Routing configuration
|
||||
- Testing setup and patterns
|
||||
- Build and development scripts
|
||||
- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
|
||||
|
||||
- Use this analysis to ensure your frontend architecture aligns with the starter's patterns
|
||||
|
||||
3. If no frontend starter is mentioned but this is a new UI, ensure we know what the ui language and framework is:
|
||||
|
||||
|
||||
@@ -18,23 +18,23 @@ This unified approach combines what would traditionally be separate backend and
|
||||
|
||||
1. Review the PRD and other documents for mentions of:
|
||||
|
||||
- Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
|
||||
- Monorepo templates (e.g., Nx, Turborepo starters)
|
||||
- Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
|
||||
- Existing projects being extended or cloned
|
||||
- Fullstack starter templates (e.g., T3 Stack, MEAN/MERN starters, Django + React templates)
|
||||
- Monorepo templates (e.g., Nx, Turborepo starters)
|
||||
- Platform-specific starters (e.g., Vercel templates, AWS Amplify starters)
|
||||
- Existing projects being extended or cloned
|
||||
|
||||
2. If starter templates or existing projects are mentioned:
|
||||
|
||||
- Ask the user to provide access (links, repos, or files)
|
||||
- Analyze to understand pre-configured choices and constraints
|
||||
- Note any architectural decisions already made
|
||||
- Identify what can be modified vs what must be retained
|
||||
- Ask the user to provide access (links, repos, or files)
|
||||
- Analyze to understand pre-configured choices and constraints
|
||||
- Note any architectural decisions already made
|
||||
- Identify what can be modified vs what must be retained
|
||||
|
||||
3. If no starter is mentioned but this is greenfield:
|
||||
|
||||
- Suggest appropriate fullstack starters based on tech preferences
|
||||
- Consider platform-specific options (Vercel, AWS, etc.)
|
||||
- Let user decide whether to use one
|
||||
- Suggest appropriate fullstack starters based on tech preferences
|
||||
- Consider platform-specific options (Vercel, AWS, etc.)
|
||||
- Let user decide whether to use one
|
||||
|
||||
4. Document the decision and any constraints it imposes
|
||||
|
||||
@@ -333,10 +333,12 @@ servers:
|
||||
2. Consider both frontend and backend components
|
||||
3. Define clear boundaries and interfaces between components
|
||||
4. For each component, specify:
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
- Primary responsibility
|
||||
- Key interfaces/APIs exposed
|
||||
- Dependencies on other components
|
||||
- Technology specifics based on tech stack choices
|
||||
|
||||
5. Create component diagrams where helpful
|
||||
6. After presenting all components, apply `tasks#advanced-elicitation` protocol]]
|
||||
|
||||
|
||||
@@ -9,13 +9,17 @@
|
||||
## Research Objectives & Methodology
|
||||
|
||||
### Research Objectives
|
||||
|
||||
{{List the primary objectives of this market research:
|
||||
|
||||
- What decisions will this research inform?
|
||||
- What specific questions need to be answered?
|
||||
- What are the success criteria for this research?}}
|
||||
|
||||
### Research Methodology
|
||||
|
||||
{{Describe the research approach:
|
||||
|
||||
- Data sources used (primary/secondary)
|
||||
- Analysis frameworks applied
|
||||
- Data collection timeframe
|
||||
@@ -24,7 +28,9 @@
|
||||
## Market Overview
|
||||
|
||||
### Market Definition
|
||||
|
||||
{{Define the market being analyzed:
|
||||
|
||||
- Product/service category
|
||||
- Geographic scope
|
||||
- Customer segments included
|
||||
@@ -33,17 +39,21 @@
|
||||
### Market Size & Growth
|
||||
|
||||
[[LLM: Guide through TAM, SAM, SOM calculations with clear assumptions. Use one or more approaches:
|
||||
|
||||
- Top-down: Start with industry data, narrow down
|
||||
- Bottom-up: Build from customer/unit economics
|
||||
- Value theory: Based on value provided vs. alternatives]]
|
||||
|
||||
#### Total Addressable Market (TAM)
|
||||
|
||||
{{Calculate and explain the total market opportunity}}
|
||||
|
||||
#### Serviceable Addressable Market (SAM)
|
||||
|
||||
{{Define the portion of TAM you can realistically reach}}
|
||||
|
||||
#### Serviceable Obtainable Market (SOM)
|
||||
|
||||
{{Estimate the portion you can realistically capture}}
|
||||
|
||||
### Market Trends & Drivers
|
||||
@@ -51,15 +61,19 @@
|
||||
[[LLM: Analyze key trends shaping the market using appropriate frameworks like PESTEL]]
|
||||
|
||||
#### Key Market Trends
|
||||
|
||||
{{List and explain 3-5 major trends:
|
||||
|
||||
- Trend 1: Description and impact
|
||||
- Trend 2: Description and impact
|
||||
- etc.}}
|
||||
|
||||
#### Growth Drivers
|
||||
|
||||
{{Identify primary factors driving market growth}}
|
||||
|
||||
#### Market Inhibitors
|
||||
|
||||
{{Identify factors constraining market growth}}
|
||||
|
||||
## Customer Analysis
|
||||
@@ -69,6 +83,7 @@
|
||||
[[LLM: For each segment, create detailed profiles including demographics/firmographics, psychographics, behaviors, needs, and willingness to pay]]
|
||||
|
||||
#### Segment 1: {{Segment Name}}
|
||||
|
||||
- **Description:** {{Brief overview}}
|
||||
- **Size:** {{Number of customers/market value}}
|
||||
- **Characteristics:** {{Key demographics/firmographics}}
|
||||
@@ -83,12 +98,15 @@
|
||||
[[LLM: Uncover what customers are really trying to accomplish]]
|
||||
|
||||
#### Functional Jobs
|
||||
|
||||
{{List practical tasks and objectives customers need to complete}}
|
||||
|
||||
#### Emotional Jobs
|
||||
|
||||
{{Describe feelings and perceptions customers seek}}
|
||||
|
||||
#### Social Jobs
|
||||
|
||||
{{Explain how customers want to be perceived by others}}
|
||||
|
||||
### Customer Journey Mapping
|
||||
@@ -96,6 +114,7 @@
|
||||
[[LLM: Map the end-to-end customer experience for primary segments]]
|
||||
|
||||
{{For primary customer segment:
|
||||
|
||||
1. **Awareness:** How they discover solutions
|
||||
2. **Consideration:** Evaluation criteria and process
|
||||
3. **Purchase:** Decision triggers and barriers
|
||||
@@ -106,13 +125,17 @@
|
||||
## Competitive Landscape
|
||||
|
||||
### Market Structure
|
||||
|
||||
{{Describe the overall competitive environment:
|
||||
|
||||
- Number of competitors
|
||||
- Market concentration
|
||||
- Competitive intensity}}
|
||||
|
||||
### Major Players Analysis
|
||||
|
||||
{{For top 3-5 competitors:
|
||||
|
||||
- Company name and brief description
|
||||
- Market share estimate
|
||||
- Key strengths and weaknesses
|
||||
@@ -120,7 +143,9 @@
|
||||
- Pricing strategy}}
|
||||
|
||||
### Competitive Positioning
|
||||
|
||||
{{Analyze how competitors are positioned:
|
||||
|
||||
- Value propositions
|
||||
- Differentiation strategies
|
||||
- Market gaps and opportunities}}
|
||||
@@ -132,22 +157,29 @@
|
||||
[[LLM: Analyze each force with specific evidence and implications]]
|
||||
|
||||
#### Supplier Power: {{Low/Medium/High}}
|
||||
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Buyer Power: {{Low/Medium/High}}
|
||||
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Competitive Rivalry: {{Low/Medium/High}}
|
||||
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Threat of New Entry: {{Low/Medium/High}}
|
||||
|
||||
{{Analysis and implications}}
|
||||
|
||||
#### Threat of Substitutes: {{Low/Medium/High}}
|
||||
|
||||
{{Analysis and implications}}
|
||||
|
||||
### Technology Adoption Lifecycle Stage
|
||||
|
||||
{{Identify where the market is in the adoption curve:
|
||||
|
||||
- Current stage and evidence
|
||||
- Implications for strategy
|
||||
- Expected progression timeline}}
|
||||
@@ -159,6 +191,7 @@
|
||||
[[LLM: Identify specific opportunities based on the analysis]]
|
||||
|
||||
#### Opportunity 1: {{Name}}
|
||||
|
||||
- **Description:** {{What is the opportunity?}}
|
||||
- **Size/Potential:** {{Quantify if possible}}
|
||||
- **Requirements:** {{What's needed to capture it?}}
|
||||
@@ -169,21 +202,27 @@
|
||||
### Strategic Recommendations
|
||||
|
||||
#### Go-to-Market Strategy
|
||||
|
||||
{{Recommend approach for market entry/expansion:
|
||||
|
||||
- Target segment prioritization
|
||||
- Positioning strategy
|
||||
- Channel strategy
|
||||
- Partnership opportunities}}
|
||||
|
||||
#### Pricing Strategy
|
||||
|
||||
{{Based on willingness to pay analysis and competitive landscape:
|
||||
|
||||
- Recommended pricing model
|
||||
- Price points/ranges
|
||||
- Value metric
|
||||
- Competitive positioning}}
|
||||
|
||||
#### Risk Mitigation
|
||||
|
||||
{{Key risks and mitigation strategies:
|
||||
|
||||
- Market risks
|
||||
- Competitive risks
|
||||
- Execution risks
|
||||
@@ -192,20 +231,23 @@
|
||||
## Appendices
|
||||
|
||||
### A. Data Sources
|
||||
|
||||
{{List all sources used in the research}}
|
||||
|
||||
### B. Detailed Calculations
|
||||
|
||||
{{Include any complex calculations or models}}
|
||||
|
||||
### C. Additional Analysis
|
||||
|
||||
{{Any supplementary analysis not included in main body}}
|
||||
|
||||
---
|
||||
|
||||
[[LLM: After completing the document, offer advanced elicitation with these custom options for market research:
|
||||
|
||||
**Market Research Elicitation Actions**
|
||||
0. Expand market sizing calculations with sensitivity analysis
|
||||
**Market Research Elicitation Actions** 0. Expand market sizing calculations with sensitivity analysis
|
||||
|
||||
1. Deep dive into a specific customer segment
|
||||
2. Analyze an emerging market trend in detail
|
||||
3. Compare this market to an analogous market
|
||||
@@ -216,4 +258,4 @@
|
||||
8. If only we had considered [X market factor]...
|
||||
9. Proceed to next section
|
||||
|
||||
These replace the standard elicitation options when working on market research documents.]]
|
||||
These replace the standard elicitation options when working on market research documents.]]
|
||||
|
||||
@@ -1,8 +1,9 @@
|
||||
# Project Brief: {{Project Name}}
|
||||
|
||||
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
|
||||
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
|
||||
|
||||
Start by asking the user which mode they prefer:
|
||||
|
||||
1. **Interactive Mode** - Work through each section collaboratively
|
||||
2. **YOLO Mode** - Generate complete draft for review and refinement
|
||||
|
||||
@@ -11,6 +12,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
## Executive Summary
|
||||
|
||||
[[LLM: Create a concise overview that captures the essence of the project. Include:
|
||||
|
||||
- Product concept in 1-2 sentences
|
||||
- Primary problem being solved
|
||||
- Target market identification
|
||||
@@ -21,6 +23,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
## Problem Statement
|
||||
|
||||
[[LLM: Articulate the problem with clarity and evidence. Address:
|
||||
|
||||
- Current state and pain points
|
||||
- Impact of the problem (quantify if possible)
|
||||
- Why existing solutions fall short
|
||||
@@ -31,6 +34,7 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
## Proposed Solution
|
||||
|
||||
[[LLM: Describe the solution approach at a high level. Include:
|
||||
|
||||
- Core concept and approach
|
||||
- Key differentiators from existing solutions
|
||||
- Why this solution will succeed where others haven't
|
||||
@@ -41,15 +45,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
## Target Users
|
||||
|
||||
[[LLM: Define and characterize the intended users with specificity. For each user segment include:
|
||||
|
||||
- Demographic/firmographic profile
|
||||
- Current behaviors and workflows
|
||||
- Specific needs and pain points
|
||||
- Goals they're trying to achieve]]
|
||||
|
||||
### Primary User Segment: {{Segment Name}}
|
||||
|
||||
{{Detailed description of primary users}}
|
||||
|
||||
### Secondary User Segment: {{Segment Name}}
|
||||
|
||||
{{Description of secondary users if applicable}}
|
||||
|
||||
## Goals & Success Metrics
|
||||
@@ -57,16 +64,19 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Establish clear objectives and how to measure success. Make goals SMART (Specific, Measurable, Achievable, Relevant, Time-bound)]]
|
||||
|
||||
### Business Objectives
|
||||
|
||||
- {{Objective 1 with metric}}
|
||||
- {{Objective 2 with metric}}
|
||||
- {{Objective 3 with metric}}
|
||||
|
||||
### User Success Metrics
|
||||
|
||||
- {{How users will measure value}}
|
||||
- {{Engagement metrics}}
|
||||
- {{Satisfaction indicators}}
|
||||
|
||||
### Key Performance Indicators (KPIs)
|
||||
|
||||
- {{KPI 1: Definition and target}}
|
||||
- {{KPI 2: Definition and target}}
|
||||
- {{KPI 3: Definition and target}}
|
||||
@@ -76,15 +86,18 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Define the minimum viable product clearly. Be specific about what's in and what's out. Help user distinguish must-haves from nice-to-haves.]]
|
||||
|
||||
### Core Features (Must Have)
|
||||
|
||||
- **Feature 1:** {{Brief description and why it's essential}}
|
||||
- **Feature 2:** {{Brief description and why it's essential}}
|
||||
- **Feature 3:** {{Brief description and why it's essential}}
|
||||
|
||||
### Out of Scope for MVP
|
||||
|
||||
- {{Feature/capability explicitly not in MVP}}
|
||||
- {{Feature/capability to be considered post-MVP}}
|
||||
|
||||
### MVP Success Criteria
|
||||
|
||||
{{Define what constitutes a successful MVP launch}}
|
||||
|
||||
## Post-MVP Vision
|
||||
@@ -92,12 +105,15 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Outline the longer-term product direction without overcommitting to specifics]]
|
||||
|
||||
### Phase 2 Features
|
||||
|
||||
{{Next priority features after MVP success}}
|
||||
|
||||
### Long-term Vision
|
||||
|
||||
{{Where this product could go in 1-2 years}}
|
||||
|
||||
### Expansion Opportunities
|
||||
|
||||
{{Potential new markets, use cases, or integrations}}
|
||||
|
||||
## Technical Considerations
|
||||
@@ -105,17 +121,20 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Document known technical constraints and preferences. Note these are initial thoughts, not final decisions.]]
|
||||
|
||||
### Platform Requirements
|
||||
|
||||
- **Target Platforms:** {{Web, mobile, desktop, etc.}}
|
||||
- **Browser/OS Support:** {{Specific requirements}}
|
||||
- **Performance Requirements:** {{Load times, concurrent users, etc.}}
|
||||
|
||||
### Technology Preferences
|
||||
|
||||
- **Frontend:** {{If any preferences exist}}
|
||||
- **Backend:** {{If any preferences exist}}
|
||||
- **Database:** {{If any preferences exist}}
|
||||
- **Hosting/Infrastructure:** {{Cloud preferences, on-prem requirements}}
|
||||
|
||||
### Architecture Considerations
|
||||
|
||||
- **Repository Structure:** {{Initial thoughts on monorepo vs. polyrepo}}
|
||||
- **Service Architecture:** {{Initial thoughts on monolith vs. microservices}}
|
||||
- **Integration Requirements:** {{Third-party services, APIs}}
|
||||
@@ -126,12 +145,14 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Clearly state limitations and assumptions to set realistic expectations]]
|
||||
|
||||
### Constraints
|
||||
|
||||
- **Budget:** {{If known}}
|
||||
- **Timeline:** {{Target launch date or development timeframe}}
|
||||
- **Resources:** {{Team size, skill constraints}}
|
||||
- **Technical:** {{Legacy systems, required tech stack}}
|
||||
|
||||
### Key Assumptions
|
||||
|
||||
- {{Assumption about users, market, or technology}}
|
||||
- {{Assumption about resources or support}}
|
||||
- {{Assumption about external dependencies}}
|
||||
@@ -141,37 +162,45 @@ Before beginning, understand what inputs are available (brainstorming results, m
|
||||
[[LLM: Identify unknowns and potential challenges proactively]]
|
||||
|
||||
### Key Risks
|
||||
|
||||
- **Risk 1:** {{Description and potential impact}}
|
||||
- **Risk 2:** {{Description and potential impact}}
|
||||
- **Risk 3:** {{Description and potential impact}}
|
||||
|
||||
### Open Questions
|
||||
|
||||
- {{Question needing research or decision}}
|
||||
- {{Question about technical approach}}
|
||||
- {{Question about market or users}}
|
||||
|
||||
### Areas Needing Further Research
|
||||
|
||||
- {{Topic requiring deeper investigation}}
|
||||
- {{Validation needed before proceeding}}
|
||||
|
||||
## Appendices
|
||||
|
||||
### A. Research Summary
|
||||
|
||||
{{If applicable, summarize key findings from:
|
||||
|
||||
- Market research
|
||||
- Competitive analysis
|
||||
- Competitive analysis
|
||||
- User interviews
|
||||
- Technical feasibility studies}}
|
||||
|
||||
### B. Stakeholder Input
|
||||
|
||||
{{Key feedback or requirements from stakeholders}}
|
||||
|
||||
### C. References
|
||||
|
||||
{{Links to relevant documents, research, or examples}}
|
||||
|
||||
## Next Steps
|
||||
|
||||
### Immediate Actions
|
||||
|
||||
1. {{First concrete next step}}
|
||||
2. {{Second concrete next step}}
|
||||
3. {{Third concrete next step}}
|
||||
@@ -184,8 +213,8 @@ This Project Brief provides the full context for {{Project Name}}. Please start
|
||||
|
||||
[[LLM: After completing each major section (not subsections), offer advanced elicitation with these custom options for project briefs:
|
||||
|
||||
**Project Brief Elicitation Actions**
|
||||
0. Expand section with more specific details
|
||||
**Project Brief Elicitation Actions** 0. Expand section with more specific details
|
||||
|
||||
1. Validate against similar successful products
|
||||
2. Stress test assumptions with edge cases
|
||||
3. Explore alternative solution approaches
|
||||
|
||||
@@ -7,8 +7,9 @@ You are now operating as a specialized AI agent from the BMAD-METHOD framework.
|
||||
1. **Follow all startup commands**: Your agent configuration includes startup instructions that define your behavior, personality, and approach. These MUST be followed exactly.
|
||||
|
||||
2. **Resource Navigation**: This bundle contains all resources you need. Resources are marked with tags like:
|
||||
- `==================== START: folder#filename ====================`
|
||||
- `==================== END: folder#filename ====================`
|
||||
|
||||
- `==================== START: folder#filename ====================`
|
||||
- `==================== END: folder#filename ====================`
|
||||
|
||||
When you need to reference a resource mentioned in your instructions:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user