Merge branch 'main' into feat/issue-1034-markdownlint
This commit is contained in:
Brian
GitHub
commit
ca0d1fd364
|
|
@ -95,7 +95,6 @@ stepsCompleted: [1, 2, 3]
|
|||
workflowType: 'party-mode'
|
||||
user_name: '{{user_name}}'
|
||||
date: '{{date}}'
|
||||
current_year: '{{current_year}}'
|
||||
agents_loaded: true
|
||||
party_active: false
|
||||
workflow_completed: true
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
|
|||
|
||||
- `project_name`, `output_folder`, `user_name`
|
||||
- `communication_language`, `document_output_language`, `user_skill_level`
|
||||
- `date`, `current_year`, `current_month` as system-generated values
|
||||
- `date` as a system-generated value
|
||||
- Agent manifest path: `{project-root}/{bmad_folder}/_cfg/agent-manifest.csv`
|
||||
|
||||
### Paths
|
||||
|
|
@ -118,7 +118,6 @@ stepsCompleted: [1]
|
|||
workflowType: 'party-mode'
|
||||
user_name: '{{user_name}}'
|
||||
date: '{{date}}'
|
||||
current_year: '{{current_year}}'
|
||||
agents_loaded: true
|
||||
party_active: true
|
||||
exit_triggers: ['*exit', 'goodbye', 'end party', 'quit']
|
||||
|
|
|
|||
|
|
@ -140,14 +140,14 @@ I see {{epic_count}} epics with {{story_count}} total stories.
|
|||
</check>
|
||||
|
||||
<action>Search for relevant starter templates with websearch, examples:
|
||||
<WebSearch>{{primary_technology}} starter template CLI create command latest {date}</WebSearch>
|
||||
<WebSearch>{{primary_technology}} boilerplate generator latest options</WebSearch>
|
||||
Search the web: "{{primary_technology}} starter template CLI create command latest"
|
||||
Search the web: "{{primary_technology}} boilerplate generator latest options"
|
||||
</action>
|
||||
|
||||
<check if="starter_templates_found">
|
||||
<action>Investigate what each starter provides:
|
||||
<WebSearch>{{starter_name}} default setup technologies included latest</WebSearch>
|
||||
<WebSearch>{{starter_name}} project structure file organization</WebSearch>
|
||||
Search the web: "{{starter_name}} default setup technologies included latest"
|
||||
Search the web: "{{starter_name}} project structure file organization"
|
||||
</action>
|
||||
|
||||
<check if="{user_skill_level} == 'expert'">
|
||||
|
|
@ -176,7 +176,7 @@ I see {{epic_count}} epics with {{story_count}} total stories.
|
|||
|
||||
<check if="user_accepts_starter">
|
||||
<action>Get current starter command and options:
|
||||
<WebSearch>{{starter_name}} CLI command options flags latest 2024</WebSearch>
|
||||
Search the web: "{{starter_name}} CLI command options flags latest"
|
||||
</action>
|
||||
|
||||
<action>Document the initialization command:
|
||||
|
|
@ -282,7 +282,7 @@ Let's work through the remaining {{remaining_count}} decisions."
|
|||
|
||||
<step n="4" goal="Facilitate collaborative decision making" repeat="for-each-decision">
|
||||
<critical>Each decision must be made WITH the user, not FOR them</critical>
|
||||
<critical>ALWAYS verify current versions using WebSearch - NEVER trust hardcoded versions</critical>
|
||||
<critical>ALWAYS search the web to verify current versions - NEVER trust hardcoded versions</critical>
|
||||
|
||||
<action>For each decision in priority order:</action>
|
||||
|
||||
|
|
@ -327,8 +327,8 @@ Let's work through the remaining {{remaining_count}} decisions."
|
|||
|
||||
<check if="decision_involves_specific_technology">
|
||||
<action>Verify current stable version:
|
||||
<WebSearch>{{technology}} latest stable version 2024</WebSearch>
|
||||
<WebSearch>{{technology}} current LTS version</WebSearch>
|
||||
Search the web: "{{technology}} latest stable version"
|
||||
Search the web: "{{technology}} current LTS version"
|
||||
</action>
|
||||
|
||||
<action>Update decision record with verified version:
|
||||
|
|
|
|||
|
|
@ -144,7 +144,6 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
|||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `create-architecture` - Produce a Scale Adaptive Architecture
|
||||
- `validate-architecture` - Validate architecture document
|
||||
- `implementation-readiness` - Validate PRD + Architecture + Epics + UX (optional)
|
||||
|
||||
**Communication Style:** Comprehensive yet pragmatic. Uses architectural metaphors. Balances technical depth with accessibility. Connects decisions to business value.
|
||||
|
|
@ -644,7 +643,6 @@ Many workflows have optional validation workflows that perform independent revie
|
|||
| Validation | Agent | Validates |
|
||||
| -------------------------- | ----------- | ------------------------------------------ |
|
||||
| `implementation-readiness` | Architect | PRD + Architecture + Epics + UX (optional) |
|
||||
| `validate-architecture` | Architect | Architecture document |
|
||||
| `validate-design` | UX Designer | UX specification and artifacts |
|
||||
| `validate-create-story` | SM | Story draft |
|
||||
|
||||
|
|
@ -976,7 +974,7 @@ Quick reference for agent selection:
|
|||
| **PM** | 📋 | 2 (Planning) | prd, tech-spec, epics-stories | Planning, requirements docs |
|
||||
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
|
||||
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
|
||||
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story, story-context | Story management, sprint coordination |
|
||||
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story | Story management, sprint coordination |
|
||||
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review | Implementation, coding |
|
||||
| **TEA** | 🧪 | All Phases | framework, atdd, automate, trace, ci | Testing, quality assurance |
|
||||
| **Paige (Tech Writer)** | 📚 | All Phases | document-project, diagrams, validation | Documentation, diagrams |
|
||||
|
|
|
|||
|
|
@ -250,8 +250,8 @@ Without AI-optimized documentation, workflows fail:
|
|||
|
||||
- **tech-spec** (Quick Flow) can't auto-detect stack/patterns → Makes wrong assumptions
|
||||
- **PRD** (BMad Method) can't reference existing code → Designs incompatible features
|
||||
- **architecture** can't build on existing structure → Suggests conflicting patterns
|
||||
- **story-context** can't inject existing patterns → Dev agent rewrites working code
|
||||
- **create-architecture** can't build on existing structure → Suggests conflicting patterns
|
||||
- **create-story** can't provide existing pattern context → Stories lack integration guidance
|
||||
- **dev-story** invents implementations → Breaks existing integrations
|
||||
|
||||
### Key Principle
|
||||
|
|
@ -370,7 +370,7 @@ When workflow-init asks about your work:
|
|||
|
||||
### 4. Respect Existing Patterns
|
||||
|
||||
Tech-spec and story-context will detect conventions. Follow them unless explicitly modernizing.
|
||||
Tech-spec and create-story workflows will detect conventions from existing documentation. Follow them unless explicitly modernizing.
|
||||
|
||||
### 5. Plan Integration Points Explicitly
|
||||
|
||||
|
|
@ -446,7 +446,7 @@ Document in tech-spec/architecture:
|
|||
- Analyzes existing auth patterns
|
||||
- Confirms conventions
|
||||
- Creates tech-spec.md + epic + 3-5 stories
|
||||
3. **Implement:** Load SM → `sprint-planning` → `create-story` → `story-context`
|
||||
3. **Implement:** Load SM → `sprint-planning` → `create-story`
|
||||
Load DEV → `dev-story` for each story
|
||||
4. **Review:** Load DEV → `code-review`
|
||||
|
||||
|
|
@ -512,12 +512,9 @@ Document in tech-spec/architecture:
|
|||
- `product-brief` - Strategic document
|
||||
3. **Plan:** Load PM → `prd` (comprehensive FRs/NFRs)
|
||||
4. **Solution:**
|
||||
- `create-architecture` - Full system architecture
|
||||
- `integration-planning` - Phased migration strategy
|
||||
- `create-architecture` - Multi-tenancy architecture
|
||||
- `validate-architecture` - External review
|
||||
- `create-architecture` - Full system architecture including multi-tenancy design
|
||||
- `create-epics-and-stories` - Create epics and stories
|
||||
- `implementation-readiness` - Executive approval
|
||||
- `implementation-readiness` - Final validation before implementation
|
||||
5. **Implement:** Phased sprint-based (50+ stories)
|
||||
|
||||
**Time:** 3-6 months
|
||||
|
|
@ -564,7 +561,7 @@ Document in tech-spec/architecture:
|
|||
**Solution:**
|
||||
|
||||
1. Ensure `document-project` captured existing architecture
|
||||
2. Check `story-context` - should document integration points
|
||||
2. Check story files created by `create-story` - should include integration context
|
||||
3. In tech-spec/architecture - explicitly document:
|
||||
- Which existing modules to modify
|
||||
- What APIs/services to integrate with
|
||||
|
|
@ -597,7 +594,7 @@ Document in tech-spec/architecture:
|
|||
|
||||
1. Check convention detection (Quick Spec Flow should detect patterns)
|
||||
2. Review documentation - ensure `document-project` captured patterns
|
||||
3. Use `story-context` - injects pattern guidance
|
||||
3. Use `create-story` workflow - it loads context from existing documentation
|
||||
4. Add to code-review checklist: pattern adherence, convention consistency
|
||||
5. Run retrospective to identify deviations early
|
||||
|
||||
|
|
@ -626,9 +623,9 @@ prd # BMad Method/Enterprise tracks
|
|||
|
||||
# Phase 3: Solutioning (BMad Method/Enterprise)
|
||||
# Architect agent:
|
||||
architecture # Create/extend architecture
|
||||
create-architecture # Create/extend architecture
|
||||
create-epics-and-stories # Create epics and stories (after architecture)
|
||||
implementation-readiness # Final validation
|
||||
implementation-readiness # Final validation
|
||||
|
||||
# Phase 4: Implementation (All Tracks)
|
||||
# SM agent:
|
||||
|
|
|
|||
|
|
@ -193,15 +193,9 @@ PRDs are for Level 2-4 projects with multiple features requiring product-level c
|
|||
|
||||
## Implementation
|
||||
|
||||
### Q: Do I need story-context for every story?
|
||||
### Q: Does create-story include implementation context?
|
||||
|
||||
**A:** Technically no, but it's recommended. story-context provides implementation-specific guidance, references existing patterns, and injects expertise. Skip it only if:
|
||||
|
||||
- Very simple story (self-explanatory)
|
||||
- You're already expert in the area
|
||||
- Time is extremely limited
|
||||
|
||||
For Level 0-1 using tech-spec, story-context is less critical because tech-spec is already comprehensive.
|
||||
**A:** Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.
|
||||
|
||||
### Q: How do I mark a story as done?
|
||||
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@ backlog → drafted → ready-for-dev → in-progress → review → done
|
|||
|
||||
- **backlog** - Story exists in epic but not yet drafted
|
||||
- **drafted** - Story file created by SM via create-story
|
||||
- **ready-for-dev** - Story has context, ready for DEV via story-context
|
||||
- **ready-for-dev** - Story drafted and reviewed, ready for DEV
|
||||
- **in-progress** - DEV is implementing via dev-story
|
||||
- **review** - Implementation complete, awaiting code-review
|
||||
- **done** - Completed with DoD met
|
||||
|
|
@ -238,7 +238,7 @@ Markdown file containing story details: description, acceptance criteria, techni
|
|||
|
||||
### Story Context
|
||||
|
||||
Technical guidance document created via story-context workflow that provides implementation-specific context, references existing patterns, suggests approaches, and injects expertise for the specific story.
|
||||
Implementation guidance embedded within story files during the create-story workflow. Provides implementation-specific context, references existing patterns, suggests approaches, and helps maintain consistency with established codebase conventions.
|
||||
|
||||
### Sprint Planning
|
||||
|
||||
|
|
|
|||
|
|
@ -313,11 +313,10 @@ flowchart LR
|
|||
direction TB
|
||||
D1[Per Epic:<br/>epic context]
|
||||
D2[Per Story:<br/>create-story]
|
||||
D3[story-context]
|
||||
D4[dev-story]
|
||||
D5[code-review]
|
||||
D6[SM, DEV]
|
||||
D1 ~~~ D2 ~~~ D3 ~~~ D4 ~~~ D5 ~~~ D6
|
||||
D3[dev-story]
|
||||
D4[code-review]
|
||||
D5[SM, DEV]
|
||||
D1 ~~~ D2 ~~~ D3 ~~~ D4 ~~~ D5
|
||||
end
|
||||
|
||||
P1 --> P2
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ For a visual representation of the complete workflow, see: [workflow-method-gree
|
|||
Stories move through these states in the sprint status file:
|
||||
|
||||
1. **TODO** - Story identified but not started
|
||||
2. **IN PROGRESS** - Story being implemented (create-story → story-context → dev-story)
|
||||
2. **IN PROGRESS** - Story being implemented (create-story → dev-story)
|
||||
3. **READY FOR REVIEW** - Implementation complete, awaiting code review
|
||||
4. **DONE** - Accepted and complete
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on industry/domain analysis with web research
|
||||
- Web search capabilities with {{current_year}} data are enabled
|
||||
- Web search is required to verify and supplement your knowledge with current facts
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ Start with domain scope understanding:
|
|||
|
||||
**Research Approach:**
|
||||
|
||||
- Current {{current_year}} web data with rigorous source verification
|
||||
- All claims verified against current public sources
|
||||
- Multi-source validation for critical domain claims
|
||||
- Confidence levels for uncertain domain information
|
||||
- Comprehensive domain coverage with industry-specific insights
|
||||
|
|
@ -66,7 +66,7 @@ For **{{research_topic}}**, I will research:
|
|||
✅ **Economic Factors** - market size, growth projections, economic impact
|
||||
✅ **Supply Chain Analysis** - value chain, ecosystem, partnerships
|
||||
|
||||
**All using current {{current_year}} web data with source verification.**
|
||||
**All claims verified against current public sources.**
|
||||
|
||||
**Does this domain research scope and approach align with your goals?**
|
||||
[C] Continue - Begin domain research with this scope
|
||||
|
|
@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
|
|||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-industry-analysis.md`
|
||||
- Load: `./step-02-domain-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current {{current_year}} web data with rigorous source verification
|
||||
- All claims verified against current public sources
|
||||
- Multi-source validation for critical domain claims
|
||||
- Confidence level framework for uncertain information
|
||||
- Comprehensive domain coverage with industry-specific insights
|
||||
|
|
@ -111,7 +111,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
✅ Domain research scope clearly confirmed with user
|
||||
✅ All domain analysis areas identified and explained
|
||||
✅ Research methodology with {{current_year}} data emphasized
|
||||
✅ Research methodology emphasized
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Scope confirmation documented when user proceeds
|
||||
✅ Proper routing to next domain research step
|
||||
|
|
@ -120,7 +120,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
❌ Not clearly confirming domain research scope with user
|
||||
❌ Missing critical domain analysis areas
|
||||
❌ Not emphasizing {{current_year}} web data requirement
|
||||
❌ Not explaining that web search is required for current facts
|
||||
❌ Not presenting [C] continue option
|
||||
❌ Proceeding without user scope confirmation
|
||||
❌ Not routing to next domain research step
|
||||
|
|
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-industry-analysis.md` to begin industry analysis with current {{current_year}} web data.
|
||||
After user selects 'C', load `./step-02-domain-analysis.md` to begin industry analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual domain research yet, just confirming the research approach and scope!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current industry data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN INDUSTRY ANALYST, not content generator
|
||||
- 💬 FOCUS on market size, growth, and industry dynamics
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct industry analysis focusing on market size, growth, and industry dynamics using current {{current_year}} web data with rigorous source verification.
|
||||
Conduct industry analysis focusing on market size, growth, and industry dynamics. Search the web to verify and supplement current facts.
|
||||
|
||||
## INDUSTRY ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Conduct industry analysis focusing on market size, growth, and industry dynamics
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different industry areas simultaneously and thoroughly.
|
||||
|
||||
Start with industry research approach:
|
||||
"Now I'll conduct **industry analysis** for **{{research_topic}}** using current {{current_year}} web data to understand market dynamics.
|
||||
"Now I'll conduct **industry analysis** for **{{research_topic}}** to understand market dynamics.
|
||||
|
||||
**Industry Analysis Focus:**
|
||||
|
||||
|
|
@ -56,10 +56,10 @@ Start with industry research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} market size value {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} market growth rate dynamics {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} market segmentation structure {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} industry trends evolution {{current_year}}"`
|
||||
Search the web: "{{research_topic}} market size value"
|
||||
Search the web: "{{research_topic}} market growth rate dynamics"
|
||||
Search the web: "{{research_topic}} market segmentation structure"
|
||||
Search the web: "{{research_topic}} industry trends evolution"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -104,11 +104,11 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Market Size and Valuation
|
||||
|
||||
[Market size analysis with source citations]
|
||||
_Total Market Size: [Current market valuation with {{current_year}} data]_
|
||||
_Total Market Size: [Current market valuation]_
|
||||
_Growth Rate: [CAGR and market growth projections]_
|
||||
_Market Segments: [Size and value of key market segments]_
|
||||
_Economic Impact: [Economic contribution and value creation]_
|
||||
_Source: [URL with {{current_year}} market size data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Dynamics and Growth
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _Growth Drivers: [Key factors driving market growth]_
|
|||
_Growth Barriers: [Factors limiting market expansion]_
|
||||
_Cyclical Patterns: [Industry seasonality and cycles]_
|
||||
_Market Maturity: [Life cycle stage and development phase]_
|
||||
_Source: [URL with {{current_year}} market dynamics data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Structure and Segmentation
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ _Primary Segments: [Key market segments and their characteristics]_
|
|||
_Sub-segment Analysis: [Detailed breakdown of market sub-segments]_
|
||||
_Geographic Distribution: [Regional market variations and concentrations]_
|
||||
_Vertical Integration: [Supply chain and value chain structure]_
|
||||
_Source: [URL with {{current_year}} market structure data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Trends and Evolution
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ _Emerging Trends: [Current industry developments and transformations]_
|
|||
_Historical Evolution: [Industry development over recent years]_
|
||||
_Technology Integration: [How technology is changing the industry]_
|
||||
_Future Outlook: [Projected industry developments and changes]_
|
||||
_Source: [URL with {{current_year}} industry trends data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Dynamics
|
||||
|
||||
|
|
@ -144,14 +144,14 @@ _Market Concentration: [Level of market consolidation and competition]_
|
|||
_Competitive Intensity: [Degree of competition and rivalry]_
|
||||
_Barriers to Entry: [Obstacles for new market entrants]_
|
||||
_Innovation Pressure: [Rate of innovation and change]_
|
||||
_Source: [URL with {{current_year}} competitive dynamics data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **industry analysis** using current {{current_year}} data to understand market dynamics for {{research_topic}}.
|
||||
"I've completed **industry analysis** for {{research_topic}}.
|
||||
|
||||
**Key Industry Findings:**
|
||||
|
||||
|
|
@ -190,7 +190,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in industry web searches
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical market size or growth data
|
||||
❌ Incomplete market structure analysis
|
||||
❌ Not identifying key industry trends
|
||||
|
|
@ -208,7 +208,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use authoritative sources (market research firms, industry associations)
|
||||
- Analyze market size, growth rates, and segmentation data
|
||||
- Study industry trends and evolution patterns
|
||||
- Focus on current {{current_year}} industry data
|
||||
- Search the web to verify facts
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -225,4 +225,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-03-competitive-landscape.md` to analyze competitive landscape, key players, and ecosystem analysis for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} industry data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and search the web to verify facts!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current competitive data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
|
||||
- 💬 FOCUS on key players, market share, and competitive dynamics
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics using current {{current_year}} web data with rigorous source verification.
|
||||
Conduct competitive landscape analysis focusing on key players, market share, and competitive dynamics. Search the web to verify and supplement current facts.
|
||||
|
||||
## COMPETITIVE LANDSCAPE ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Conduct competitive landscape analysis focusing on key players, market share, an
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different competitive areas simultaneously and thoroughly.
|
||||
|
||||
Start with competitive research approach:
|
||||
"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the competitive ecosystem.
|
||||
"Now I'll conduct **competitive landscape analysis** for **{{research_topic}}** to understand the competitive ecosystem.
|
||||
|
||||
**Competitive Landscape Focus:**
|
||||
|
||||
|
|
@ -56,10 +56,10 @@ Start with competitive research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} key players market leaders {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} market share competitive landscape {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} competitive strategies differentiation {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} entry barriers competitive dynamics {{current_year}}"`
|
||||
Search the web: "{{research_topic}} key players market leaders"
|
||||
Search the web: "{{research_topic}} market share competitive landscape"
|
||||
Search the web: "{{research_topic}} competitive strategies differentiation"
|
||||
Search the web: "{{research_topic}} entry barriers competitive dynamics"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ _Market Leaders: [Dominant players and their market positions]_
|
|||
_Major Competitors: [Significant competitors and their specialties]_
|
||||
_Emerging Players: [New entrants and innovative companies]_
|
||||
_Global vs Regional: [Geographic distribution of key players]_
|
||||
_Source: [URL with {{current_year}} competitive data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Share and Competitive Positioning
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _Market Share Distribution: [Current market share breakdown]_
|
|||
_Competitive Positioning: [How players position themselves in the market]_
|
||||
_Value Proposition Mapping: [Different value propositions across players]_
|
||||
_Customer Segments Served: [Different customer bases by competitor]_
|
||||
_Source: [URL with {{current_year}} market share data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Strategies and Differentiation
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ _Cost Leadership Strategies: [Players competing on price and efficiency]_
|
|||
_Differentiation Strategies: [Players competing on unique value]_
|
||||
_Focus/Niche Strategies: [Players targeting specific segments]_
|
||||
_Innovation Approaches: [How different players innovate]_
|
||||
_Source: [URL with {{current_year}} competitive strategies data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Business Models and Value Propositions
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ _Primary Business Models: [How competitors make money]_
|
|||
_Revenue Streams: [Different approaches to monetization]_
|
||||
_Value Chain Integration: [Vertical integration vs partnership models]_
|
||||
_Customer Relationship Models: [How competitors build customer loyalty]_
|
||||
_Source: [URL with {{current_year}} business models data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Dynamics and Entry Barriers
|
||||
|
||||
|
|
@ -144,7 +144,7 @@ _Barriers to Entry: [Obstacles facing new market entrants]_
|
|||
_Competitive Intensity: [Level of rivalry and competitive pressure]_
|
||||
_Market Consolidation Trends: [M&A activity and market concentration]_
|
||||
_Switching Costs: [Costs for customers to switch between providers]_
|
||||
_Source: [URL with {{current_year}} competitive dynamics data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Ecosystem and Partnership Analysis
|
||||
|
||||
|
|
@ -153,14 +153,14 @@ _Supplier Relationships: [Key supplier partnerships and dependencies]_
|
|||
_Distribution Channels: [How competitors reach customers]_
|
||||
_Technology Partnerships: [Strategic technology alliances]_
|
||||
_Ecosystem Control: [Who controls key parts of the value chain]_
|
||||
_Source: [URL with {{current_year}} ecosystem data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **competitive landscape analysis** using current {{current_year}} data to understand the competitive ecosystem for {{research_topic}}.
|
||||
"I've completed **competitive landscape analysis** for {{research_topic}}.
|
||||
|
||||
**Key Competitive Findings:**
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in competitive web searches
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical key players or market leaders
|
||||
❌ Incomplete market share or positioning analysis
|
||||
❌ Not identifying competitive strategies
|
||||
|
|
@ -217,7 +217,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use company websites, annual reports, and investor presentations
|
||||
- Analyze market share data and competitive positioning
|
||||
- Study competitive strategies and differentiation approaches
|
||||
- Focus on current {{current_year}} competitive data
|
||||
- Search the web to verify facts
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -234,4 +234,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-04-regulatory-focus.md` to analyze regulatory requirements, compliance frameworks, and legal considerations for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} competitive data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and search the web to verify facts!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current regulatory data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A REGULATORY ANALYST, not content generator
|
||||
- 💬 FOCUS on compliance requirements and regulatory landscape
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,14 +31,14 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct focused regulatory and compliance analysis using current {{current_year}} web data with emphasis on requirements that impact {{research_topic}}.
|
||||
Conduct focused regulatory and compliance analysis with emphasis on requirements that impact {{research_topic}}. Search the web to verify and supplement current facts.
|
||||
|
||||
## REGULATORY FOCUS SEQUENCE:
|
||||
|
||||
### 1. Begin Regulatory Analysis
|
||||
|
||||
Start with regulatory research approach:
|
||||
"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}** using current {{current_year}} data.
|
||||
"Now I'll focus on **regulatory and compliance requirements** that impact **{{research_topic}}**.
|
||||
|
||||
**Regulatory Focus Areas:**
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Start with regulatory research approach:
|
|||
### 2. Web Search for Specific Regulations
|
||||
|
||||
Search for current regulatory information:
|
||||
`WebSearch: "{{research_topic}} regulations compliance requirements {{current_year}}"`
|
||||
Search the web: "{{research_topic}} regulations compliance requirements"
|
||||
|
||||
**Regulatory focus:**
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Search for current regulatory information:
|
|||
### 3. Web Search for Industry Standards
|
||||
|
||||
Search for current industry standards:
|
||||
`WebSearch: "{{research_topic}} standards best practices {{current_year}}"`
|
||||
Search the web: "{{research_topic}} standards best practices"
|
||||
|
||||
**Standards focus:**
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ Search for current industry standards:
|
|||
### 4. Web Search for Data Privacy Requirements
|
||||
|
||||
Search for current privacy regulations:
|
||||
`WebSearch: "data privacy regulations {{research_topic}} {{current_year}}"`
|
||||
Search the web: "data privacy regulations {{research_topic}}"
|
||||
|
||||
**Privacy focus:**
|
||||
|
||||
|
|
@ -100,32 +100,32 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Applicable Regulations
|
||||
|
||||
[Specific regulations analysis with source citations]
|
||||
_Source: [URL with {{current_year}} regulatory data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Standards and Best Practices
|
||||
|
||||
[Industry standards analysis with source citations]
|
||||
_Source: [URL with {{current_year}} standards data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Compliance Frameworks
|
||||
|
||||
[Compliance frameworks analysis with source citations]
|
||||
_Source: [URL with {{current_year}} compliance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Protection and Privacy
|
||||
|
||||
[Privacy requirements analysis with source citations]
|
||||
_Source: [URL with {{current_year}} privacy data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Licensing and Certification
|
||||
|
||||
[Licensing requirements analysis with source citations]
|
||||
_Source: [URL with {{current_year}} licensing data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Considerations
|
||||
|
||||
[Practical implementation considerations with source citations]
|
||||
_Source: [URL with {{current_year}} implementation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Assessment
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ _Source: [URL with {{current_year}} implementation data]_
|
|||
### 6. Present Analysis and Continue Option
|
||||
|
||||
Show the generated regulatory analysis and present continue option:
|
||||
"I've completed **regulatory requirements analysis** using current {{current_year}} data to understand compliance requirements for {{research_topic}}.
|
||||
"I've completed **regulatory requirements analysis** for {{research_topic}}.
|
||||
|
||||
**Key Regulatory Findings:**
|
||||
|
||||
|
|
@ -162,7 +162,7 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Applicable regulations identified with current {{current_year}} citations
|
||||
✅ Applicable regulations identified with current citations
|
||||
✅ Industry standards and best practices documented
|
||||
✅ Compliance frameworks clearly mapped
|
||||
✅ Data protection requirements analyzed
|
||||
|
|
@ -172,7 +172,7 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in regulatory web searches
|
||||
❌ Relying on training data instead of web search for current facts
|
||||
❌ Missing critical regulatory requirements for the domain
|
||||
❌ Not providing implementation considerations for compliance
|
||||
❌ Not completing risk assessment for regulatory compliance
|
||||
|
|
@ -200,6 +200,6 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-04-technical-trends.md` to analyze technical trends and innovations in the domain.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-technical-trends.md` to analyze technical trends and innovations in the domain.
|
||||
|
||||
Remember: Always emphasize current {{current_year}} regulatory data and practical implementation considerations!
|
||||
Remember: Search the web to verify regulatory facts and provide practical implementation considerations!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current technical data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNOLOGY ANALYST, not content generator
|
||||
- 💬 FOCUS on emerging technologies and innovation patterns
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,14 +31,14 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive technical trends analysis using current {{current_year}} web data with emphasis on innovations and emerging technologies impacting {{research_topic}}.
|
||||
Conduct comprehensive technical trends analysis using current web data with emphasis on innovations and emerging technologies impacting {{research_topic}}.
|
||||
|
||||
## TECHNICAL TRENDS SEQUENCE:
|
||||
|
||||
### 1. Begin Technical Trends Analysis
|
||||
|
||||
Start with technology research approach:
|
||||
"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current {{current_year}} data.
|
||||
"Now I'll conduct **technical trends and emerging technologies** analysis for **{{research_topic}}** using current data.
|
||||
|
||||
**Technical Trends Focus:**
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Start with technology research approach:
|
|||
### 2. Web Search for Emerging Technologies
|
||||
|
||||
Search for current technology information:
|
||||
`WebSearch: "{{research_topic}} emerging technologies innovations {{current_year}}"`
|
||||
Search the web: "{{research_topic}} emerging technologies innovations"
|
||||
|
||||
**Technology focus:**
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Search for current technology information:
|
|||
### 3. Web Search for Digital Transformation
|
||||
|
||||
Search for current transformation trends:
|
||||
`WebSearch: "{{research_topic}} digital transformation {{current_year}}"`
|
||||
Search the web: "{{research_topic}} digital transformation trends"
|
||||
|
||||
**Transformation focus:**
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ Search for current transformation trends:
|
|||
### 4. Web Search for Future Outlook
|
||||
|
||||
Search for future projections:
|
||||
`WebSearch: "{{research_topic}} future outlook {{current_year}} 2025"`
|
||||
Search the web: "{{research_topic}} future outlook trends"
|
||||
|
||||
**Future focus:**
|
||||
|
||||
|
|
@ -102,32 +102,32 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Emerging Technologies
|
||||
|
||||
[Emerging technologies analysis with source citations]
|
||||
_Source: [URL with {{current_year}} technology data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Digital Transformation
|
||||
|
||||
[Digital transformation analysis with source citations]
|
||||
_Source: [URL with {{current_year}} transformation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Innovation Patterns
|
||||
|
||||
[Innovation patterns analysis with source citations]
|
||||
_Source: [URL with {{current_year}} innovation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Future Outlook
|
||||
|
||||
[Future outlook and projections with source citations]
|
||||
_Source: [URL with {{current_year}} outlook data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Opportunities
|
||||
|
||||
[Implementation opportunity analysis with source citations]
|
||||
_Source: [URL with {{current_year}} implementation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Challenges and Risks
|
||||
|
||||
[Challenges and risks assessment with source citations]
|
||||
_Source: [URL with {{current_year}} risk data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## Recommendations
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ _Source: [URL with {{current_year}} risk data]_
|
|||
### 6. Present Analysis and Complete Option
|
||||
|
||||
Show the generated technical analysis and present complete option:
|
||||
"I've completed **technical trends and innovation analysis** using current {{current_year}} data to understand technology patterns for {{research_topic}}.
|
||||
"I've completed **technical trends and innovation analysis** for {{research_topic}}.
|
||||
|
||||
**Technical Highlights:**
|
||||
|
||||
|
|
@ -181,7 +181,7 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Emerging technologies identified with current {{current_year}} data
|
||||
✅ Emerging technologies identified with current data
|
||||
✅ Digital transformation trends clearly documented
|
||||
✅ Future outlook and projections analyzed
|
||||
✅ Implementation opportunities and challenges mapped
|
||||
|
|
@ -193,7 +193,7 @@ Content is already written to document when generated in step 5. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in technology web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Missing critical emerging technologies in the domain
|
||||
❌ Not providing practical implementation recommendations
|
||||
❌ Not completing strategic recommendations
|
||||
|
|
@ -230,4 +230,4 @@ Research workflow complete. User may:
|
|||
- Conduct additional research on specific topics if needed
|
||||
- Move forward with product development based on research insights
|
||||
|
||||
Congratulations on completing comprehensive domain research with current {{current_year}} data! 🎉
|
||||
Congratulations on completing comprehensive domain research! 🎉
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current domain data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A DOMAIN RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on comprehensive synthesis and authoritative conclusions
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -72,7 +72,7 @@ Produce a comprehensive, authoritative research document on **{{research_topic}}
|
|||
- Set professional, authoritative tone
|
||||
|
||||
**Web Search for Introduction Context:**
|
||||
`WebSearch: "{{research_topic}} significance importance {{current_year}}"`
|
||||
Search the web: "{{research_topic}} significance importance"
|
||||
|
||||
### 3. Synthesize All Research Sections
|
||||
|
||||
|
|
@ -93,7 +93,7 @@ Produce a comprehensive, authoritative research document on **{{research_topic}}
|
|||
|
||||
## Executive Summary
|
||||
|
||||
[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive {{current_year}} research]
|
||||
[2-3 paragraph compelling summary of the most critical findings and strategic implications for {{research_topic}} based on comprehensive current research]
|
||||
|
||||
**Key Findings:**
|
||||
|
||||
|
|
@ -123,9 +123,9 @@ Produce a comprehensive, authoritative research document on **{{research_topic}}
|
|||
|
||||
### Research Significance
|
||||
|
||||
[Compelling narrative about why {{research_topic}} research is critical in {{current_year}}]
|
||||
_Why this research matters now: [Strategic importance with {{current_year}} context]_
|
||||
_Source: [URL with {{current_year}} industry significance data]_
|
||||
[Compelling narrative about why {{research_topic}} research is critical right now]
|
||||
_Why this research matters now: [Strategic importance with current context]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Research Methodology
|
||||
|
||||
|
|
@ -134,7 +134,7 @@ _Source: [URL with {{current_year}} industry significance data]_
|
|||
- **Research Scope**: [Comprehensive coverage areas]
|
||||
- **Data Sources**: [Authoritative sources and verification approach]
|
||||
- **Analysis Framework**: [Structured analysis methodology]
|
||||
- **Time Period**: [{{current_year}} focus and historical context]
|
||||
- **Time Period**: [current focus and historical context]
|
||||
- **Geographic Coverage**: [Regional/global scope]
|
||||
|
||||
### Research Goals and Objectives
|
||||
|
|
@ -151,11 +151,11 @@ _Source: [URL with {{current_year}} industry significance data]_
|
|||
|
||||
### Market Size and Growth Projections
|
||||
|
||||
[Comprehensive market analysis synthesized from step-02 with {{current_year}} data]
|
||||
[Comprehensive market analysis synthesized from step-02 with current data]
|
||||
_Market Size: [Current market valuation]_
|
||||
_Growth Rate: [CAGR and projections]_
|
||||
_Market Drivers: [Key growth factors]_
|
||||
_Source: [URL with {{current_year}} market data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Industry Structure and Value Chain
|
||||
|
||||
|
|
@ -163,17 +163,17 @@ _Source: [URL with {{current_year}} market data]_
|
|||
_Value Chain Components: [Detailed breakdown]_
|
||||
_Industry Segments: [Market segmentation analysis]_
|
||||
_Economic Impact: [Industry economic significance]_
|
||||
_Source: [URL with {{current_year}} industry structure data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Technology Landscape and Innovation Trends
|
||||
|
||||
### Current Technology Adoption
|
||||
|
||||
[Technology trends analysis from step-04 with {{current_year}} context]
|
||||
[Technology trends analysis from step-04 with current context]
|
||||
_Emerging Technologies: [Key technologies affecting {{research_topic}}]_
|
||||
_Adoption Patterns: [Technology adoption rates and patterns]_
|
||||
_Innovation Drivers: [Factors driving technology change]_
|
||||
_Source: [URL with {{current_year}} technology data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Digital Transformation Impact
|
||||
|
||||
|
|
@ -181,17 +181,17 @@ _Source: [URL with {{current_year}} technology data]_
|
|||
_Transformation Trends: [Major digital transformation patterns]_
|
||||
_Disruption Opportunities: [Technology-driven opportunities]_
|
||||
_Future Technology Outlook: [Emerging technologies and timelines]_
|
||||
_Source: [URL with {{current_year}} digital transformation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Regulatory Framework and Compliance Requirements
|
||||
|
||||
### Current Regulatory Landscape
|
||||
|
||||
[Regulatory analysis from step-03 with {{current_year}} updates]
|
||||
[Regulatory analysis from step-03 with current updates]
|
||||
_Key Regulations: [Critical regulatory requirements]_
|
||||
_Compliance Standards: [Industry standards and best practices]_
|
||||
_Recent Changes: [{{current_year}} regulatory updates and implications]_
|
||||
_Source: [URL with {{current_year}} regulatory data]_
|
||||
_Recent Changes: [current regulatory updates and implications]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk and Compliance Considerations
|
||||
|
||||
|
|
@ -199,17 +199,17 @@ _Source: [URL with {{current_year}} regulatory data]_
|
|||
_Compliance Risks: [Major regulatory and compliance risks]_
|
||||
_Risk Mitigation Strategies: [Approaches to manage regulatory risks]_
|
||||
_Future Regulatory Trends: [Anticipated regulatory developments]_
|
||||
_Source: [URL with {{current_year}} compliance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Competitive Landscape and Ecosystem Analysis
|
||||
|
||||
### Market Positioning and Key Players
|
||||
|
||||
[Competitive analysis with {{current_year}} market positioning]
|
||||
[Competitive analysis with current market positioning]
|
||||
_Market Leaders: [Dominant players and strategies]_
|
||||
_Emerging Competitors: [New entrants and innovative approaches]_
|
||||
_Competitive Dynamics: [Market competition patterns and trends]_
|
||||
_Source: [URL with {{current_year}} competitive data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Ecosystem and Partnership Landscape
|
||||
|
||||
|
|
@ -217,7 +217,7 @@ _Source: [URL with {{current_year}} competitive data]_
|
|||
_Ecosystem Players: [Key stakeholders and relationships]_
|
||||
_Partnership Opportunities: [Strategic collaboration potential]_
|
||||
_Supply Chain Dynamics: [Supply chain structure and risks]_
|
||||
_Source: [URL with {{current_year}} ecosystem data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Strategic Insights and Domain Opportunities
|
||||
|
||||
|
|
@ -227,7 +227,7 @@ _Source: [URL with {{current_year}} ecosystem data]_
|
|||
_Market-Technology Convergence: [How technology and market forces interact]_
|
||||
_Regulatory-Strategic Alignment: [How regulatory environment shapes strategy]_
|
||||
_Competitive Positioning Opportunities: [Strategic advantages based on research]_
|
||||
_Source: [URL with {{current_year}} strategic analysis data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Opportunities
|
||||
|
||||
|
|
@ -235,7 +235,7 @@ _Source: [URL with {{current_year}} strategic analysis data]_
|
|||
_Market Opportunities: [Specific market entry or expansion opportunities]_
|
||||
_Technology Opportunities: [Technology adoption or innovation opportunities]_
|
||||
_Partnership Opportunities: [Strategic collaboration and partnership potential]_
|
||||
_Source: [URL with {{current_year}} opportunity data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Implementation Considerations and Risk Assessment
|
||||
|
||||
|
|
@ -245,7 +245,7 @@ _Source: [URL with {{current_year}} opportunity data]_
|
|||
_Implementation Timeline: [Recommended phased approach]_
|
||||
_Resource Requirements: [Key resources and capabilities needed]_
|
||||
_Success Factors: [Critical success factors for implementation]_
|
||||
_Source: [URL with {{current_year}} implementation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Management and Mitigation
|
||||
|
||||
|
|
@ -253,7 +253,7 @@ _Source: [URL with {{current_year}} implementation data]_
|
|||
_Implementation Risks: [Major risks and mitigation approaches]_
|
||||
_Market Risks: [Market-related risks and contingency plans]_
|
||||
_Technology Risks: [Technology adoption and implementation risks]_
|
||||
_Source: [URL with {{current_year}} risk management data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Future Outlook and Strategic Planning
|
||||
|
||||
|
|
@ -263,7 +263,7 @@ _Source: [URL with {{current_year}} risk management data]_
|
|||
_Near-term Outlook: [1-2 year projections and implications]_
|
||||
_Medium-term Trends: [3-5 year expected developments]_
|
||||
_Long-term Vision: [5+ year strategic outlook for {{research_topic}}]_
|
||||
_Source: [URL with {{current_year}} future outlook data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
|
|
@ -271,7 +271,7 @@ _Source: [URL with {{current_year}} future outlook data]_
|
|||
_Immediate Actions: [Priority actions for next 6 months]_
|
||||
_Strategic Initiatives: [Key strategic initiatives for 1-2 years]_
|
||||
_Long-term Strategy: [Strategic positioning for 3+ years]_
|
||||
_Source: [URL with {{current_year}} strategic planning data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Research Methodology and Source Verification
|
||||
|
||||
|
|
@ -281,7 +281,6 @@ _Source: [URL with {{current_year}} strategic planning data]_
|
|||
_Primary Sources: [Key authoritative sources used]_
|
||||
_Secondary Sources: [Supporting research and analysis]_
|
||||
_Web Search Queries: [Complete list of search queries used]_
|
||||
_Data Currency: [All data verified for {{current_year}} currency]_
|
||||
|
||||
### Research Quality Assurance
|
||||
|
||||
|
|
@ -327,9 +326,9 @@ _Professional Networks: [Industry communities and knowledge sources]_
|
|||
---
|
||||
|
||||
**Research Completion Date:** {{date}}
|
||||
**Research Period:** {{current_year}} comprehensive analysis
|
||||
**Research Period:** Comprehensive analysis
|
||||
**Document Length:** As needed for comprehensive coverage
|
||||
**Source Verification:** All facts cited with {{current_year}} sources
|
||||
**Source Verification:** All facts cited with sources
|
||||
**Confidence Level:** High - based on multiple authoritative sources
|
||||
|
||||
_This comprehensive research document serves as an authoritative reference on {{research_topic}} and provides strategic insights for informed decision-making._
|
||||
|
|
@ -348,7 +347,7 @@ _This comprehensive research document serves as an authoritative reference on {{
|
|||
- **Exhaustive Research Coverage**: All aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Summary**: Key findings and strategic implications highlighted
|
||||
- **Strategic Recommendations**: Actionable insights based on comprehensive research
|
||||
- **Complete Source Citations**: Every factual claim verified with {{current_year}} sources
|
||||
- **Complete Source Citations**: Every factual claim verified with sources
|
||||
|
||||
**Research Completeness:**
|
||||
|
||||
|
|
@ -364,7 +363,7 @@ _This comprehensive research document serves as an authoritative reference on {{
|
|||
- Professional structure and compelling narrative
|
||||
- As long as needed for comprehensive coverage
|
||||
- Multiple independent sources for all claims
|
||||
- {{current_year}} data throughout with proper citations
|
||||
- Proper citations throughout
|
||||
|
||||
**Ready to complete this comprehensive research document?**
|
||||
[C] Complete Research - Save final comprehensive document
|
||||
|
|
@ -389,7 +388,7 @@ When user selects 'C', append the complete comprehensive research document using
|
|||
✅ Exhaustive research coverage across all domain aspects
|
||||
✅ Executive summary with key findings and strategic implications
|
||||
✅ Strategic recommendations grounded in comprehensive research
|
||||
✅ Complete source verification with {{current_year}} citations
|
||||
✅ Complete source verification with citations
|
||||
✅ Professional document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Domain research workflow completed with comprehensive document
|
||||
|
|
@ -401,7 +400,7 @@ When user selects 'C', append the complete comprehensive research document using
|
|||
❌ Incomplete research coverage across domain aspects
|
||||
❌ Not providing executive summary with key findings
|
||||
❌ Missing strategic recommendations based on research
|
||||
❌ Not using {{current_year}} sources for all factual claims
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing document without professional structure
|
||||
❌ Not presenting completion option for final document
|
||||
|
||||
|
|
@ -438,6 +437,6 @@ Complete authoritative research document on {{research_topic}} that:
|
|||
- Establishes professional credibility through comprehensive research
|
||||
- Provides strategic insights for informed decision-making
|
||||
- Serves as reference document for continued use
|
||||
- Maintains highest research quality standards with {{current_year}} verification
|
||||
- Maintains highest research quality standards
|
||||
|
||||
Congratulations on completing comprehensive domain research with professional documentation! 🎉
|
||||
Congratulations on completing comprehensive domain research! 🎉
|
||||
|
|
|
|||
|
|
@ -44,8 +44,8 @@ Start with research confirmation:
|
|||
|
||||
- **Research Topic**: {{research_topic}}
|
||||
- **Research Goals**: {{research_goals}}
|
||||
- **Research Type**: Market Research using current {{current_year}} data
|
||||
- **Approach**: Comprehensive market analysis with rigorous source verification
|
||||
- **Research Type**: Market Research
|
||||
- **Approach**: Comprehensive market analysis with source verification
|
||||
|
||||
**Market Research Areas We'll Cover:**
|
||||
|
||||
|
|
@ -83,7 +83,6 @@ Write initial research scope to document:
|
|||
**Topic**: {{research_topic}}
|
||||
**Goals**: {{research_goals}}
|
||||
**Research Type**: Market Research
|
||||
**Data Currency**: {{current_year}} with rigorous source verification
|
||||
**Date**: {{date}}
|
||||
|
||||
### Research Scope
|
||||
|
|
@ -97,7 +96,7 @@ Write initial research scope to document:
|
|||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current {{current_year}} web data with source verification
|
||||
- Current web data with source verification
|
||||
- Multiple independent sources for critical claims
|
||||
- Confidence level assessment for uncertain data
|
||||
- Comprehensive coverage with no critical gaps
|
||||
|
|
@ -123,7 +122,7 @@ Show initial scope document and present continue option:
|
|||
|
||||
- Research topic and goals confirmed
|
||||
- Market analysis focus areas defined
|
||||
- Research methodology with {{current_year}} data verification
|
||||
- Research methodology verification
|
||||
- Clear workflow progression
|
||||
|
||||
**Document Status:** Initial scope written to research file for your review
|
||||
|
|
@ -177,6 +176,6 @@ This step ensures:
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user confirmation and scope finalization, load `./step-02-customer-insights.md` to begin detailed market research with customer insights analysis using {{current_year}} data and rigorous source verification.
|
||||
After user confirmation and scope finalization, load `./step-02-customer-insights.md` to begin detailed market research with customer insights analysis.
|
||||
|
||||
Remember: Init steps confirm understanding and scope, not generate research content!
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without web search verification
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current customer data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER BEHAVIOR ANALYST, not content generator
|
||||
- 💬 FOCUS on customer behavior patterns and demographic analysis
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete research
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer behavior and segment analysis using current {{current_year}} web data with emphasis on patterns and demographics.
|
||||
Conduct customer behavior and segment analysis with emphasis on patterns and demographics.
|
||||
|
||||
## CUSTOMER BEHAVIOR ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Conduct customer behavior and segment analysis using current {{current_year}} we
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer behavior areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer behavior research approach:
|
||||
"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer patterns.
|
||||
"Now I'll conduct **customer behavior analysis** for **{{research_topic}}** to understand customer patterns.
|
||||
|
||||
**Customer Behavior Focus:**
|
||||
|
||||
|
|
@ -56,10 +56,10 @@ Start with customer behavior research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} customer behavior patterns {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} customer demographics {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} psychographic profiles {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} customer behavior drivers {{current_year}}"`
|
||||
Search the web: "{{research_topic}} customer behavior patterns"
|
||||
Search the web: "{{research_topic}} customer demographics"
|
||||
Search the web: "{{research_topic}} psychographic profiles"
|
||||
Search the web: "{{research_topic}} customer behavior drivers"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
_Behavior Drivers: [Key motivations and patterns from web search]_
|
||||
_Interaction Preferences: [Customer engagement and interaction patterns]_
|
||||
_Decision Habits: [How customers typically make decisions]_
|
||||
_Source: [URL with {{current_year}} customer behavior data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Demographic Segmentation
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _Age Demographics: [Age groups and preferences]_
|
|||
_Income Levels: [Income segments and purchasing behavior]_
|
||||
_Geographic Distribution: [Regional/city differences]_
|
||||
_Education Levels: [Education impact on behavior]_
|
||||
_Source: [URL with {{current_year}} demographic data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Psychographic Profiles
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ _Values and Beliefs: [Core values driving customer behavior]_
|
|||
_Lifestyle Preferences: [Lifestyle choices and behaviors]_
|
||||
_Attitudes and Opinions: [Customer attitudes toward products/services]_
|
||||
_Personality Traits: [Personality influences on behavior]_
|
||||
_Source: [URL with {{current_year}} psychographic data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Segment Profiles
|
||||
|
||||
|
|
@ -134,7 +134,7 @@ _Source: [URL with {{current_year}} psychographic data]_
|
|||
_Segment 1: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Segment 2: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Segment 3: [Detailed profile including demographics, psychographics, behavior]_
|
||||
_Source: [URL with {{current_year}} segment data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Behavior Drivers and Influences
|
||||
|
||||
|
|
@ -143,7 +143,7 @@ _Emotional Drivers: [Emotional factors influencing behavior]_
|
|||
_Rational Drivers: [Logical decision factors]_
|
||||
_Social Influences: [Social and peer influences]_
|
||||
_Economic Influences: [Economic factors affecting behavior]_
|
||||
_Source: [URL with {{current_year}} behavior drivers data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Interaction Patterns
|
||||
|
||||
|
|
@ -152,14 +152,14 @@ _Research and Discovery: [How customers find and research options]_
|
|||
_Purchase Decision Process: [Steps in purchase decision making]_
|
||||
_Post-Purchase Behavior: [After-purchase engagement patterns]_
|
||||
_Loyalty and Retention: [Factors driving customer loyalty]_
|
||||
_Source: [URL with {{current_year}} interaction data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer behavior analysis** using current {{current_year}} data to understand customer patterns for {{research_topic}}.
|
||||
"I've completed **customer behavior analysis** for {{research_topic}}, focusing on customer patterns.
|
||||
|
||||
**Key Customer Behavior Findings:**
|
||||
|
||||
|
|
@ -186,7 +186,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer behavior patterns identified with current {{current_year}} citations
|
||||
✅ Customer behavior patterns identified with current citations
|
||||
✅ Demographic segmentation thoroughly analyzed
|
||||
✅ Psychographic profiles clearly documented
|
||||
✅ Customer interaction patterns captured
|
||||
|
|
@ -198,7 +198,8 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in customer web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer behavior patterns
|
||||
❌ Incomplete demographic segmentation analysis
|
||||
❌ Missing psychographic profile documentation
|
||||
|
|
@ -215,7 +216,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use demographic data from authoritative sources
|
||||
- Research psychographic profiling and value systems
|
||||
- Analyze customer interaction and engagement patterns
|
||||
- Focus on current {{current_year}} behavior data and trends
|
||||
- Focus on current behavior data and trends
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -232,4 +233,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-03-customer-pain-points.md` to analyze customer pain points, challenges, and unmet needs for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} customer data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and emphasize current customer data with rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current customer data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER INSIGHTS ANALYST, not content generator
|
||||
- 💬 FOCUS on customer behavior and needs analysis
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
|
|
@ -28,7 +28,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive customer insights analysis using current {{current_year}} web data with emphasis on behavior patterns and needs.
|
||||
Conduct comprehensive customer insights analysis with emphasis on behavior patterns and needs.
|
||||
|
||||
## CUSTOMER INSIGHTS SEQUENCE:
|
||||
|
||||
|
|
@ -37,7 +37,7 @@ Conduct comprehensive customer insights analysis using current {{current_year}}
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer areas simultaneously and thoroughly
|
||||
|
||||
Start with customer research approach:
|
||||
"Now I'll conduct **customer insights analysis** using current {{current_year}} web data to understand customer behavior and needs.
|
||||
"Now I'll conduct **customer insights analysis** to understand customer behavior and needs.
|
||||
|
||||
**Customer Insights Focus:**
|
||||
|
||||
|
|
@ -54,9 +54,9 @@ Start with customer research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "[product/service/market] customer behavior patterns {{current_year}}"`
|
||||
`WebSearch: "[product/service/market] customer pain points challenges {{current_year}}"`
|
||||
`WebSearch: "[product/service/market] customer decision process {{current_year}}"`
|
||||
Search the web: "[product/service/market] customer behavior patterns"
|
||||
Search the web: "[product/service/market] customer pain points challenges"
|
||||
Search the web: "[product/service/market] customer decision process"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -99,43 +99,43 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Customer Behavior Patterns
|
||||
|
||||
[Customer behavior analysis with source citations]
|
||||
_Source: [URL with {{current_year}} customer data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Pain Points and Challenges
|
||||
|
||||
[Pain points analysis with source citations]
|
||||
_Source: [URL with {{current_year}} customer challenges data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision-Making Processes
|
||||
|
||||
[Decision-making analysis with source citations]
|
||||
_Source: [URL with {{current_year}} decision process data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Journey Mapping
|
||||
|
||||
[Customer journey analysis with source citations]
|
||||
_Source: [URL with {{current_year}} customer journey data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Satisfaction Drivers
|
||||
|
||||
[Satisfaction drivers analysis with source citations]
|
||||
_Source: [URL with {{current_year}} satisfaction data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Demographic Profiles
|
||||
|
||||
[Demographic profiles analysis with source citations]
|
||||
_Source: [URL with {{current_year}} demographic data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Psychographic Profiles
|
||||
|
||||
[Psychographic profiles analysis with source citations]
|
||||
_Source: [URL with {{current_year}} psychographic data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
Show the generated customer insights and present continue option:
|
||||
"I've completed the **customer insights analysis** using current {{current_year}} data to understand customer behavior and needs.
|
||||
"I've completed the **customer insights analysis** for customer behavior and needs.
|
||||
|
||||
**Key Customer Findings:**
|
||||
|
||||
|
|
@ -154,7 +154,7 @@ Show the generated customer insights and present continue option:
|
|||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load: `./step-03-competitive-analysis.md`
|
||||
- Load: `./step-05-competitive-analysis.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -162,7 +162,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Customer behavior patterns identified with current {{current_year}} citations
|
||||
✅ Customer behavior patterns identified with current citations
|
||||
✅ Pain points and challenges clearly documented
|
||||
✅ Decision-making processes thoroughly analyzed
|
||||
✅ Customer journey insights captured and mapped
|
||||
|
|
@ -172,7 +172,8 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in customer web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer behavior patterns
|
||||
❌ Not identifying key pain points and challenges
|
||||
❌ Incomplete customer journey mapping
|
||||
|
|
@ -193,6 +194,6 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-03-competitive-analysis.md` to focus on competitive landscape analysis.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-competitive-analysis.md` to focus on competitive landscape analysis.
|
||||
|
||||
Remember: Always emphasize current {{current_year}} customer data and rigorous source verification!
|
||||
Remember: Always emphasize current customer data and rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current customer data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER NEEDS ANALYST, not content generator
|
||||
- 💬 FOCUS on customer pain points, challenges, and unmet needs
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer pain points and needs analysis using current {{current_year}} web data with emphasis on challenges and frustrations.
|
||||
Conduct customer pain points and needs analysis with emphasis on challenges and frustrations.
|
||||
|
||||
## CUSTOMER PAIN POINTS ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ Conduct customer pain points and needs analysis using current {{current_year}} w
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer pain point areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer pain points research approach:
|
||||
"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer challenges.
|
||||
"Now I'll conduct **customer pain points analysis** for **{{research_topic}}** to understand customer challenges.
|
||||
|
||||
**Customer Pain Points Focus:**
|
||||
|
||||
|
|
@ -57,10 +57,10 @@ Start with customer pain points research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} customer pain points challenges {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} customer frustrations {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} unmet customer needs {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} customer barriers to adoption {{current_year}}"`
|
||||
Search the web: "{{research_topic}} customer pain points challenges"
|
||||
Search the web: "{{research_topic}} customer frustrations"
|
||||
Search the web: "{{research_topic}} unmet customer needs"
|
||||
Search the web: "{{research_topic}} customer barriers to adoption"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -109,7 +109,7 @@ _Primary Frustrations: [Major customer frustrations identified]_
|
|||
_Usage Barriers: [Barriers preventing effective usage]_
|
||||
_Service Pain Points: [Customer service and support issues]_
|
||||
_Frequency Analysis: [How often these challenges occur]_
|
||||
_Source: [URL with {{current_year}} customer challenges data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Unmet Customer Needs
|
||||
|
||||
|
|
@ -118,7 +118,7 @@ _Critical Unmet Needs: [Most important unaddressed needs]_
|
|||
_Solution Gaps: [Opportunities to address unmet needs]_
|
||||
_Market Gaps: [Market opportunities from unmet needs]_
|
||||
_Priority Analysis: [Which needs are most critical]_
|
||||
_Source: [URL with {{current_year}} unmet needs data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Barriers to Adoption
|
||||
|
||||
|
|
@ -127,7 +127,7 @@ _Price Barriers: [Cost-related barriers to adoption]_
|
|||
_Technical Barriers: [Complexity or technical barriers]_
|
||||
_Trust Barriers: [Trust and credibility issues]_
|
||||
_Convenience Barriers: [Ease of use or accessibility issues]_
|
||||
_Source: [URL with {{current_year}} adoption barriers data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Service and Support Pain Points
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ _Customer Service Issues: [Common customer service problems]_
|
|||
_Support Gaps: [Areas where customer support is lacking]_
|
||||
_Communication Issues: [Communication breakdowns and frustrations]_
|
||||
_Response Time Issues: [Slow response and resolution problems]_
|
||||
_Source: [URL with {{current_year}} service pain points data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Satisfaction Gaps
|
||||
|
||||
|
|
@ -145,7 +145,7 @@ _Expectation Gaps: [Differences between expectations and reality]_
|
|||
_Quality Gaps: [Areas where quality expectations aren't met]_
|
||||
_Value Perception Gaps: [Perceived value vs actual value]_
|
||||
_Trust and Credibility Gaps: [Trust issues affecting satisfaction]_
|
||||
_Source: [URL with {{current_year}} satisfaction gap data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Emotional Impact Assessment
|
||||
|
||||
|
|
@ -154,7 +154,7 @@ _Frustration Levels: [Customer frustration severity assessment]_
|
|||
_Loyalty Risks: [How pain points affect customer loyalty]_
|
||||
_Reputation Impact: [Impact on brand or product reputation]_
|
||||
_Customer Retention Risks: [Risk of customer loss from pain points]_
|
||||
_Source: [URL with {{current_year}} emotional impact data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Pain Point Prioritization
|
||||
|
||||
|
|
@ -163,14 +163,14 @@ _High Priority Pain Points: [Most critical pain points to address]_
|
|||
_Medium Priority Pain Points: [Important but less critical pain points]_
|
||||
_Low Priority Pain Points: [Minor pain points with lower impact]_
|
||||
_Opportunity Mapping: [Pain points with highest solution opportunity]_
|
||||
_Source: [URL with {{current_year}} prioritization data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer pain points analysis** using current {{current_year}} data to understand customer challenges for {{research_topic}}.
|
||||
"I've completed **customer pain points analysis** for {{research_topic}}, focusing on customer challenges.
|
||||
|
||||
**Key Pain Points Findings:**
|
||||
|
||||
|
|
@ -209,7 +209,8 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in customer web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical customer challenges or frustrations
|
||||
❌ Not identifying unmet needs or solution gaps
|
||||
❌ Incomplete adoption barriers analysis
|
||||
|
|
@ -227,7 +228,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use customer feedback and complaint data
|
||||
- Analyze customer support and service issues
|
||||
- Study barriers to customer adoption
|
||||
- Focus on current {{current_year}} pain point data
|
||||
- Focus on current pain point data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -244,4 +245,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-04-customer-decisions.md` to analyze customer decision processes, journey mapping, and decision factors for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} customer pain points data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and emphasize current customer pain points data with rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current customer data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A CUSTOMER DECISION ANALYST, not content generator
|
||||
- 💬 FOCUS on customer decision processes and journey mapping
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -32,7 +32,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct customer decision processes and journey analysis using current {{current_year}} web data with emphasis on decision factors and journey mapping.
|
||||
Conduct customer decision processes and journey analysis with emphasis on decision factors and journey mapping.
|
||||
|
||||
## CUSTOMER DECISIONS ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ Conduct customer decision processes and journey analysis using current {{current
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different customer decision areas simultaneously and thoroughly.
|
||||
|
||||
Start with customer decisions research approach:
|
||||
"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** using current {{current_year}} web data to understand customer decision-making.
|
||||
"Now I'll conduct **customer decision processes analysis** for **{{research_topic}}** to understand customer decision-making.
|
||||
|
||||
**Customer Decisions Focus:**
|
||||
|
||||
|
|
@ -57,10 +57,10 @@ Start with customer decisions research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} customer decision process {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} buying criteria factors {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} customer journey mapping {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} decision influencing factors {{current_year}}"`
|
||||
Search the web: "{{research_topic}} customer decision process"
|
||||
Search the web: "{{research_topic}} buying criteria factors"
|
||||
Search the web: "{{research_topic}} customer journey mapping"
|
||||
Search the web: "{{research_topic}} decision influencing factors"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -109,7 +109,7 @@ _Decision Stages: [Key stages in customer decision making]_
|
|||
_Decision Timelines: [Timeframes for different decisions]_
|
||||
_Complexity Levels: [Decision complexity assessment]_
|
||||
_Evaluation Methods: [How customers evaluate options]_
|
||||
_Source: [URL with {{current_year}} decision process data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision Factors and Criteria
|
||||
|
||||
|
|
@ -118,7 +118,7 @@ _Primary Decision Factors: [Most important factors in decisions]_
|
|||
_Secondary Decision Factors: [Supporting factors influencing decisions]_
|
||||
_Weighing Analysis: [How different factors are weighed]_
|
||||
_Evoluton Patterns: [How factors change over time]_
|
||||
_Source: [URL with {{current_year}} decision factors data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Journey Mapping
|
||||
|
||||
|
|
@ -128,7 +128,7 @@ _Consideration Stage: [Evaluation and comparison process]_
|
|||
_Decision Stage: [Final decision-making process]_
|
||||
_Purchase Stage: [Purchase execution and completion]_
|
||||
_Post-Purchase Stage: [Post-decision evaluation and behavior]_
|
||||
_Source: [URL with {{current_year}} journey mapping data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Touchpoint Analysis
|
||||
|
||||
|
|
@ -137,7 +137,7 @@ _Digital Touchpoints: [Online and digital interaction points]_
|
|||
_Offline Touchpoints: [Physical and in-person interaction points]_
|
||||
_Information Sources: [Where customers get information]_
|
||||
_Influence Channels: [What influences customer decisions]_
|
||||
_Source: [URL with {{current_year}} touchpoint data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Information Gathering Patterns
|
||||
|
||||
|
|
@ -146,7 +146,7 @@ _Research Methods: [How customers research options]_
|
|||
_Information Sources Trusted: [Most trusted information sources]_
|
||||
_Research Duration: [Time spent gathering information]_
|
||||
_Evaluation Criteria: [How customers evaluate information]_
|
||||
_Source: [URL with {{current_year}} information gathering data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Decision Influencers
|
||||
|
||||
|
|
@ -155,7 +155,7 @@ _Peer Influence: [How friends and family influence decisions]_
|
|||
_Expert Influence: [How expert opinions affect decisions]_
|
||||
_Media Influence: [How media and marketing affect decisions]_
|
||||
_Social Proof Influence: [How reviews and testimonials affect decisions]_
|
||||
_Source: [URL with {{current_year}} decision influencer data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Purchase Decision Factors
|
||||
|
||||
|
|
@ -164,7 +164,7 @@ _Immediate Purchase Drivers: [Factors triggering immediate purchase]_
|
|||
_Delayed Purchase Drivers: [Factors causing purchase delays]_
|
||||
_Brand Loyalty Factors: [Factors driving repeat purchases]_
|
||||
_Price Sensitivity: [How price affects purchase decisions]_
|
||||
_Source: [URL with {{current_year}} purchase decision data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Decision Optimizations
|
||||
|
||||
|
|
@ -173,14 +173,14 @@ _Friction Reduction: [Ways to make decisions easier]_
|
|||
_Trust Building: [Building customer trust in decisions]_
|
||||
_Conversion Optimization: [Optimizing decision-to-purchase rates]_
|
||||
_Loyalty Building: [Building long-term customer relationships]_
|
||||
_Source: [URL with {{current_year}} decision optimization data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **customer decision processes analysis** using current {{current_year}} data to understand customer decision-making for {{research_topic}}.
|
||||
"I've completed **customer decision processes analysis** for {{research_topic}}, focusing on customer decision-making.
|
||||
|
||||
**Key Decision Findings:**
|
||||
|
||||
|
|
@ -219,7 +219,8 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in customer web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical decision-making process stages
|
||||
❌ Not identifying key decision factors
|
||||
❌ Incomplete customer journey mapping
|
||||
|
|
@ -237,7 +238,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use customer journey mapping methodologies
|
||||
- Analyze buying criteria and decision factors
|
||||
- Study decision influence and touchpoint analysis
|
||||
- Focus on current {{current_year}} decision data
|
||||
- Focus on current decision data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -254,4 +255,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-05-competitive-analysis.md` to analyze competitive landscape, market positioning, and competitive strategies for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} customer decision data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and emphasize current customer decision data with rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current competitive data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A COMPETITIVE ANALYST, not content generator
|
||||
- 💬 FOCUS on competitive landscape and market positioning
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
|
|
@ -28,14 +28,14 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive competitive analysis using current {{current_year}} web data with emphasis on market positioning.
|
||||
Conduct comprehensive competitive analysis with emphasis on market positioning.
|
||||
|
||||
## COMPETITIVE ANALYSIS SEQUENCE:
|
||||
|
||||
### 1. Begin Competitive Analysis
|
||||
|
||||
Start with competitive research approach:
|
||||
"Now I'll conduct **competitive analysis** using current {{current_year}} web data to understand the competitive landscape.
|
||||
"Now I'll conduct **competitive analysis** to understand the competitive landscape.
|
||||
|
||||
**Competitive Analysis Focus:**
|
||||
|
||||
|
|
@ -61,43 +61,43 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Key Market Players
|
||||
|
||||
[Key players analysis with market share data]
|
||||
_Source: [URL with {{current_year}} market share data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Share Analysis
|
||||
|
||||
[Market share analysis with source citations]
|
||||
_Source: [URL with {{current_year}} market share data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Positioning
|
||||
|
||||
[Positioning analysis with source citations]
|
||||
_Source: [URL with {{current_year}} positioning data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strengths and Weaknesses
|
||||
|
||||
[SWOT analysis with source citations]
|
||||
_Source: [URL with {{current_year}} competitor analysis]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Differentiation
|
||||
|
||||
[Differentiation analysis with source citations]
|
||||
_Source: [URL with {{current_year}} differentiation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Threats
|
||||
|
||||
[Threats analysis with source citations]
|
||||
_Source: [URL with {{current_year}} threat assessment]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Opportunities
|
||||
|
||||
[Competitive opportunities analysis with source citations]
|
||||
_Source: [URL with {{current_year}} opportunity data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 3. Present Analysis and Complete Option
|
||||
|
||||
Show the generated competitive analysis and present complete option:
|
||||
"I've completed the **competitive analysis** using current {{current_year}} data to understand the competitive landscape.
|
||||
"I've completed the **competitive analysis** for the competitive landscape.
|
||||
|
||||
**Key Competitive Findings:**
|
||||
|
||||
|
|
@ -124,7 +124,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Key market players identified with {{current_year}} data
|
||||
✅ Key market players identified
|
||||
✅ Market share analysis completed with source verification
|
||||
✅ Competitive positioning strategies clearly mapped
|
||||
✅ Strengths and weaknesses thoroughly analyzed
|
||||
|
|
@ -135,7 +135,8 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in competitive web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing key market players or market share data
|
||||
❌ Incomplete competitive positioning analysis
|
||||
❌ Not identifying market differentiation opportunities
|
||||
|
|
@ -172,4 +173,4 @@ Market research workflow complete. User may:
|
|||
- Conduct additional competitive research on specific companies
|
||||
- Combine market research with other research types for comprehensive insights
|
||||
|
||||
Congratulations on completing comprehensive market research with current {{current_year}} data! 🎉
|
||||
Congratulations on completing comprehensive market research! 🎉
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current market data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A MARKET RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on strategic recommendations and actionable insights
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
|
|
@ -38,7 +38,7 @@ Produce a comprehensive, authoritative market research document on **{{research_
|
|||
### 1. Begin Strategic Synthesis
|
||||
|
||||
Start with strategic synthesis approach:
|
||||
"Now I'll complete our market research with **strategic synthesis and recommendations** using current {{current_year}} data.
|
||||
"Now I'll complete our market research with **strategic synthesis and recommendations** .
|
||||
|
||||
**Strategic Synthesis Focus:**
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Start with strategic synthesis approach:
|
|||
### 2. Web Search for Market Entry Strategies
|
||||
|
||||
Search for current market strategies:
|
||||
`WebSearch: "market entry strategies best practices {{current_year}}"`
|
||||
Search the web: "market entry strategies best practices"
|
||||
|
||||
**Strategy focus:**
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Search for current market strategies:
|
|||
### 3. Web Search for Risk Assessment
|
||||
|
||||
Search for current risk approaches:
|
||||
`WebSearch: "market research risk assessment frameworks {{current_year}}"`
|
||||
Search the web: "market research risk assessment frameworks"
|
||||
|
||||
**Risk focus:**
|
||||
|
||||
|
|
@ -105,10 +105,10 @@ Prepare comprehensive market research document with full structure:
|
|||
|
||||
### Market Research Significance
|
||||
|
||||
[Compelling market narrative about why {{research_topic}} research is critical in {{current_year}}]
|
||||
_Market Importance: [Strategic market significance with {{current_year}} context]_
|
||||
**Compelling market narrative about why {{research_topic}} research is critical now**
|
||||
_Market Importance: [Strategic market significance with up-to-date context]_
|
||||
_Business Impact: [Business implications of market research]_
|
||||
_Source: [URL with {{current_year}} market significance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Research Methodology
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _Source: [URL with {{current_year}} market significance data]_
|
|||
- **Market Scope**: [Comprehensive market coverage areas]
|
||||
- **Data Sources**: [Authoritative market sources and verification approach]
|
||||
- **Analysis Framework**: [Structured market analysis methodology]
|
||||
- **Time Period**: [{{current_year}} focus and market evolution context]
|
||||
- **Time Period**: [current focus and market evolution context]
|
||||
- **Geographic Coverage**: [Regional/global market scope]
|
||||
|
||||
### Market Research Goals and Objectives
|
||||
|
|
@ -134,12 +134,12 @@ _Source: [URL with {{current_year}} market significance data]_
|
|||
|
||||
### Market Size and Growth Projections
|
||||
|
||||
[Comprehensive market analysis with {{current_year}} data]
|
||||
_[Comprehensive market analysis]_
|
||||
_Market Size: [Current market valuation and size]_
|
||||
_Growth Rate: [CAGR and market growth projections]_
|
||||
_Market Drivers: [Key factors driving market growth]_
|
||||
_Market Segments: [Detailed market segmentation analysis]_
|
||||
_Source: [URL with {{current_year}} market size data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Trends and Dynamics
|
||||
|
||||
|
|
@ -147,7 +147,7 @@ _Source: [URL with {{current_year}} market size data]_
|
|||
_Emerging Trends: [Key market trends and their implications]_
|
||||
_Market Dynamics: [Forces shaping market evolution]_
|
||||
_Consumer Behavior Shifts: [Changes in customer behavior and preferences]_
|
||||
_Source: [URL with {{current_year}} market trends data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Pricing and Business Model Analysis
|
||||
|
||||
|
|
@ -155,17 +155,17 @@ _Source: [URL with {{current_year}} market trends data]_
|
|||
_Pricing Strategies: [Current pricing approaches and models]_
|
||||
_Business Model Evolution: [Emerging and successful business models]_
|
||||
_Value Proposition Analysis: [Customer value proposition assessment]_
|
||||
_Source: [URL with {{current_year}} pricing data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Customer Insights and Behavior Analysis
|
||||
|
||||
### Customer Behavior Patterns
|
||||
|
||||
[Customer insights analysis with {{current_year}} context]
|
||||
[Customer insights analysis with current context]
|
||||
_Behavior Patterns: [Key customer behavior trends and patterns]_
|
||||
_Customer Journey: [Complete customer journey mapping]_
|
||||
_Decision Factors: [Factors influencing customer decisions]_
|
||||
_Source: [URL with {{current_year}} customer behavior data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Pain Points and Needs
|
||||
|
||||
|
|
@ -173,7 +173,7 @@ _Source: [URL with {{current_year}} customer behavior data]_
|
|||
_Pain Points: [Key customer challenges and frustrations]_
|
||||
_Unmet Needs: [Unsolved customer needs and opportunities]_
|
||||
_Customer Expectations: [Current customer expectations and requirements]_
|
||||
_Source: [URL with {{current_year}} customer insights data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Customer Segmentation and Targeting
|
||||
|
||||
|
|
@ -181,7 +181,7 @@ _Source: [URL with {{current_year}} customer insights data]_
|
|||
_Customer Segments: [Detailed customer segment profiles]_
|
||||
_Target Market Analysis: [Most attractive customer segments]_
|
||||
_Segment-specific Strategies: [Tailored approaches for key segments]_
|
||||
_Source: [URL with {{current_year}} segmentation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Competitive Landscape and Positioning
|
||||
|
||||
|
|
@ -191,7 +191,7 @@ _Source: [URL with {{current_year}} segmentation data]_
|
|||
_Market Leaders: [Dominant competitors and their strategies]_
|
||||
_Emerging Competitors: [New entrants and innovative approaches]_
|
||||
_Competitive Advantages: [Key differentiators and competitive advantages]_
|
||||
_Source: [URL with {{current_year}} competitive data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Market Positioning Strategies
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ _Source: [URL with {{current_year}} competitive data]_
|
|||
_Positioning Opportunities: [Opportunities for market differentiation]_
|
||||
_Competitive Gaps: [Unserved market needs and opportunities]_
|
||||
_Positioning Framework: [Recommended positioning approach]_
|
||||
_Source: [URL with {{current_year}} positioning data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Strategic Market Recommendations
|
||||
|
||||
|
|
@ -209,7 +209,7 @@ _Source: [URL with {{current_year}} positioning data]_
|
|||
_High-Value Opportunities: [Most attractive market opportunities]_
|
||||
_Market Entry Timing: [Optimal timing for market entry or expansion]_
|
||||
_Growth Strategies: [Recommended approaches for market growth]_
|
||||
_Source: [URL with {{current_year}} market opportunity data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Recommendations
|
||||
|
||||
|
|
@ -217,7 +217,7 @@ _Source: [URL with {{current_year}} market opportunity data]_
|
|||
_Market Entry Strategy: [Recommended approach for market entry/expansion]_
|
||||
_Competitive Strategy: [Recommended competitive positioning and approach]_
|
||||
_Customer Acquisition Strategy: [Recommended customer acquisition approach]_
|
||||
_Source: [URL with {{current_year}} strategic data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Market Entry and Growth Strategies
|
||||
|
||||
|
|
@ -227,7 +227,7 @@ _Source: [URL with {{current_year}} strategic data]_
|
|||
_Market Entry Approach: [Recommended market entry strategy and tactics]_
|
||||
_Channel Strategy: [Optimal channels for market reach and customer acquisition]_
|
||||
_Partnership Strategy: [Strategic partnership and collaboration opportunities]_
|
||||
_Source: [URL with {{current_year}} market entry data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Growth and Scaling Strategy
|
||||
|
||||
|
|
@ -235,7 +235,7 @@ _Source: [URL with {{current_year}} market entry data]_
|
|||
_Growth Phases: [Recommended phased approach to market growth]_
|
||||
_Scaling Considerations: [Key factors for successful market scaling]_
|
||||
_Expansion Opportunities: [Opportunities for geographic or segment expansion]_
|
||||
_Source: [URL with {{current_year}} growth strategy data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Risk Assessment and Mitigation
|
||||
|
||||
|
|
@ -245,7 +245,7 @@ _Source: [URL with {{current_year}} growth strategy data]_
|
|||
_Market Risks: [Key market-related risks and uncertainties]_
|
||||
_Competitive Risks: [Competitive threats and mitigation strategies]_
|
||||
_Regulatory Risks: [Regulatory and compliance considerations]_
|
||||
_Source: [URL with {{current_year}} risk assessment data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Mitigation Strategies
|
||||
|
||||
|
|
@ -253,7 +253,7 @@ _Source: [URL with {{current_year}} risk assessment data]_
|
|||
_Risk Mitigation Approaches: [Strategies for managing identified risks]_
|
||||
_Contingency Planning: [Backup plans and alternative approaches]_
|
||||
_Market Sensitivity Analysis: [Impact of market changes on strategy]_
|
||||
_Source: [URL with {{current_year}} mitigation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Implementation Roadmap and Success Metrics
|
||||
|
||||
|
|
@ -263,7 +263,7 @@ _Source: [URL with {{current_year}} mitigation data]_
|
|||
_Implementation Timeline: [Recommended phased implementation approach]_
|
||||
_Required Resources: [Key resources and capabilities needed]_
|
||||
_Implementation Milestones: [Key milestones and success criteria]_
|
||||
_Source: [URL with {{current_year}} implementation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Success Metrics and KPIs
|
||||
|
||||
|
|
@ -271,7 +271,7 @@ _Source: [URL with {{current_year}} implementation data]_
|
|||
_Key Performance Indicators: [Critical metrics for measuring success]_
|
||||
_Monitoring and Reporting: [Approach for tracking and reporting progress]_
|
||||
_Success Criteria: [Clear criteria for determining success]_
|
||||
_Source: [URL with {{current_year}} metrics data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Future Market Outlook and Opportunities
|
||||
|
||||
|
|
@ -281,7 +281,7 @@ _Source: [URL with {{current_year}} metrics data]_
|
|||
_Near-term Market Evolution: [1-2 year market development expectations]_
|
||||
_Medium-term Market Trends: [3-5 year expected market developments]_
|
||||
_Long-term Market Vision: [5+ year market outlook for {{research_topic}}]_
|
||||
_Source: [URL with {{current_year}} future trends data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Strategic Opportunities
|
||||
|
||||
|
|
@ -289,7 +289,7 @@ _Source: [URL with {{current_year}} future trends data]_
|
|||
_Emerging Opportunities: [New market opportunities and their potential]_
|
||||
_Innovation Opportunities: [Areas for market innovation and differentiation]_
|
||||
_Strategic Market Investments: [Recommended market investments and priorities]_
|
||||
_Source: [URL with {{current_year}} opportunity data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 10. Market Research Methodology and Source Verification
|
||||
|
||||
|
|
@ -299,7 +299,6 @@ _Source: [URL with {{current_year}} opportunity data]_
|
|||
_Primary Market Sources: [Key authoritative market sources used]_
|
||||
_Secondary Market Sources: [Supporting market research and analysis]_
|
||||
_Market Web Search Queries: [Complete list of market search queries used]_
|
||||
_Market Data Currency: [All market data verified for {{current_year}} currency]_
|
||||
|
||||
### Market Research Quality Assurance
|
||||
|
||||
|
|
@ -344,9 +343,9 @@ _Market Analysis Tools: [Tools and resources for ongoing market analysis]_
|
|||
---
|
||||
|
||||
**Market Research Completion Date:** {{date}}
|
||||
**Research Period:** {{current_year}} comprehensive market analysis
|
||||
**Research Period:** current comprehensive market analysis
|
||||
**Document Length:** As needed for comprehensive market coverage
|
||||
**Source Verification:** All market facts cited with {{current_year}} sources
|
||||
**Source Verification:** All market facts cited with current sources
|
||||
**Market Confidence Level:** High - based on multiple authoritative market sources
|
||||
|
||||
_This comprehensive market research document serves as an authoritative market reference on {{research_topic}} and provides strategic market insights for informed decision-making._
|
||||
|
|
@ -365,7 +364,7 @@ _This comprehensive market research document serves as an authoritative market r
|
|||
- **Exhaustive Market Research Coverage**: All market aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Market Summary**: Key market findings and strategic implications highlighted
|
||||
- **Strategic Market Recommendations**: Actionable market insights based on comprehensive research
|
||||
- **Complete Market Source Citations**: Every market claim verified with {{current_year}} sources
|
||||
- **Complete Market Source Citations**: Every market claim verified with current sources
|
||||
|
||||
**Market Research Completeness:**
|
||||
|
||||
|
|
@ -380,7 +379,7 @@ _This comprehensive market research document serves as an authoritative market r
|
|||
- Professional market structure and compelling narrative
|
||||
- As long as needed for comprehensive market coverage
|
||||
- Multiple independent sources for all market claims
|
||||
- {{current_year}} market data throughout with proper citations
|
||||
- current market data throughout with proper citations
|
||||
|
||||
**Ready to complete this comprehensive market research document?**
|
||||
[C] Complete Research - Save final comprehensive market research document
|
||||
|
|
@ -404,7 +403,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
✅ Exhaustive market research coverage across all market aspects
|
||||
✅ Executive market summary with key findings and strategic implications
|
||||
✅ Strategic market recommendations grounded in comprehensive research
|
||||
✅ Complete market source verification with {{current_year}} citations
|
||||
✅ Complete market source verification with current citations
|
||||
✅ Professional market document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Market research workflow completed with comprehensive document
|
||||
|
|
@ -416,7 +415,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
❌ Incomplete market research coverage across market aspects
|
||||
❌ Not providing executive market summary with key findings
|
||||
❌ Missing strategic market recommendations based on research
|
||||
❌ Not using {{current_year}} market sources for all factual claims
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing market document without professional structure
|
||||
❌ Not presenting completion option for final market document
|
||||
|
||||
|
|
@ -461,7 +460,7 @@ Complete authoritative market research document on {{research_topic}} that:
|
|||
- Establishes professional market credibility through comprehensive research
|
||||
- Provides strategic market insights for informed decision-making
|
||||
- Serves as market reference document for continued use
|
||||
- Maintains highest market research quality standards with {{current_year}} verification
|
||||
- Maintains highest market research quality standards with current verification
|
||||
|
||||
## NEXT STEPS:
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,6 @@
|
|||
**Date:** {{date}}
|
||||
**Author:** {{user_name}}
|
||||
**Research Type:** {{research_type}}
|
||||
**Data Currency:** {{current_year}}
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@
|
|||
- **Research topic = "{{research_topic}}"** - discovered from initial discussion
|
||||
- **Research goals = "{{research_goals}}"** - captured from initial discussion
|
||||
- Focus on technical architecture and implementation research
|
||||
- Web search capabilities with {{current_year}} data are enabled
|
||||
- Web search is required to verify and supplement your knowledge with current facts
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ Start with technical scope understanding:
|
|||
|
||||
**Research Approach:**
|
||||
|
||||
- Current {{current_year}} web data with rigorous source verification
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence levels for uncertain technical information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
|
@ -66,7 +66,7 @@ For **{{research_topic}}**, I will research:
|
|||
✅ **Integration Patterns** - APIs, protocols, interoperability
|
||||
✅ **Performance Considerations** - scalability, optimization, patterns
|
||||
|
||||
**All using current {{current_year}} web data with source verification.**
|
||||
**All claims verified against current public sources.**
|
||||
|
||||
**Does this technical research scope and approach align with your goals?**
|
||||
[C] Continue - Begin technical research with this scope
|
||||
|
|
@ -77,7 +77,7 @@ For **{{research_topic}}**, I will research:
|
|||
|
||||
- Document scope confirmation in research file
|
||||
- Update frontmatter: `stepsCompleted: [1]`
|
||||
- Load: `./step-02-technology-stack.md`
|
||||
- Load: `./step-02-technical-overview.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
**Research Methodology:**
|
||||
|
||||
- Current {{current_year}} web data with rigorous source verification
|
||||
- Current web data with rigorous source verification
|
||||
- Multi-source validation for critical technical claims
|
||||
- Confidence level framework for uncertain information
|
||||
- Comprehensive technical coverage with architecture-specific insights
|
||||
|
|
@ -111,7 +111,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
✅ Technical research scope clearly confirmed with user
|
||||
✅ All technical analysis areas identified and explained
|
||||
✅ Research methodology with {{current_year}} data emphasized
|
||||
✅ Research methodology emphasized
|
||||
✅ [C] continue option presented and handled correctly
|
||||
✅ Scope confirmation documented when user proceeds
|
||||
✅ Proper routing to next technical research step
|
||||
|
|
@ -120,7 +120,7 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
❌ Not clearly confirming technical research scope with user
|
||||
❌ Missing critical technical analysis areas
|
||||
❌ Not emphasizing {{current_year}} web data requirement
|
||||
❌ Not explaining that web search is required for current facts
|
||||
❌ Not presenting [C] continue option
|
||||
❌ Proceeding without user scope confirmation
|
||||
❌ Not routing to next technical research step
|
||||
|
|
@ -131,6 +131,6 @@ When user selects 'C', append scope confirmation:
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C', load `./step-02-technology-stack.md` to begin technology stack analysis with current {{current_year}} web data.
|
||||
After user selects 'C', load `./step-02-technical-overview.md` to begin technology stack analysis.
|
||||
|
||||
Remember: This is SCOPE CONFIRMATION ONLY - no actual technical research yet, just confirming the research approach and scope!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current technology data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNOLOGY STACK ANALYST, not content generator
|
||||
- 💬 FOCUS on languages, frameworks, tools, and platforms
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms using current {{current_year}} web data with rigorous source verification.
|
||||
Conduct technology stack analysis focusing on languages, frameworks, tools, and platforms. Search the web to verify and supplement current facts.
|
||||
|
||||
## TECHNOLOGY STACK ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Conduct technology stack analysis focusing on languages, frameworks, tools, and
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different technology stack areas simultaneously and thoroughly.
|
||||
|
||||
Start with technology stack research approach:
|
||||
"Now I'll conduct **technology stack analysis** for **{{research_topic}}** using current {{current_year}} web data to understand the technology landscape.
|
||||
"Now I'll conduct **technology stack analysis** for **{{research_topic}}** to understand the technology landscape.
|
||||
|
||||
**Technology Stack Focus:**
|
||||
|
||||
|
|
@ -56,10 +56,10 @@ Start with technology stack research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} programming languages frameworks {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} development tools platforms {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} database storage technologies {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} cloud infrastructure platforms {{current_year}}"`
|
||||
Search the web: "{{research_topic}} programming languages frameworks"
|
||||
Search the web: "{{research_topic}} development tools platforms"
|
||||
Search the web: "{{research_topic}} database storage technologies"
|
||||
Search the web: "{{research_topic}} cloud infrastructure platforms"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ _Popular Languages: [Most widely used languages for {{research_topic}}]_
|
|||
_Emerging Languages: [Growing languages gaining adoption]_
|
||||
_Language Evolution: [How language preferences are changing]_
|
||||
_Performance Characteristics: [Language performance and suitability]_
|
||||
_Source: [URL with {{current_year}} language data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Frameworks and Libraries
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _Major Frameworks: [Dominant frameworks and their use cases]_
|
|||
_Micro-frameworks: [Lightweight options and specialized libraries]_
|
||||
_Evolution Trends: [How frameworks are evolving and changing]_
|
||||
_Ecosystem Maturity: [Library availability and community support]_
|
||||
_Source: [URL with {{current_year}} framework data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Database and Storage Technologies
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ _Relational Databases: [Traditional SQL databases and their evolution]_
|
|||
_NoSQL Databases: [Document, key-value, graph, and other NoSQL options]_
|
||||
_In-Memory Databases: [Redis, Memcached, and performance-focused solutions]_
|
||||
_Data Warehousing: [Analytics and big data storage solutions]_
|
||||
_Source: [URL with {{current_year}} database data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Tools and Platforms
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ _IDE and Editors: [Development environments and their evolution]_
|
|||
_Version Control: [Git and related development tools]_
|
||||
_Build Systems: [Compilation, packaging, and automation tools]_
|
||||
_Testing Frameworks: [Unit testing, integration testing, and QA tools]_
|
||||
_Source: [URL with {{current_year}} tools data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Cloud Infrastructure and Deployment
|
||||
|
||||
|
|
@ -144,7 +144,7 @@ _Major Cloud Providers: [AWS, Azure, GCP and their services]_
|
|||
_Container Technologies: [Docker, Kubernetes, and orchestration]_
|
||||
_Serverless Platforms: [FaaS and event-driven computing]_
|
||||
_CDN and Edge Computing: [Content delivery and distributed computing]_
|
||||
_Source: [URL with {{current_year}} cloud data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Trends
|
||||
|
||||
|
|
@ -153,14 +153,14 @@ _Migration Patterns: [How technology choices are evolving]_
|
|||
_Emerging Technologies: [New technologies gaining traction]_
|
||||
_Legacy Technology: [Older technologies being phased out]_
|
||||
_Community Trends: [Developer preferences and open-source adoption]_
|
||||
_Source: [URL with {{current_year}} adoption data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **technology stack analysis** using current {{current_year}} data to understand the technology landscape for {{research_topic}}.
|
||||
"I've completed **technology stack analysis** of the technology landscape for {{research_topic}}.
|
||||
|
||||
**Key Technology Stack Findings:**
|
||||
|
||||
|
|
@ -199,7 +199,8 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in technology web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical programming languages or frameworks
|
||||
❌ Incomplete database and storage technology analysis
|
||||
❌ Not identifying development tools and platforms
|
||||
|
|
@ -217,7 +218,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use technology documentation and best practices guides
|
||||
- Analyze open-source projects and their technology choices
|
||||
- Study technology adoption patterns and migration trends
|
||||
- Focus on current {{current_year}} technology data
|
||||
- Focus on current technology data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -234,4 +235,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-03-integration-patterns.md` to analyze APIs, communication protocols, and system interoperability for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} technology data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and emphasize current technology data with rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current integration data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN INTEGRATION ANALYST, not content generator
|
||||
- 💬 FOCUS on APIs, protocols, and system interoperability
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,7 +31,7 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability using current {{current_year}} web data with rigorous source verification.
|
||||
Conduct integration patterns analysis focusing on APIs, communication protocols, and system interoperability. Search the web to verify and supplement current facts.
|
||||
|
||||
## INTEGRATION PATTERNS ANALYSIS SEQUENCE:
|
||||
|
||||
|
|
@ -40,7 +40,7 @@ Conduct integration patterns analysis focusing on APIs, communication protocols,
|
|||
**UTILIZE SUBPROCESSES AND SUBAGENTS**: Use research subagents, subprocesses or parallel processing if available to thoroughly analyze different integration areas simultaneously and thoroughly.
|
||||
|
||||
Start with integration patterns research approach:
|
||||
"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** using current {{current_year}} web data to understand system integration approaches.
|
||||
"Now I'll conduct **integration patterns analysis** for **{{research_topic}}** to understand system integration approaches.
|
||||
|
||||
**Integration Patterns Focus:**
|
||||
|
||||
|
|
@ -56,10 +56,10 @@ Start with integration patterns research approach:
|
|||
|
||||
**Execute multiple web searches simultaneously:**
|
||||
|
||||
`WebSearch: "{{research_topic}} API design patterns protocols {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} communication protocols data formats {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} system interoperability integration {{current_year}}"`
|
||||
`WebSearch: "{{research_topic}} microservices integration patterns {{current_year}}"`
|
||||
Search the web: "{{research_topic}} API design patterns protocols"
|
||||
Search the web: "{{research_topic}} communication protocols data formats"
|
||||
Search the web: "{{research_topic}} system interoperability integration"
|
||||
Search the web: "{{research_topic}} microservices integration patterns"
|
||||
|
||||
**Analysis approach:**
|
||||
|
||||
|
|
@ -108,7 +108,7 @@ _RESTful APIs: [REST principles and best practices for {{research_topic}}]_
|
|||
_GraphQL APIs: [GraphQL adoption and implementation patterns]_
|
||||
_RPC and gRPC: [High-performance API communication patterns]_
|
||||
_Webhook Patterns: [Event-driven API integration approaches]_
|
||||
_Source: [URL with {{current_year}} API design data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Communication Protocols
|
||||
|
||||
|
|
@ -117,7 +117,7 @@ _HTTP/HTTPS Protocols: [Web-based communication patterns and evolution]_
|
|||
_WebSocket Protocols: [Real-time communication and persistent connections]_
|
||||
_Message Queue Protocols: [AMQP, MQTT, and messaging patterns]_
|
||||
_grpc and Protocol Buffers: [High-performance binary communication protocols]_
|
||||
_Source: [URL with {{current_year}} communication protocols data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Formats and Standards
|
||||
|
||||
|
|
@ -126,7 +126,7 @@ _JSON and XML: [Structured data exchange formats and their evolution]_
|
|||
_Protobuf and MessagePack: [Efficient binary serialization formats]_
|
||||
_CSV and Flat Files: [Legacy data integration and bulk transfer patterns]_
|
||||
_Custom Data Formats: [Domain-specific data exchange standards]_
|
||||
_Source: [URL with {{current_year}} data formats data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Interoperability Approaches
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ _Point-to-Point Integration: [Direct system-to-system communication patterns]_
|
|||
_API Gateway Patterns: [Centralized API management and routing]_
|
||||
_Service Mesh: [Service-to-service communication and observability]_
|
||||
_Enterprise Service Bus: [Traditional enterprise integration patterns]_
|
||||
_Source: [URL with {{current_year}} interoperability data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Microservices Integration Patterns
|
||||
|
||||
|
|
@ -144,7 +144,7 @@ _API Gateway Pattern: [External API management and routing]_
|
|||
_Service Discovery: [Dynamic service registration and discovery]_
|
||||
_Circuit Breaker Pattern: [Fault tolerance and resilience patterns]_
|
||||
_Saga Pattern: [Distributed transaction management]_
|
||||
_Source: [URL with {{current_year}} microservices data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Event-Driven Integration
|
||||
|
||||
|
|
@ -153,7 +153,7 @@ _Publish-Subscribe Patterns: [Event broadcasting and subscription models]_
|
|||
_Event Sourcing: [Event-based state management and persistence]_
|
||||
_Message Broker Patterns: [RabbitMQ, Kafka, and message routing]_
|
||||
_CQRS Patterns: [Command Query Responsibility Segregation]_
|
||||
_Source: [URL with {{current_year}} event-driven data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration Security Patterns
|
||||
|
||||
|
|
@ -162,14 +162,14 @@ _OAuth 2.0 and JWT: [API authentication and authorization patterns]_
|
|||
_API Key Management: [Secure API access and key rotation]_
|
||||
_Mutual TLS: [Certificate-based service authentication]_
|
||||
_Data Encryption: [Secure data transmission and storage]_
|
||||
_Source: [URL with {{current_year}} integration security data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 5. Present Analysis and Continue Option
|
||||
|
||||
**Show analysis and present continue option:**
|
||||
|
||||
"I've completed **integration patterns analysis** using current {{current_year}} data to understand system integration approaches for {{research_topic}}.
|
||||
"I've completed **integration patterns analysis** of system integration approaches for {{research_topic}}.
|
||||
|
||||
**Key Integration Patterns Findings:**
|
||||
|
||||
|
|
@ -208,7 +208,8 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in integration web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical API design patterns or protocols
|
||||
❌ Incomplete communication protocols analysis
|
||||
❌ Not identifying system interoperability approaches
|
||||
|
|
@ -226,7 +227,7 @@ Content is already written to document when generated in step 4. No additional a
|
|||
- Use communication protocol specifications and standards
|
||||
- Analyze integration platform and middleware solutions
|
||||
- Study microservices architecture patterns and case studies
|
||||
- Focus on current {{current_year}} integration data
|
||||
- Focus on current integration data
|
||||
- Present conflicting information when sources disagree
|
||||
- Apply confidence levels appropriately
|
||||
|
||||
|
|
@ -243,4 +244,4 @@ Content is already written to document when generated in step 4. No additional a
|
|||
|
||||
After user selects 'C', load `./step-04-architectural-patterns.md` to analyze architectural patterns, design decisions, and system structures for {{research_topic}}.
|
||||
|
||||
Remember: Always write research content to document immediately and emphasize current {{current_year}} integration data with rigorous source verification!
|
||||
Remember: Always write research content to document immediately and emphasize current integration data with rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current architectural data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A SYSTEMS ARCHITECT, not content generator
|
||||
- 💬 FOCUS on architectural patterns and design decisions
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📝 WRITE CONTENT IMMEDIATELY TO DOCUMENT
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,14 +31,14 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive architectural patterns analysis using current {{current_year}} web data with emphasis on design decisions and implementation approaches for {{research_topic}}.
|
||||
Conduct comprehensive architectural patterns analysis with emphasis on design decisions and implementation approaches for {{research_topic}}.
|
||||
|
||||
## ARCHITECTURAL PATTERNS SEQUENCE:
|
||||
|
||||
### 1. Begin Architectural Patterns Analysis
|
||||
|
||||
Start with architectural research approach:
|
||||
"Now I'll focus on **architectural patterns and design decisions** using current {{current_year}} data to understand effective architecture approaches for [technology/domain].
|
||||
"Now I'll focus on **architectural patterns and design decisions** for effective architecture approaches for [technology/domain].
|
||||
|
||||
**Architectural Patterns Focus:**
|
||||
|
||||
|
|
@ -53,7 +53,7 @@ Start with architectural research approach:
|
|||
### 2. Web Search for System Architecture Patterns
|
||||
|
||||
Search for current architecture patterns:
|
||||
`WebSearch: "system architecture patterns best practices {{current_year}}"`
|
||||
Search the web: "system architecture patterns best practices"
|
||||
|
||||
**Architecture focus:**
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Search for current architecture patterns:
|
|||
### 3. Web Search for Design Principles
|
||||
|
||||
Search for current design principles:
|
||||
`WebSearch: "software design principles patterns {{current_year}}"`
|
||||
Search the web: "software design principles patterns"
|
||||
|
||||
**Design focus:**
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ Search for current design principles:
|
|||
### 4. Web Search for Scalability Patterns
|
||||
|
||||
Search for current scalability approaches:
|
||||
`WebSearch: "scalability architecture patterns {{current_year}}"`
|
||||
Search the web: "scalability architecture patterns"
|
||||
|
||||
**Scalability focus:**
|
||||
|
||||
|
|
@ -100,43 +100,43 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### System Architecture Patterns
|
||||
|
||||
[System architecture patterns analysis with source citations]
|
||||
_Source: [URL with {{current_year}} architecture data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Design Principles and Best Practices
|
||||
|
||||
[Design principles analysis with source citations]
|
||||
_Source: [URL with {{current_year}} design data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability and Performance Patterns
|
||||
|
||||
[Scalability patterns analysis with source citations]
|
||||
_Source: [URL with {{current_year}} scalability data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Integration and Communication Patterns
|
||||
|
||||
[Integration patterns analysis with source citations]
|
||||
_Source: [URL with {{current_year}} integration data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Security Architecture Patterns
|
||||
|
||||
[Security patterns analysis with source citations]
|
||||
_Source: [URL with {{current_year}} security data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Data Architecture Patterns
|
||||
|
||||
[Data architecture analysis with source citations]
|
||||
_Source: [URL with {{current_year}} data architecture data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Architecture
|
||||
|
||||
[Deployment architecture analysis with source citations]
|
||||
_Source: [URL with {{current_year}} deployment data]_
|
||||
_Source: [URL]_
|
||||
```
|
||||
|
||||
### 6. Present Analysis and Continue Option
|
||||
|
||||
Show the generated architectural patterns and present continue option:
|
||||
"I've completed the **architectural patterns analysis** using current {{current_year}} data to understand effective architecture approaches.
|
||||
"I've completed the **architectural patterns analysis** for effective architecture approaches.
|
||||
|
||||
**Key Architectural Findings:**
|
||||
|
||||
|
|
@ -155,7 +155,7 @@ Show the generated architectural patterns and present continue option:
|
|||
|
||||
- Append the final content to the research document
|
||||
- Update frontmatter: `stepsCompleted: [1, 2, 3]`
|
||||
- Load: `./step-04-implementation-research.md`
|
||||
- Load: `./step-05-implementation-research.md`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
|
||||
|
|
@ -163,7 +163,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ System architecture patterns identified with current {{current_year}} citations
|
||||
✅ System architecture patterns identified with current citations
|
||||
✅ Design principles clearly documented and analyzed
|
||||
✅ Scalability and performance patterns thoroughly mapped
|
||||
✅ Integration and communication patterns captured
|
||||
|
|
@ -174,7 +174,8 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in architectural web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical system architecture patterns
|
||||
❌ Not analyzing design trade-offs and considerations
|
||||
❌ Incomplete scalability or performance patterns analysis
|
||||
|
|
@ -195,6 +196,6 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `./step-04-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
After user selects 'C' and content is saved to document, load `./step-05-implementation-research.md` to focus on implementation approaches and technology adoption.
|
||||
|
||||
Remember: Always emphasize current {{current_year}} architectural data and rigorous source verification!
|
||||
Remember: Always emphasize current architectural data and rigorous source verification!
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current implementation data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE AN IMPLEMENTATION ENGINEER, not content generator
|
||||
- 💬 FOCUS on implementation approaches and technology adoption
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
|
|
@ -28,14 +28,14 @@
|
|||
|
||||
## YOUR TASK:
|
||||
|
||||
Conduct comprehensive implementation research using current {{current_year}} web data with emphasis on practical implementation approaches and technology adoption.
|
||||
Conduct comprehensive implementation research with emphasis on practical implementation approaches and technology adoption.
|
||||
|
||||
## IMPLEMENTATION RESEARCH SEQUENCE:
|
||||
|
||||
### 1. Begin Implementation Research
|
||||
|
||||
Start with implementation research approach:
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis using current {{current_year}} data.
|
||||
"Now I'll complete our technical research with **implementation approaches and technology adoption** analysis.
|
||||
|
||||
**Implementation Research Focus:**
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ Start with implementation research approach:
|
|||
### 2. Web Search for Technology Adoption
|
||||
|
||||
Search for current adoption strategies:
|
||||
`WebSearch: "technology adoption strategies migration {{current_year}}"`
|
||||
Search the web: "technology adoption strategies migration"
|
||||
|
||||
**Adoption focus:**
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ Search for current adoption strategies:
|
|||
### 3. Web Search for Development Workflows
|
||||
|
||||
Search for current development practices:
|
||||
`WebSearch: "software development workflows tooling {{current_year}}"`
|
||||
Search the web: "software development workflows tooling"
|
||||
|
||||
**Workflow focus:**
|
||||
|
||||
|
|
@ -74,7 +74,7 @@ Search for current development practices:
|
|||
### 4. Web Search for Operational Excellence
|
||||
|
||||
Search for current operational practices:
|
||||
`WebSearch: "DevOps operations best practices {{current_year}}"`
|
||||
Search the web: "DevOps operations best practices"
|
||||
|
||||
**Operations focus:**
|
||||
|
||||
|
|
@ -97,37 +97,37 @@ When saving to document, append these Level 2 and Level 3 sections:
|
|||
### Technology Adoption Strategies
|
||||
|
||||
[Technology adoption analysis with source citations]
|
||||
_Source: [URL with {{current_year}} adoption data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Development Workflows and Tooling
|
||||
|
||||
[Development workflows analysis with source citations]
|
||||
_Source: [URL with {{current_year}} development data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Testing and Quality Assurance
|
||||
|
||||
[Testing approaches analysis with source citations]
|
||||
_Source: [URL with {{current_year}} testing data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Deployment and Operations Practices
|
||||
|
||||
[Deployment practices analysis with source citations]
|
||||
_Source: [URL with {{current_year}} deployment data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Team Organization and Skills
|
||||
|
||||
[Team organization analysis with source citations]
|
||||
_Source: [URL with {{current_year}} team data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Cost Optimization and Resource Management
|
||||
|
||||
[Cost optimization analysis with source citations]
|
||||
_Source: [URL with {{current_year}} optimization data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Risk Assessment and Mitigation
|
||||
|
||||
[Risk mitigation analysis with source citations]
|
||||
_Source: [URL with {{current_year}} risk data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## Technical Research Recommendations
|
||||
|
||||
|
|
@ -151,7 +151,7 @@ _Source: [URL with {{current_year}} risk data]_
|
|||
### 6. Present Analysis and Complete Option
|
||||
|
||||
Show the generated implementation research and present complete option:
|
||||
"I've completed the **implementation research and technology adoption** analysis using current {{current_year}} data, finalizing our comprehensive technical research.
|
||||
"I've completed the **implementation research and technology adoption** analysis, finalizing our comprehensive technical research.
|
||||
|
||||
**Implementation Highlights:**
|
||||
|
||||
|
|
@ -185,7 +185,7 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ Technology adoption strategies identified with current {{current_year}} citations
|
||||
✅ Technology adoption strategies identified with current citations
|
||||
✅ Development workflows and tooling thoroughly analyzed
|
||||
✅ Testing and deployment practices clearly documented
|
||||
✅ Team organization and skill requirements mapped
|
||||
|
|
@ -196,7 +196,8 @@ When user selects 'C', append the content directly to the research document usin
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not using {{current_year}} in implementation web searches
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
|
||||
❌ Missing critical technology adoption strategies
|
||||
❌ Not providing practical implementation guidance
|
||||
❌ Incomplete development workflows or operational practices analysis
|
||||
|
|
@ -234,4 +235,4 @@ Technical research workflow complete. User may:
|
|||
- Combine technical research with other research types for comprehensive insights
|
||||
- Move forward with implementation based on technical insights
|
||||
|
||||
Congratulations on completing comprehensive technical research with current {{current_year}} data! 🎉
|
||||
Congratulations on completing comprehensive technical research! 🎉
|
||||
|
|
|
|||
|
|
@ -6,10 +6,10 @@
|
|||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS use {{current_year}} web searches for current technical data
|
||||
- ✅ Search the web to verify and supplement your knowledge with current facts
|
||||
- 📋 YOU ARE A TECHNICAL RESEARCH STRATEGIST, not content generator
|
||||
- 💬 FOCUS on comprehensive technical synthesis and authoritative conclusions
|
||||
- 🔍 WEB RESEARCH REQUIRED - Use {{current_year}} data and verify sources
|
||||
- 🔍 WEB SEARCH REQUIRED - verify current facts against live sources
|
||||
- 📄 PRODUCE COMPREHENSIVE DOCUMENT with narrative intro, TOC, and summary
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -74,7 +74,7 @@ Produce a comprehensive, authoritative technical research document on **{{resear
|
|||
- Set authoritative, technical expert tone
|
||||
|
||||
**Web Search for Technical Introduction Context:**
|
||||
`WebSearch: "{{research_topic}} technical significance importance {{current_year}}"`
|
||||
Search the web: "{{research_topic}} technical significance importance"
|
||||
|
||||
### 3. Synthesize All Technical Research Sections
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ Produce a comprehensive, authoritative technical research document on **{{resear
|
|||
|
||||
## Executive Summary
|
||||
|
||||
[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive {{current_year}} technical research]
|
||||
[2-3 paragraph compelling summary of the most critical technical findings and strategic implications for {{research_topic}} based on comprehensive current technical research]
|
||||
|
||||
**Key Technical Findings:**
|
||||
|
||||
|
|
@ -127,10 +127,10 @@ Produce a comprehensive, authoritative technical research document on **{{resear
|
|||
|
||||
### Technical Research Significance
|
||||
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical in {{current_year}}]
|
||||
_Technical Importance: [Strategic technical significance with {{current_year}} context]_
|
||||
[Compelling technical narrative about why {{research_topic}} research is critical right now]
|
||||
_Technical Importance: [Strategic technical significance with current context]_
|
||||
_Business Impact: [Business implications of technical research]_
|
||||
_Source: [URL with {{current_year}} technical significance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Research Methodology
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ _Source: [URL with {{current_year}} technical significance data]_
|
|||
- **Technical Scope**: [Comprehensive technical coverage areas]
|
||||
- **Data Sources**: [Authoritative technical sources and verification approach]
|
||||
- **Analysis Framework**: [Structured technical analysis methodology]
|
||||
- **Time Period**: [{{current_year}} focus and technical evolution context]
|
||||
- **Time Period**: [current focus and technical evolution context]
|
||||
- **Technical Depth**: [Level of technical detail and analysis]
|
||||
|
||||
### Technical Research Goals and Objectives
|
||||
|
|
@ -156,11 +156,11 @@ _Source: [URL with {{current_year}} technical significance data]_
|
|||
|
||||
### Current Technical Architecture Patterns
|
||||
|
||||
[Comprehensive architectural analysis synthesized from step-03 with {{current_year}} context]
|
||||
[Comprehensive architectural analysis synthesized from step-03 with current context]
|
||||
_Dominant Patterns: [Current architectural approaches]_
|
||||
_Architectural Evolution: [Historical and current evolution patterns]_
|
||||
_Architectural Trade-offs: [Key architectural decisions and implications]_
|
||||
_Source: [URL with {{current_year}} architectural data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### System Design Principles and Best Practices
|
||||
|
||||
|
|
@ -168,18 +168,18 @@ _Source: [URL with {{current_year}} architectural data]_
|
|||
_Design Principles: [Core principles guiding {{research_topic}} implementations]_
|
||||
_Best Practice Patterns: [Industry-standard approaches and methodologies]_
|
||||
_Architectural Quality Attributes: [Performance, scalability, maintainability considerations]_
|
||||
_Source: [URL with {{current_year}} design principles data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 3. Implementation Approaches and Best Practices
|
||||
|
||||
### Current Implementation Methodologies
|
||||
|
||||
[Implementation analysis from step-04 with {{current_year}} context]
|
||||
[Implementation analysis from step-04 with current context]
|
||||
_Development Approaches: [Current development methodologies and approaches]_
|
||||
_Code Organization Patterns: [Structural patterns and organization strategies]_
|
||||
_Quality Assurance Practices: [Testing, validation, and quality approaches]_
|
||||
_Deployment Strategies: [Current deployment and operations practices]_
|
||||
_Source: [URL with {{current_year}} implementation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Implementation Framework and Tooling
|
||||
|
||||
|
|
@ -187,18 +187,18 @@ _Source: [URL with {{current_year}} implementation data]_
|
|||
_Development Frameworks: [Popular frameworks and their characteristics]_
|
||||
_Tool Ecosystem: [Development tools and platform considerations]_
|
||||
_Build and Deployment Systems: [CI/CD and automation approaches]_
|
||||
_Source: [URL with {{current_year}} framework data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 4. Technology Stack Evolution and Current Trends
|
||||
|
||||
### Current Technology Stack Landscape
|
||||
|
||||
[Technology stack analysis from step-02 with {{current_year}} updates]
|
||||
[Technology stack analysis from step-02 with current updates]
|
||||
_Programming Languages: [Current language trends and adoption patterns]_
|
||||
_Frameworks and Libraries: [Popular frameworks and their use cases]_
|
||||
_Database and Storage Technologies: [Current data storage and management trends]_
|
||||
_API and Communication Technologies: [Integration and communication patterns]_
|
||||
_Source: [URL with {{current_year}} technology stack data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technology Adoption Patterns
|
||||
|
||||
|
|
@ -206,17 +206,17 @@ _Source: [URL with {{current_year}} technology stack data]_
|
|||
_Adoption Trends: [Technology adoption rates and patterns]_
|
||||
_Migration Patterns: [Technology migration and evolution trends]_
|
||||
_Emerging Technologies: [New technologies and their potential impact]_
|
||||
_Source: [URL with {{current_year}} adoption data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 5. Integration and Interoperability Patterns
|
||||
|
||||
### Current Integration Approaches
|
||||
|
||||
[Integration patterns analysis with {{current_year}} context]
|
||||
[Integration patterns analysis with current context]
|
||||
_API Design Patterns: [Current API design and implementation patterns]_
|
||||
_Service Integration: [Microservices and service integration approaches]_
|
||||
_Data Integration: [Data exchange and integration patterns]_
|
||||
_Source: [URL with {{current_year}} integration data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Interoperability Standards and Protocols
|
||||
|
||||
|
|
@ -224,7 +224,7 @@ _Source: [URL with {{current_year}} integration data]_
|
|||
_Standards Compliance: [Industry standards and compliance requirements]_
|
||||
_Protocol Selection: [Communication protocols and selection criteria]_
|
||||
_Integration Challenges: [Common integration challenges and solutions]_
|
||||
_Source: [URL with {{current_year}} interoperability data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 6. Performance and Scalability Analysis
|
||||
|
||||
|
|
@ -234,7 +234,7 @@ _Source: [URL with {{current_year}} interoperability data]_
|
|||
_Performance Benchmarks: [Current performance characteristics and benchmarks]_
|
||||
_Optimization Strategies: [Performance optimization approaches and techniques]_
|
||||
_Monitoring and Measurement: [Performance monitoring and measurement practices]_
|
||||
_Source: [URL with {{current_year}} performance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Scalability Patterns and Approaches
|
||||
|
||||
|
|
@ -242,17 +242,17 @@ _Source: [URL with {{current_year}} performance data]_
|
|||
_Scalability Patterns: [Architectural and design patterns for scalability]_
|
||||
_Capacity Planning: [Capacity planning and resource management approaches]_
|
||||
_Elasticity and Auto-scaling: [Dynamic scaling approaches and implementations]_
|
||||
_Source: [URL with {{current_year}} scalability data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 7. Security and Compliance Considerations
|
||||
|
||||
### Security Best Practices and Frameworks
|
||||
|
||||
[Security analysis with {{current_year}} context]
|
||||
[Security analysis with current context]
|
||||
_Security Frameworks: [Current security frameworks and best practices]_
|
||||
_Threat Landscape: [Current security threats and mitigation approaches]_
|
||||
_Secure Development Practices: [Secure coding and development lifecycle]_
|
||||
_Source: [URL with {{current_year}} security data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Compliance and Regulatory Considerations
|
||||
|
||||
|
|
@ -260,7 +260,7 @@ _Source: [URL with {{current_year}} security data]_
|
|||
_Industry Standards: [Relevant industry standards and compliance requirements]_
|
||||
_Regulatory Compliance: [Legal and regulatory considerations for {{research_topic}}]_
|
||||
_Audit and Governance: [Technical audit and governance practices]_
|
||||
_Source: [URL with {{current_year}} compliance data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 8. Strategic Technical Recommendations
|
||||
|
||||
|
|
@ -270,7 +270,7 @@ _Source: [URL with {{current_year}} compliance data]_
|
|||
_Architecture Recommendations: [Recommended architectural approaches and patterns]_
|
||||
_Technology Selection: [Recommended technology stack and selection criteria]_
|
||||
_Implementation Strategy: [Recommended implementation approaches and methodologies]_
|
||||
_Source: [URL with {{current_year}} technical strategy data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Competitive Technical Advantage
|
||||
|
||||
|
|
@ -278,7 +278,7 @@ _Source: [URL with {{current_year}} technical strategy data]_
|
|||
_Technology Differentiation: [Technical approaches that provide competitive advantage]_
|
||||
_Innovation Opportunities: [Areas for technical innovation and differentiation]_
|
||||
_Strategic Technology Investments: [Recommended technology investments and priorities]_
|
||||
_Source: [URL with {{current_year}} competitive analysis data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 9. Implementation Roadmap and Risk Assessment
|
||||
|
||||
|
|
@ -288,7 +288,7 @@ _Source: [URL with {{current_year}} competitive analysis data]_
|
|||
_Implementation Phases: [Recommended phased implementation approach]_
|
||||
_Technology Migration Strategy: [Approach for technology adoption and migration]_
|
||||
_Resource Planning: [Technical resources and capabilities planning]_
|
||||
_Source: [URL with {{current_year}} implementation planning data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Technical Risk Management
|
||||
|
||||
|
|
@ -296,7 +296,7 @@ _Source: [URL with {{current_year}} implementation planning data]_
|
|||
_Technical Risks: [Major technical risks and mitigation strategies]_
|
||||
_Implementation Risks: [Risks associated with implementation and deployment]_
|
||||
_Business Impact Risks: [Technical risks and their business implications]_
|
||||
_Source: [URL with {{current_year}} technical risk data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 10. Future Technical Outlook and Innovation Opportunities
|
||||
|
||||
|
|
@ -306,7 +306,7 @@ _Source: [URL with {{current_year}} technical risk data]_
|
|||
_Near-term Technical Evolution: [1-2 year technical development expectations]_
|
||||
_Medium-term Technology Trends: [3-5 year expected technical developments]_
|
||||
_Long-term Technical Vision: [5+ year technical outlook for {{research_topic}}]_
|
||||
_Source: [URL with {{current_year}} future trends data]_
|
||||
_Source: [URL]_
|
||||
|
||||
### Innovation and Research Opportunities
|
||||
|
||||
|
|
@ -314,7 +314,7 @@ _Source: [URL with {{current_year}} future trends data]_
|
|||
_Research Opportunities: [Areas for technical research and innovation]_
|
||||
_Emerging Technology Adoption: [Potential new technologies and adoption timelines]_
|
||||
_Innovation Framework: [Approach for fostering technical innovation]_
|
||||
_Source: [URL with {{current_year}} innovation data]_
|
||||
_Source: [URL]_
|
||||
|
||||
## 11. Technical Research Methodology and Source Verification
|
||||
|
||||
|
|
@ -324,7 +324,6 @@ _Source: [URL with {{current_year}} innovation data]_
|
|||
_Primary Technical Sources: [Key authoritative technical sources used]_
|
||||
_Secondary Technical Sources: [Supporting technical research and analysis]_
|
||||
_Technical Web Search Queries: [Complete list of technical search queries used]_
|
||||
_Technical Data Currency: [All technical data verified for {{current_year}} currency]_
|
||||
|
||||
### Technical Research Quality Assurance
|
||||
|
||||
|
|
@ -370,9 +369,9 @@ _Technical Communities: [Professional networks and technical communities]_
|
|||
---
|
||||
|
||||
**Technical Research Completion Date:** {{date}}
|
||||
**Research Period:** {{current_year}} comprehensive technical analysis
|
||||
**Research Period:** current comprehensive technical analysis
|
||||
**Document Length:** As needed for comprehensive technical coverage
|
||||
**Source Verification:** All technical facts cited with {{current_year}} sources
|
||||
**Source Verification:** All technical facts cited with current sources
|
||||
**Technical Confidence Level:** High - based on multiple authoritative technical sources
|
||||
|
||||
_This comprehensive technical research document serves as an authoritative technical reference on {{research_topic}} and provides strategic technical insights for informed decision-making and implementation._
|
||||
|
|
@ -391,7 +390,7 @@ _This comprehensive technical research document serves as an authoritative techn
|
|||
- **Exhaustive Technical Research Coverage**: All technical aspects of {{research_topic}} thoroughly analyzed
|
||||
- **Executive Technical Summary**: Key technical findings and strategic implications highlighted
|
||||
- **Strategic Technical Recommendations**: Actionable technical insights based on comprehensive research
|
||||
- **Complete Technical Source Citations**: Every technical claim verified with {{current_year}} sources
|
||||
- **Complete Technical Source Citations**: Every technical claim verified with current sources
|
||||
|
||||
**Technical Research Completeness:**
|
||||
|
||||
|
|
@ -407,7 +406,7 @@ _This comprehensive technical research document serves as an authoritative techn
|
|||
- Professional technical structure and compelling narrative
|
||||
- As long as needed for comprehensive technical coverage
|
||||
- Multiple independent technical sources for all claims
|
||||
- {{current_year}} technical data throughout with proper citations
|
||||
- current technical data throughout with proper citations
|
||||
|
||||
**Ready to complete this comprehensive technical research document?**
|
||||
[C] Complete Research - Save final comprehensive technical document
|
||||
|
|
@ -432,7 +431,7 @@ When user selects 'C', append the complete comprehensive technical research docu
|
|||
✅ Exhaustive technical research coverage across all technical aspects
|
||||
✅ Executive technical summary with key findings and strategic implications
|
||||
✅ Strategic technical recommendations grounded in comprehensive research
|
||||
✅ Complete technical source verification with {{current_year}} citations
|
||||
✅ Complete technical source verification with current citations
|
||||
✅ Professional technical document structure and compelling narrative
|
||||
✅ [C] complete option presented and handled correctly
|
||||
✅ Technical research workflow completed with comprehensive document
|
||||
|
|
@ -444,7 +443,7 @@ When user selects 'C', append the complete comprehensive technical research docu
|
|||
❌ Incomplete technical research coverage across technical aspects
|
||||
❌ Not providing executive technical summary with key findings
|
||||
❌ Missing strategic technical recommendations based on research
|
||||
❌ Not using {{current_year}} technical sources for all factual claims
|
||||
❌ Relying solely on training data without web verification for current facts
|
||||
❌ Producing technical document without professional structure
|
||||
❌ Not presenting completion option for final technical document
|
||||
|
||||
|
|
@ -481,6 +480,6 @@ Complete authoritative technical research document on {{research_topic}} that:
|
|||
- Establishes technical credibility through comprehensive research
|
||||
- Provides strategic technical insights for informed decision-making
|
||||
- Serves as technical reference document for continued use
|
||||
- Maintains highest technical research quality standards with {{current_year}} verification
|
||||
- Maintains highest technical research quality standards with current verification
|
||||
|
||||
Congratulations on completing comprehensive technical research with professional documentation! 🎉
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ web_bundle: true
|
|||
**Document Standards:**
|
||||
|
||||
- **Comprehensive Coverage**: Exhaustive research with no critical gaps
|
||||
- **Source Verification**: Every factual claim cited with URLs from {{current_year}}
|
||||
- **Source Verification**: Every factual claim backed by web sources with URL citations
|
||||
- **Document Length**: As long as needed to fully cover the research topic
|
||||
- **Professional Structure**: Compelling narrative introduction, detailed TOC, and comprehensive summary
|
||||
- **Authoritative Sources**: Multiple independent sources for all critical claims
|
||||
|
|
@ -46,7 +46,7 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
|
|||
|
||||
- `project_name`, `output_folder`, `user_name`
|
||||
- `communication_language`, `document_output_language`, `user_skill_level`
|
||||
- `date`, `current_year`, `current_month` as system-generated values
|
||||
- `date` as a system-generated value
|
||||
- `enable_web_research = true` (web research is default behavior)
|
||||
|
||||
### Paths
|
||||
|
|
@ -57,11 +57,17 @@ Load config from `{project-root}/{bmad_folder}/bmm/config.yaml` and resolve:
|
|||
|
||||
---
|
||||
|
||||
## PREREQUISITE
|
||||
|
||||
**⛔ Web search required.** If unavailable, abort and tell the user.
|
||||
|
||||
---
|
||||
|
||||
## RESEARCH BEHAVIOR
|
||||
|
||||
### Web Research Standards
|
||||
|
||||
- **Current Data Only**: Always use {{current_year}} in web searches
|
||||
- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
|
||||
- **Source Verification**: Require citations for all factual claims
|
||||
- **Anti-Hallucination Protocol**: Never present information without verified sources
|
||||
- **Multiple Sources**: Require at least 2 independent sources for critical claims
|
||||
|
|
@ -88,7 +94,7 @@ Execute research type discovery and routing:
|
|||
**Research Standards:**
|
||||
|
||||
- **Anti-Hallucination Protocol**: Never present information without verified sources
|
||||
- **Current Data Only**: Always use {{current_year}} in web searches
|
||||
- **Current Data Only**: Search the web to verify and supplement your knowledge with current facts
|
||||
- **Source Citation**: Always include URLs for factual claims from web searches
|
||||
- **Multiple Sources**: Require 2+ independent sources for critical claims
|
||||
- **Conflict Resolution**: Present conflicting views and note discrepancies
|
||||
|
|
@ -96,7 +102,7 @@ Execute research type discovery and routing:
|
|||
|
||||
### Collaborative Research Discovery
|
||||
|
||||
"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with current {{current_year}} data and rigorous source verification, while you bring the domain expertise and research direction.
|
||||
"Welcome {{user_name}}! I'm excited to work with you as your research partner. I bring web research capabilities with rigorous source verification, while you bring the domain expertise and research direction.
|
||||
|
||||
**Let me help you clarify what you'd like to research.**
|
||||
|
||||
|
|
@ -190,10 +196,9 @@ research_topic: '{{research_topic}}'
|
|||
research_goals: '{{research_goals}}'
|
||||
user_name: '{{user_name}}'
|
||||
date: '{{date}}'
|
||||
current_year: '{{current_year}}'
|
||||
web_research_enabled: true
|
||||
source_verification: true
|
||||
---
|
||||
```
|
||||
|
||||
**Note:** All research workflows emphasize current web data with {{current_year}} searches and rigorous source verification.
|
||||
**Note:** All research workflows require web search for current data and source verification.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,13 @@
|
|||
---
|
||||
stepsCompleted: []
|
||||
inputDocuments: []
|
||||
documentCounts:
|
||||
briefs: 0
|
||||
research: 0
|
||||
brainstorming: 0
|
||||
projectDocs: 0
|
||||
workflowType: 'prd'
|
||||
lastStep: 0
|
||||
---
|
||||
|
||||
# Product Requirements Document - {{project_name}}
|
||||
|
|
|
|||
|
|
@ -1,43 +1,75 @@
|
|||
---
|
||||
name: 'step-01-init'
|
||||
description: 'Initialize the PRD workflow by detecting continuation state and setting up the document'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-01-init.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-02-discovery.md'
|
||||
continueStepFile: '{workflow_path}/steps/step-01b-continue.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Template References
|
||||
prdTemplate: '{workflow_path}/prd-template.md'
|
||||
---
|
||||
|
||||
# Step 1: Workflow Initialization
|
||||
|
||||
**Progress: Step 1 of 10** - Next: Project Discovery
|
||||
**Progress: Step 1 of 11** - Next: Project Discovery
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Initialize the PRD workflow by detecting continuation state, discovering input documents, and setting up the document structure for collaborative product requirement discovery.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
### Universal Rules:
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS treat this as collaborative discovery between PM peers
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- 💬 FOCUS on initialization and setup only - don't look ahead to future steps
|
||||
- 🚪 DETECT existing workflow state and handle continuation properly
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a product-focused PM facilitator collaborating with an expert peer
|
||||
- ✅ If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus only on initialization and setup - no content generation yet
|
||||
- 🚫 FORBIDDEN to look ahead to future steps or assume knowledge from them
|
||||
- 💬 Approach: Systematic setup with clear reporting to user
|
||||
- 🚪 Detect existing workflow state and handle continuation properly
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- 💾 Initialize document and update frontmatter
|
||||
- 🎯 Show your analysis of current state before taking any action
|
||||
- 💾 Initialize document structure and update frontmatter appropriately
|
||||
- 📖 Set up frontmatter `stepsCompleted: [1]` before loading next step
|
||||
- 🚫 FORBIDDEN to load next step until setup is complete
|
||||
- 🚫 FORBIDDEN to load next step until user selects 'C' (Continue)
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Variables from workflow.md are available in memory
|
||||
- Previous context = what's in output document + frontmatter
|
||||
- Don't assume knowledge from other steps
|
||||
- Input document discovery happens in this step
|
||||
- Available context: Variables from workflow.md are available in memory
|
||||
- Focus: Workflow initialization and document setup only
|
||||
- Limits: Don't assume knowledge from other steps or create content yet
|
||||
- Dependencies: Configuration loaded from workflow.md initialization
|
||||
|
||||
## YOUR TASK:
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
Initialize the PRD workflow by detecting continuation state and setting up the document.
|
||||
|
||||
## INITIALIZATION SEQUENCE:
|
||||
|
||||
### 1. Check for Existing Workflow
|
||||
### 1. Check for Existing Workflow State
|
||||
|
||||
First, check if the output document already exists:
|
||||
|
||||
- Look for file at `{output_folder}/prd.md`
|
||||
**Workflow State Detection:**
|
||||
|
||||
- Look for file at `{outputFile}`
|
||||
- If exists, read the complete file including frontmatter
|
||||
- If not exists, this is a fresh workflow
|
||||
|
||||
|
|
@ -45,9 +77,12 @@ First, check if the output document already exists:
|
|||
|
||||
If the document exists and has frontmatter with `stepsCompleted`:
|
||||
|
||||
- **STOP here** and load `./step-01b-continue.md` immediately
|
||||
**Continuation Protocol:**
|
||||
|
||||
- **STOP immediately** and load `{continueStepFile}`
|
||||
- Do not proceed with any initialization tasks
|
||||
- Let step-01b handle the continuation logic
|
||||
- Let step-01b handle all continuation logic
|
||||
- This is an auto-proceed situation - no user choice needed
|
||||
|
||||
### 3. Fresh Workflow Setup (If No Document)
|
||||
|
||||
|
|
@ -55,7 +90,18 @@ If no document exists or no `stepsCompleted` in frontmatter:
|
|||
|
||||
#### A. Input Document Discovery
|
||||
|
||||
Discover and load context documents using smart discovery:
|
||||
Discover and load context documents using smart discovery.
|
||||
|
||||
**IMPORTANT: Track document counts as you discover files.**
|
||||
|
||||
Initialize counters:
|
||||
|
||||
```
|
||||
briefCount = 0
|
||||
researchCount = 0
|
||||
brainstormingCount = 0
|
||||
projectDocsCount = 0
|
||||
```
|
||||
|
||||
**Product Brief (Priority: Analysis → Main → Sharded → Whole):**
|
||||
|
||||
|
|
@ -64,6 +110,7 @@ Discover and load context documents using smart discovery:
|
|||
3. If no main files: Check for sharded brief folder: `{output_folder}/*brief*/**/*.md`
|
||||
4. If sharded folder exists: Load EVERY file in that folder completely
|
||||
5. Add discovered files to `inputDocuments` frontmatter
|
||||
6. **Update briefCount with number of files found**
|
||||
|
||||
**Research Documents (Priority: Analysis → Main → Sharded → Whole):**
|
||||
|
||||
|
|
@ -72,20 +119,23 @@ Discover and load context documents using smart discovery:
|
|||
3. If no main files: Check for sharded research folder: `{output_folder}/*research*/**/*.md`
|
||||
4. Load useful research files completely
|
||||
5. Add discovered files to `inputDocuments` frontmatter
|
||||
6. **Update researchCount with number of files found**
|
||||
|
||||
**Brainstorming Documents (Priority: Analysis → Main):**
|
||||
|
||||
1. Check analysis folder: `{output_folder}/analysis/brainstorming/*brainstorming*.md`
|
||||
2. If no analysis files: Try main folder: `{output_folder}/*brainstorming*.md`
|
||||
3. Add discovered files to `inputDocuments` frontmatter
|
||||
4. **Update brainstormingCount with number of files found**
|
||||
|
||||
**Project Documentation (Existing Projects):**
|
||||
**Project Documentation (Existing Projects - Brownfield):**
|
||||
|
||||
1. Look for index file: `{output_folder}/index.md`
|
||||
2. CRITICAL: Load index.md to understand what project files are available
|
||||
3. Read available files from index to understand existing project context
|
||||
4. This provides essential context for extending existing project with new PRD
|
||||
5. Add discovered files to `inputDocuments` frontmatter
|
||||
6. **Update projectDocsCount with number of files found (including index.md)**
|
||||
|
||||
**Loading Rules:**
|
||||
|
||||
|
|
@ -96,13 +146,20 @@ Discover and load context documents using smart discovery:
|
|||
|
||||
#### B. Create Initial Document
|
||||
|
||||
Copy the template from `{installed_path}/prd-template.md` to `{output_folder}/prd.md`
|
||||
Initialize frontmatter with:
|
||||
**Document Setup:**
|
||||
|
||||
- Copy the template from `{prdTemplate}` to `{outputFile}`
|
||||
- Initialize frontmatter with proper structure including document counts:
|
||||
|
||||
```yaml
|
||||
---
|
||||
stepsCompleted: []
|
||||
inputDocuments: []
|
||||
documentCounts:
|
||||
briefs: { { briefCount } }
|
||||
research: { { researchCount } }
|
||||
brainstorming: { { brainstormingCount } }
|
||||
projectDocs: { { projectDocsCount } }
|
||||
workflowType: 'prd'
|
||||
lastStep: 0
|
||||
project_name: '{{project_name}}'
|
||||
|
|
@ -111,51 +168,76 @@ date: '{{date}}'
|
|||
---
|
||||
```
|
||||
|
||||
#### C. Complete Initialization and Report
|
||||
#### C. Present Initialization Results
|
||||
|
||||
Complete setup and report to user:
|
||||
**Setup Report to User:**
|
||||
|
||||
"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
|
||||
|
||||
**Document Setup:**
|
||||
|
||||
- Created: `{output_folder}/prd.md` from template
|
||||
- Created: `{outputFile}` from template
|
||||
- Initialized frontmatter with workflow state
|
||||
|
||||
**Input Documents Discovered:**
|
||||
Report what was found:
|
||||
"Welcome {{user_name}}! I've set up your PRD workspace for {{project_name}}.
|
||||
|
||||
**Documents Found:**
|
||||
|
||||
- Product brief: {number of brief files loaded or "None found"}
|
||||
- Research: {number of research files loaded or "None found"}
|
||||
- Project docs: {number of project files loaded or "None found"}
|
||||
- Product briefs: {{briefCount}} files {if briefCount > 0}✓ loaded{else}(none found){/if}
|
||||
- Research: {{researchCount}} files {if researchCount > 0}✓ loaded{else}(none found){/if}
|
||||
- Brainstorming: {{brainstormingCount}} files {if brainstormingCount > 0}✓ loaded{else}(none found){/if}
|
||||
- Project docs: {{projectDocsCount}} files {if projectDocsCount > 0}✓ loaded (brownfield project){else}(none found - greenfield project){/if}
|
||||
|
||||
**Files loaded:** {list of specific file names or "No additional documents found"}
|
||||
|
||||
Do you have any other documents you'd like me to include, or shall we continue to the next step?
|
||||
{if projectDocsCount > 0}
|
||||
📋 **Note:** This is a **brownfield project**. Your existing project documentation has been loaded. In the next step, I'll ask specifically about what new features or changes you want to add to your existing system.
|
||||
{/if}
|
||||
|
||||
[C] Continue - Save this and move to Project Discovery (Step 2 of 10)
|
||||
Do you have any other documents you'd like me to include, or shall we continue to the next step?"
|
||||
|
||||
## SUCCESS METRICS:
|
||||
### 4. Present MENU OPTIONS
|
||||
|
||||
✅ Existing workflow detected and handed off to step-01b correctly
|
||||
✅ Fresh workflow initialized with template and frontmatter
|
||||
✅ Input documents discovered and loaded using sharded-first logic
|
||||
✅ All discovered files tracked in frontmatter `inputDocuments`
|
||||
✅ User confirmed document setup and can proceed
|
||||
Display menu after setup report:
|
||||
|
||||
## FAILURE MODES:
|
||||
"[C] Continue - Save this and move to Project Discovery (Step 2 of 11)"
|
||||
|
||||
❌ Proceeding with fresh initialization when existing workflow exists
|
||||
❌ Not updating frontmatter with discovered input documents
|
||||
❌ Creating document without proper template
|
||||
❌ Not checking sharded folders first before whole files
|
||||
❌ Not reporting what documents were found to user
|
||||
#### Menu Handling Logic:
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
- IF C: Update frontmatter with `stepsCompleted: [1]`, then load, read entire file, then execute {nextStepFile}
|
||||
- IF user provides additional files: Load them, update inputDocuments and documentCounts, redisplay report
|
||||
- IF user asks questions: Answer and redisplay menu
|
||||
|
||||
## NEXT STEP:
|
||||
#### EXECUTION RULES:
|
||||
|
||||
After user selects [C] to continue, load `{installed_path}/step/step-02-discovery.md` to begin the project discovery phase.
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [frontmatter properly updated with stepsCompleted: [1] and documentCounts], will you then load and read fully `{nextStepFile}` to execute and begin project discovery.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- Existing workflow detected and properly handed off to step-01b
|
||||
- Fresh workflow initialized with template and proper frontmatter
|
||||
- Input documents discovered and loaded using sharded-first logic
|
||||
- All discovered files tracked in frontmatter `inputDocuments`
|
||||
- **Document counts stored in frontmatter `documentCounts`**
|
||||
- User clearly informed of brownfield vs greenfield status
|
||||
- Menu presented and user input handled correctly
|
||||
- Frontmatter updated with `stepsCompleted: [1]` before proceeding
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Proceeding with fresh initialization when existing workflow exists
|
||||
- Not updating frontmatter with discovered input documents
|
||||
- **Not storing document counts in frontmatter**
|
||||
- Creating document without proper template structure
|
||||
- Not checking sharded folders first before whole files
|
||||
- Not reporting discovered documents to user clearly
|
||||
- Proceeding without user selecting 'C' (Continue)
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
|
|
@ -1,56 +1,81 @@
|
|||
---
|
||||
name: 'step-01b-continue'
|
||||
description: 'Resume an interrupted PRD workflow from the last completed step'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-01b-continue.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
---
|
||||
|
||||
# Step 1B: Workflow Continuation
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Resume the PRD workflow from where it was left off, ensuring smooth continuation with full context restoration.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
### Universal Rules:
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS treat this as collaborative discovery between PM peers
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a product-focused PM facilitator collaborating with an expert peer
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ Resume workflow from exact point where it was interrupted
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 💬 FOCUS on understanding where we left off and continuing appropriately
|
||||
- 🚪 RESUME workflow from exact point where it was interrupted
|
||||
- 🚫 FORBIDDEN to modify content completed in previous steps
|
||||
- 📖 Only reload documents that were already tracked in `inputDocuments`
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis of current state before taking action
|
||||
- 💾 Keep existing frontmatter `stepsCompleted` values
|
||||
- 📖 Only load documents that were already tracked in `inputDocuments`
|
||||
- 🚫 FORBIDDEN to modify content completed in previous steps
|
||||
- 🚫 FORBIDDEN to discover new input documents during continuation
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
||||
- Current document and frontmatter are already loaded
|
||||
- Previous context = complete document + existing frontmatter
|
||||
- Input documents listed in frontmatter were already processed
|
||||
- Last completed step = `lastStep` value from frontmatter
|
||||
- Available context: Current document and frontmatter are already loaded
|
||||
- Focus: Workflow state analysis and continuation logic only
|
||||
- Limits: Don't assume knowledge beyond what's in the document
|
||||
- Dependencies: Existing workflow state from previous session
|
||||
|
||||
## YOUR TASK:
|
||||
|
||||
Resume the PRD workflow from where it was left off, ensuring smooth continuation.
|
||||
|
||||
## CONTINUATION SEQUENCE:
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
### 1. Analyze Current State
|
||||
|
||||
**State Assessment:**
|
||||
Review the frontmatter to understand:
|
||||
|
||||
- `stepsCompleted`: Which steps are already done
|
||||
- `lastStep`: The most recently completed step number
|
||||
- `inputDocuments`: What context was already loaded
|
||||
- `documentCounts`: briefs, research, brainstorming, projectDocs counts
|
||||
- All other frontmatter variables
|
||||
|
||||
### 2. Load All Input Documents
|
||||
### 2. Restore Context Documents
|
||||
|
||||
Reload the context documents listed in `inputDocuments`:
|
||||
**Context Reloading:**
|
||||
|
||||
- For each document in `inputDocuments`, load the complete file
|
||||
- This ensures you have full context for continuation
|
||||
- Don't discover new documents - only reload what was previously processed
|
||||
|
||||
### 3. Summarize Current Progress
|
||||
### 3. Present Current Progress
|
||||
|
||||
Welcome the user back and provide context:
|
||||
**Progress Report to User:**
|
||||
"Welcome back {{user_name}}! I'm resuming our PRD collaboration for {{project_name}}.
|
||||
|
||||
**Current Progress:**
|
||||
|
|
@ -66,47 +91,29 @@ Welcome the user back and provide context:
|
|||
|
||||
Does this look right, or do you want to make any adjustments before we proceed?"
|
||||
|
||||
### 4. Determine Next Step
|
||||
### 4. Determine Continuation Path
|
||||
|
||||
**Next Step Logic:**
|
||||
Based on `lastStep` value, determine which step to load next:
|
||||
|
||||
- If `lastStep = 1` → Load `./step-02-discovery.md`
|
||||
- If `lastStep = 2` → Load `./step-03-success.md`
|
||||
- If `lastStep = 3` → Load `./step-04-journeys.md`
|
||||
- Continue this pattern for all steps
|
||||
- If `lastStep = 10` → Workflow already complete
|
||||
- If `lastStep = 4` → Load `./step-05-domain.md`
|
||||
- If `lastStep = 5` → Load `./step-06-innovation.md`
|
||||
- If `lastStep = 6` → Load `./step-07-project-type.md`
|
||||
- If `lastStep = 7` → Load `./step-08-scoping.md`
|
||||
- If `lastStep = 8` → Load `./step-09-functional.md`
|
||||
- If `lastStep = 9` → Load `./step-10-nonfunctional.md`
|
||||
- If `lastStep = 10` → Load `./step-11-complete.md`
|
||||
- If `lastStep = 11` → Workflow already complete
|
||||
|
||||
### 5. Present Continuation Options
|
||||
### 5. Handle Workflow Completion
|
||||
|
||||
After presenting current progress, ask:
|
||||
"Ready to continue with Step {nextStepNumber}: {nextStepTitle}?
|
||||
|
||||
[C] Continue to Step {nextStepNumber}"
|
||||
|
||||
## SUCCESS METRICS:
|
||||
|
||||
✅ All previous input documents successfully reloaded
|
||||
✅ Current workflow state accurately analyzed and presented
|
||||
✅ User confirms understanding of progress
|
||||
✅ Correct next step identified and prepared for loading
|
||||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Discovering new input documents instead of reloading existing ones
|
||||
❌ Modifying content from already completed steps
|
||||
❌ Loading wrong next step based on `lastStep` value
|
||||
❌ Proceeding without user confirmation of current state
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
|
||||
## WORKFLOW ALREADY COMPLETE?
|
||||
|
||||
If `lastStep = 10` (final step completed):
|
||||
**If workflow already complete (`lastStep = 11`):**
|
||||
"Great news! It looks like we've already completed the PRD workflow for {{project_name}}.
|
||||
|
||||
The final document is ready at {output_folder}/prd.md with all sections completed through step 10.
|
||||
The final document is ready at `{outputFile}` with all sections completed through step 11.
|
||||
|
||||
Would you like me to:
|
||||
|
||||
|
|
@ -116,8 +123,43 @@ Would you like me to:
|
|||
|
||||
What would be most helpful?"
|
||||
|
||||
## NEXT STEP:
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
After user confirms they're ready to continue, load the appropriate next step file based on the `lastStep` value from frontmatter.
|
||||
**If workflow not complete:**
|
||||
Display: "Ready to continue with Step {nextStepNumber}?
|
||||
|
||||
Remember: Do NOT load the next step until user explicitly selects [C] to continue!
|
||||
**Select an Option:** [C] Continue to next step"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C: Load, read entire file, then execute the appropriate next step file based on `lastStep`
|
||||
- IF Any other comments or queries: respond and redisplay menu
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY proceed to next step when user selects 'C'
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [current state confirmed], will you then load and read fully the appropriate next step file to resume the workflow.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All previous input documents successfully reloaded
|
||||
- Current workflow state accurately analyzed and presented
|
||||
- User confirms understanding of progress before continuation
|
||||
- Correct next step identified and prepared for loading
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Discovering new input documents instead of reloading existing ones
|
||||
- Modifying content from already completed steps
|
||||
- Loading wrong next step based on `lastStep` value
|
||||
- Proceeding without user confirmation of current state
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
|
|
|||
|
|
@ -1,16 +1,53 @@
|
|||
---
|
||||
name: 'step-02-discovery'
|
||||
description: 'Conduct project and domain discovery with data-driven classification'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-02-discovery.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-03-success.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Data Files
|
||||
projectTypesCSV: '{workflow_path}/project-types.csv'
|
||||
domainComplexityCSV: '{workflow_path}/domain-complexity.csv'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 2: Project & Domain Discovery
|
||||
|
||||
**Progress: Step 2 of 10** - Next: Success Criteria Definition
|
||||
**Progress: Step 2 of 11** - Next: Success Criteria Definition
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Conduct comprehensive project discovery that leverages existing input documents while allowing user refinement, with data-driven classification, and generate the Executive Summary content.
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
- 🛑 NEVER generate content without user input
|
||||
### Universal Rules:
|
||||
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete decisions
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
- ✅ ALWAYS treat this as collaborative discovery between PM peers
|
||||
- 🛑 NEVER generate content without user input
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure entire file is read
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- 💬 FOCUS on project classification and vision alignment only
|
||||
|
||||
### Role Reinforcement:
|
||||
|
||||
- ✅ You are a product-focused PM facilitator collaborating with an expert peer
|
||||
- ✅ We engage in collaborative dialogue, not command-response
|
||||
- ✅ You bring structured thinking and facilitation skills, while the user brings domain expertise and product vision
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Focus on project classification and vision alignment only
|
||||
- 🚫 FORBIDDEN to generate content without real user input
|
||||
- 💬 APPROACH: Adapt questions based on document context (brownfield vs greenfield)
|
||||
- 🎯 LOAD classification data BEFORE starting discovery conversation
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
|
@ -31,8 +68,8 @@ This step will generate content and present choices:
|
|||
|
||||
## PROTOCOL INTEGRATION:
|
||||
|
||||
- When 'A' selected: Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml
|
||||
- When 'P' selected: Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md
|
||||
- When 'A' selected: Execute {advancedElicitationTask}
|
||||
- When 'P' selected: Execute {partyModeWorkflow}
|
||||
- PROTOCOLS always return to this step's A/P/C menu
|
||||
- User accepts/rejects protocol changes before proceeding
|
||||
|
||||
|
|
@ -40,40 +77,56 @@ This step will generate content and present choices:
|
|||
|
||||
- Current document and frontmatter from step 1 are available
|
||||
- Input documents already loaded are in memory (product briefs, research, brainstorming, project docs)
|
||||
- **Document counts available in frontmatter `documentCounts`**
|
||||
- Classification CSV data will be loaded in this step only
|
||||
- This will be the first content section appended to the document
|
||||
- LEVERAGE existing input documents to accelerate discovery process
|
||||
- installed_path = `{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd`
|
||||
|
||||
## YOUR TASK:
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
|
||||
Conduct comprehensive project discovery that leverages existing input documents while allowing user refinement, with data-driven classification and generate the first content section.
|
||||
### 1. Read Document State from Frontmatter
|
||||
|
||||
## DISCOVERY SEQUENCE:
|
||||
**CRITICAL FIRST ACTION:** Read the frontmatter from `{outputFile}` to get document counts.
|
||||
|
||||
### 1. Load Classification Data
|
||||
```
|
||||
Read documentCounts from prd.md frontmatter:
|
||||
- briefCount = documentCounts.briefs
|
||||
- researchCount = documentCounts.research
|
||||
- brainstormingCount = documentCounts.brainstorming
|
||||
- projectDocsCount = documentCounts.projectDocs
|
||||
```
|
||||
|
||||
**ANNOUNCE your understanding:**
|
||||
|
||||
"From step 1, I have loaded:
|
||||
|
||||
- Product briefs: {{briefCount}} files
|
||||
- Research: {{researchCount}} files
|
||||
- Brainstorming: {{brainstormingCount}} files
|
||||
- Project docs: {{projectDocsCount}} files
|
||||
|
||||
{if projectDocsCount > 0}This is a **brownfield project** - I'll focus on understanding what you want to add or change.{else}This is a **greenfield project** - I'll help you define the full product vision.{/if}"
|
||||
|
||||
### 2. Load Classification Data
|
||||
|
||||
Load and prepare CSV data for intelligent classification:
|
||||
|
||||
- Load `{installed_path}/project-types.csv` completely
|
||||
- Load `{installed_path/domain-complexity.csv` completely
|
||||
- Load `{projectTypesCSV}` completely
|
||||
- Load `{domainComplexityCSV}` completely
|
||||
- Parse column structures and store in memory for this step only
|
||||
|
||||
### 2. Leverage Input Documents for Head Start
|
||||
### 3. Begin Discovery Conversation
|
||||
|
||||
Analyze available input documents to provide informed discovery:
|
||||
**SELECT EXACTLY ONE DISCOVERY PATH based on document state:**
|
||||
|
||||
**Check Input Documents Available:**
|
||||
---
|
||||
|
||||
- Product Briefs: {{number_of_briefs}} documents loaded
|
||||
- Research Documents: {{number_of_research}} documents loaded
|
||||
- Brainstorming Results: {{number_of_brainstorming}} documents loaded
|
||||
- Project Documentation: {{number_of_project_docs}} documents loaded
|
||||
#### PATH A: Has Product Brief (briefCount > 0)
|
||||
|
||||
**If Input Documents Exist:**
|
||||
"As your PM peer, I've reviewed your existing project documentation and have a great starting point for our discovery. Let me share what I understand and you can refine or correct as needed.
|
||||
**Use this path when:** `briefCount > 0`
|
||||
|
||||
**Based on your product brief and research:**
|
||||
"As your PM peer, I've reviewed your product brief and have a great starting point for our discovery. Let me share what I understand and you can refine or correct as needed.
|
||||
|
||||
**Based on your product brief:**
|
||||
|
||||
**What you're building:**
|
||||
{{extracted_vision_from_brief}}
|
||||
|
|
@ -87,9 +140,47 @@ Analyze available input documents to provide informed discovery:
|
|||
**What makes it special:**
|
||||
{{extracted_differentiator_from_brief}}
|
||||
|
||||
{if projectDocsCount > 0}I also see you have existing project documentation. This PRD will define how new features integrate with your existing system architecture.{/if}
|
||||
|
||||
**How does this align with your vision?** Should we refine any of these points or are there important aspects I'm missing?"
|
||||
|
||||
**If No Input Documents:**
|
||||
**AFTER this message, SKIP to Section 4.**
|
||||
|
||||
---
|
||||
|
||||
#### PATH B: No Brief but Has Project Docs - Brownfield (briefCount == 0 AND projectDocsCount > 0)
|
||||
|
||||
**Use this path when:** `briefCount == 0 AND projectDocsCount > 0`
|
||||
|
||||
**NOTE:** Extract the following from loaded project documentation (index.md, architecture.md, project-overview.md, etc.):
|
||||
|
||||
"As your PM peer, I've reviewed your existing project documentation from document-project.
|
||||
|
||||
**Your existing system includes:**
|
||||
|
||||
- **Tech Stack:** {analyze index.md and architecture.md for technologies used}
|
||||
- **Architecture:** {summarize architecture patterns from architecture.md}
|
||||
- **Key Components:** {list main components from source-tree-analysis.md or project-overview.md}
|
||||
|
||||
This PRD will define **new features or changes** to add to this existing codebase.
|
||||
|
||||
**Tell me about what you want to add or change:**
|
||||
|
||||
- What new capability or feature do you want to build?
|
||||
- What problem will this solve for your users?
|
||||
- How should it integrate with the existing system?
|
||||
- Is this adding new functionality, improving existing features, or fixing issues?
|
||||
|
||||
I'll help you create a PRD focused on these additions while respecting your existing patterns and architecture."
|
||||
|
||||
**AFTER this message, SKIP to Section 4.**
|
||||
|
||||
---
|
||||
|
||||
#### PATH C: No Documents - Greenfield (briefCount == 0 AND projectDocsCount == 0)
|
||||
|
||||
**Use this path when:** `briefCount == 0 AND projectDocsCount == 0`
|
||||
|
||||
"As your PM peer, I'm excited to help you shape {{project_name}}. Let me start by understanding what you want to build.
|
||||
|
||||
**Tell me about what you want to create:**
|
||||
|
|
@ -100,9 +191,13 @@ Analyze available input documents to provide informed discovery:
|
|||
|
||||
I'll be listening for signals to help us classify the project and domain so we can ask the right questions throughout our process."
|
||||
|
||||
### 3. Listen for Classification Signals
|
||||
**AFTER this message, continue to Section 4.**
|
||||
|
||||
As the user describes their product, listen for and match against:
|
||||
---
|
||||
|
||||
### 4. Listen for Classification Signals
|
||||
|
||||
As the user describes their product/feature, listen for and match against:
|
||||
|
||||
#### Project Type Signals
|
||||
|
||||
|
|
@ -122,11 +217,14 @@ Compare user description against `signals` from `domain-complexity.csv`:
|
|||
- Examples: "payment,banking,trading" → fintech
|
||||
- Store the matched `domain` and `complexity_level`
|
||||
|
||||
### 4. Enhanced Classification with Document Context
|
||||
### 5. Present Classification for Validation
|
||||
|
||||
Leverage both user input and document analysis for classification:
|
||||
**SELECT EXACTLY ONE CLASSIFICATION PRESENTATION based on document state:**
|
||||
|
||||
---
|
||||
|
||||
#### IF PATH A was used (briefCount > 0):
|
||||
|
||||
**If Input Documents Exist:**
|
||||
"Based on your product brief and our discussion, I'm classifying this as:
|
||||
|
||||
- **Project Type:** {project_type_from_brief_or_conversation}
|
||||
|
|
@ -136,10 +234,33 @@ Leverage both user input and document analysis for classification:
|
|||
From your brief, I detected these classification signals:
|
||||
{{classification_signals_from_brief}}
|
||||
|
||||
{if projectDocsCount > 0}Your existing project documentation also indicates:
|
||||
|
||||
- **Existing Tech Stack:** {from architecture.md or index.md}
|
||||
- **Architecture Pattern:** {from architecture.md}
|
||||
|
||||
I'll ensure the new features align with your existing system.{/if}
|
||||
|
||||
Combined with our conversation, this suggests the above classification. Does this sound right?"
|
||||
|
||||
**If No Input Documents:**
|
||||
Present your classifications for user validation:
|
||||
---
|
||||
|
||||
#### IF PATH B was used (briefCount == 0 AND projectDocsCount > 0):
|
||||
|
||||
"Based on your existing project documentation and our discussion about new features:
|
||||
|
||||
- **Existing Project Type:** {detected from project docs - e.g., web_app, api_backend}
|
||||
- **Tech Stack:** {from architecture.md or index.md}
|
||||
- **New Feature Type:** {from user's description of what they want to add}
|
||||
- **Domain:** {detected_domain}
|
||||
- **Complexity:** {complexity_level}
|
||||
|
||||
I'll ensure the PRD aligns with your existing architecture patterns. Does this classification sound right?"
|
||||
|
||||
---
|
||||
|
||||
#### IF PATH C was used (briefCount == 0 AND projectDocsCount == 0):
|
||||
|
||||
"Based on our conversation, I'm hearing this as:
|
||||
|
||||
- **Project Type:** {detected_project_type}
|
||||
|
|
@ -148,11 +269,16 @@ Present your classifications for user validation:
|
|||
|
||||
Does this sound right to you? I want to make sure we're on the same page before diving deeper."
|
||||
|
||||
### 5. Identify What Makes It Special
|
||||
---
|
||||
|
||||
Leverage input documents for initial understanding, then refine:
|
||||
### 6. Identify What Makes It Special
|
||||
|
||||
**SELECT EXACTLY ONE DIFFERENTIATOR DISCOVERY based on document state:**
|
||||
|
||||
---
|
||||
|
||||
#### IF PATH A was used (briefCount > 0):
|
||||
|
||||
**If Input Documents Exist:**
|
||||
"From your product brief, I understand that what makes this special is:
|
||||
{{extracted_differentiator_from_brief}}
|
||||
|
||||
|
|
@ -162,7 +288,21 @@ Let's explore this deeper:
|
|||
- **Missing aspects:** Are there other differentiators that aren't captured in your brief?
|
||||
- **Evolution:** How has your thinking on this evolved since you wrote the brief?"
|
||||
|
||||
**If No Input Documents:**
|
||||
---
|
||||
|
||||
#### IF PATH B was used (briefCount == 0 AND projectDocsCount > 0):
|
||||
|
||||
"Your existing system already provides certain capabilities. Now let's define what makes these **new additions** special:
|
||||
|
||||
- What gap in your current system will this fill?
|
||||
- How will this improve the experience for your existing users?
|
||||
- What's the key insight that led you to prioritize this addition?
|
||||
- What would make users say 'finally, this is what we needed'?"
|
||||
|
||||
---
|
||||
|
||||
#### IF PATH C was used (briefCount == 0 AND projectDocsCount == 0):
|
||||
|
||||
Ask focused questions to capture the product's unique value:
|
||||
|
||||
- "What would make users say 'this is exactly what I needed'?"
|
||||
|
|
@ -170,7 +310,9 @@ Ask focused questions to capture the product's unique value:
|
|||
- "What assumption about [problem space] are you challenging?"
|
||||
- "If this succeeds wildly, what changed for your users?"
|
||||
|
||||
### 6. Generate Executive Summary Content
|
||||
---
|
||||
|
||||
### 7. Generate Executive Summary Content
|
||||
|
||||
Based on the conversation, prepare the content to append to the document:
|
||||
|
||||
|
|
@ -190,75 +332,84 @@ Based on the conversation, prepare the content to append to the document:
|
|||
**Technical Type:** {project_type}
|
||||
**Domain:** {domain}
|
||||
**Complexity:** {complexity_level}
|
||||
{if projectDocsCount > 0}**Project Context:** Brownfield - extending existing system{else}**Project Context:** Greenfield - new project{/if}
|
||||
|
||||
{project_classification_content}
|
||||
```
|
||||
|
||||
### 7. Present Content and Menu
|
||||
### 8. Present Content and Menu
|
||||
|
||||
Show the generated content to the user and present:
|
||||
|
||||
"I've drafted our Executive Summary based on our conversation. This will be the first section of your PRD.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
[Show the complete markdown content from step 7]
|
||||
|
||||
**What would you like to do?**
|
||||
**Select an Option:**
|
||||
[A] Advanced Elicitation - Let's dive deeper and refine this content
|
||||
[P] Party Mode - Bring in different perspectives to improve this
|
||||
[C] Continue - Save this and move to Success Criteria Definition (Step 3 of 10)"
|
||||
[C] Continue - Save this and move to Success Criteria Definition (Step 3 of 11)"
|
||||
|
||||
### 8. Handle Menu Selection
|
||||
### 9. Handle Menu Selection
|
||||
|
||||
#### If 'A' (Advanced Elicitation):
|
||||
#### IF A (Advanced Elicitation):
|
||||
|
||||
- Execute {project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml with the current content
|
||||
- Execute {advancedElicitationTask} with the current content
|
||||
- Process the enhanced content that comes back
|
||||
- Ask user: "Accept these changes to the Executive Summary? (y/n)"
|
||||
- If yes: Update the content with improvements, then return to A/P/C menu
|
||||
- If no: Keep original content, then return to A/P/C menu
|
||||
|
||||
#### If 'P' (Party Mode):
|
||||
#### IF P (Party Mode):
|
||||
|
||||
- Execute {project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md with the current content
|
||||
- Execute {partyModeWorkflow} with the current content
|
||||
- Process the collaborative improvements that come back
|
||||
- Ask user: "Accept these changes to the Executive Summary? (y/n)"
|
||||
- If yes: Update the content with improvements, then return to A/P/C menu
|
||||
- If no: Keep original content, then return to A/P/C menu
|
||||
|
||||
#### If 'C' (Continue):
|
||||
#### IF C (Continue):
|
||||
|
||||
- Append the final content to `{output_folder}/prd.md`
|
||||
- Append the final content to `{outputFile}`
|
||||
- Update frontmatter: `stepsCompleted: [1, 2]`
|
||||
- Load `./step-03-success.md`
|
||||
- Load `{nextStepFile}`
|
||||
|
||||
## APPEND TO DOCUMENT:
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
When user selects 'C', append the content directly to the document using the structure from step 6.
|
||||
ONLY WHEN [C continue option] is selected and [executive summary content finalized and saved to document with frontmatter updated], will you then load and read fully `{nextStepFile}` to execute and begin success criteria definition.
|
||||
|
||||
## SUCCESS METRICS:
|
||||
---
|
||||
|
||||
✅ Classification data loaded and used effectively
|
||||
✅ Input documents analyzed and leveraged for head start
|
||||
✅ User classifications validated and confirmed
|
||||
✅ Product differentiator clearly identified and refined
|
||||
✅ Executive summary content generated collaboratively with document context
|
||||
✅ A/P/C menu presented and handled correctly
|
||||
✅ Content properly appended to document when C selected
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
## FAILURE MODES:
|
||||
### ✅ SUCCESS:
|
||||
|
||||
❌ Skipping classification data loading and guessing classifications
|
||||
❌ Not leveraging existing input documents to accelerate discovery
|
||||
❌ Not validating classifications with user before proceeding
|
||||
❌ Generating executive summary without real user input
|
||||
❌ Missing the "what makes it special" discovery and refinement
|
||||
❌ Not presenting A/P/C menu after content generation
|
||||
❌ Appending content without user selecting 'C'
|
||||
- Document counts read from frontmatter and announced
|
||||
- Classification data loaded and used effectively
|
||||
- **Correct discovery path selected based on document counts**
|
||||
- Input documents analyzed and leveraged for head start
|
||||
- User classifications validated and confirmed
|
||||
- Product differentiator clearly identified and refined
|
||||
- Executive summary content generated collaboratively with document context
|
||||
- A/P/C menu presented and handled correctly
|
||||
- Content properly appended to document when C selected
|
||||
- Frontmatter updated with stepsCompleted: [1, 2]
|
||||
|
||||
❌ **CRITICAL**: Reading only partial step file - leads to incomplete understanding and poor decisions
|
||||
❌ **CRITICAL**: Proceeding with 'C' without fully reading and understanding the next step file
|
||||
❌ **CRITICAL**: Making decisions without complete understanding of step requirements and protocols
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- **Not reading documentCounts from frontmatter first**
|
||||
- **Executing multiple discovery paths instead of exactly one**
|
||||
- Skipping classification data loading and guessing classifications
|
||||
- Not leveraging existing input documents to accelerate discovery
|
||||
- Not validating classifications with user before proceeding
|
||||
- Generating executive summary without real user input
|
||||
- Missing the "what makes it special" discovery and refinement
|
||||
- Not presenting A/P/C menu after content generation
|
||||
- Appending content without user selecting 'C'
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
|
||||
## COMPLEXITY HANDLING:
|
||||
|
||||
|
|
@ -267,9 +418,3 @@ If `complexity_level = "high"`:
|
|||
- Note the `suggested_workflow` and `web_searches` from domain CSV
|
||||
- Consider mentioning domain research needs in classification section
|
||||
- Document complexity implications in project classification
|
||||
|
||||
## NEXT STEP:
|
||||
|
||||
After user selects 'C' and content is saved to document, load `installed_path/steps/step-03-success.md` to define success criteria.
|
||||
|
||||
Remember: Do NOT proceed to step-03 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
||||
|
|
|
|||
|
|
@ -1,6 +1,24 @@
|
|||
---
|
||||
name: 'step-03-success'
|
||||
description: 'Define comprehensive success criteria covering user, business, and technical success'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-03-success.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-04-journeys.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 3: Success Criteria Definition
|
||||
|
||||
**Progress: Step 3 of 10** - Next: User Journey Mapping
|
||||
**Progress: Step 3 of 11** - Next: User Journey Mapping
|
||||
|
||||
## MANDATORY EXECUTION RULES (READ FIRST):
|
||||
|
||||
|
|
@ -204,7 +222,7 @@ Show the generated content and present choices:
|
|||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's dive deeper and refine these success metrics
|
||||
[P] Party Mode - Bring in different perspectives on success criteria
|
||||
[C] Continue - Save success criteria and move to User Journey Mapping (Step 4 of 10)"
|
||||
[C] Continue - Save success criteria and move to User Journey Mapping (Step 4 of 11)"
|
||||
|
||||
### 9. Handle Menu Selection
|
||||
|
||||
|
|
|
|||
|
|
@ -1,3 +1,21 @@
|
|||
---
|
||||
name: 'step-04-journeys'
|
||||
description: 'Map ALL user types that interact with the system with narrative story-based journeys'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-04-journeys.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-05-domain.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 4: User Journey Mapping
|
||||
|
||||
**Progress: Step 4 of 11** - Next: Domain Requirements
|
||||
|
|
|
|||
|
|
@ -1,3 +1,24 @@
|
|||
---
|
||||
name: 'step-05-domain'
|
||||
description: 'Explore domain-specific requirements for complex domains (optional step)'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-05-domain.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-06-innovation.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Data Files
|
||||
domainComplexityCSV: '{workflow_path}/domain-complexity.csv'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 5: Domain-Specific Exploration
|
||||
|
||||
**Progress: Step 5 of 11** - Next: Innovation Focus
|
||||
|
|
|
|||
|
|
@ -1,3 +1,24 @@
|
|||
---
|
||||
name: 'step-06-innovation'
|
||||
description: 'Detect and explore innovative aspects of the product (optional step)'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-06-innovation.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-07-project-type.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Data Files
|
||||
projectTypesCSV: '{workflow_path}/project-types.csv'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 6: Innovation Discovery
|
||||
|
||||
**Progress: Step 6 of 11** - Next: Project Type Analysis
|
||||
|
|
|
|||
|
|
@ -1,3 +1,24 @@
|
|||
---
|
||||
name: 'step-07-project-type'
|
||||
description: 'Conduct project-type specific discovery using CSV-driven guidance'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-07-project-type.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-08-scoping.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Data Files
|
||||
projectTypesCSV: '{workflow_path}/project-types.csv'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 7: Project-Type Deep Dive
|
||||
|
||||
**Progress: Step 7 of 11** - Next: Scoping
|
||||
|
|
|
|||
|
|
@ -1,3 +1,21 @@
|
|||
---
|
||||
name: 'step-08-scoping'
|
||||
description: 'Define MVP boundaries and prioritize features across development phases'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-08-scoping.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-09-functional.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 8: Scoping Exercise - MVP & Future Features
|
||||
|
||||
**Progress: Step 8 of 11** - Next: Functional Requirements
|
||||
|
|
|
|||
|
|
@ -1,3 +1,21 @@
|
|||
---
|
||||
name: 'step-09-functional'
|
||||
description: 'Synthesize all discovery into comprehensive functional requirements'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-09-functional.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 9: Functional Requirements Synthesis
|
||||
|
||||
**Progress: Step 9 of 11** - Next: Non-Functional Requirements
|
||||
|
|
|
|||
|
|
@ -1,3 +1,21 @@
|
|||
---
|
||||
name: 'step-10-nonfunctional'
|
||||
description: 'Define quality attributes that matter for this specific product'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-10-nonfunctional.md'
|
||||
nextStepFile: '{workflow_path}/steps/step-11-complete.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
|
||||
# Task References
|
||||
advancedElicitationTask: '{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml'
|
||||
partyModeWorkflow: '{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Step 10: Non-Functional Requirements
|
||||
|
||||
**Progress: Step 10 of 11** - Next: Complete PRD
|
||||
|
|
|
|||
|
|
@ -1,3 +1,16 @@
|
|||
---
|
||||
name: 'step-11-complete'
|
||||
description: 'Complete the PRD workflow, update status files, and suggest next steps'
|
||||
|
||||
# Path Definitions
|
||||
workflow_path: '{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd'
|
||||
|
||||
# File References
|
||||
thisStepFile: '{workflow_path}/steps/step-11-complete.md'
|
||||
workflowFile: '{workflow_path}/workflow.md'
|
||||
outputFile: '{output_folder}/prd.md'
|
||||
---
|
||||
|
||||
# Step 11: Workflow Completion
|
||||
|
||||
**Final Step - Complete the PRD**
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@
|
|||
- ✅ ALWAYS treat this as collaborative discovery between architectural peers
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- 💬 FOCUS on evaluating starter template options with current versions
|
||||
- 🌐 ALWAYS verify current versions using WebSearch - NEVER trust hardcoded versions
|
||||
- 🌐 ALWAYS search the web to verify current versions - NEVER trust hardcoded versions
|
||||
- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
|
||||
- 📖 CRITICAL: ALWAYS read the complete step file before taking any action - partial understanding leads to incomplete architecture
|
||||
- 🔄 CRITICAL: When loading next step with 'C', ensure the entire file is read and understood before proceeding
|
||||
|
|
@ -14,7 +14,7 @@
|
|||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- 🌐 Use WebSearch to verify current versions and options
|
||||
- 🌐 Search the web to verify current versions and options
|
||||
- ⚠️ Present A/P/C menu after generating starter template analysis
|
||||
- 💾 ONLY save when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3]` before loading next step
|
||||
|
|
@ -118,12 +118,12 @@ If UX specification was loaded, consider UX requirements when selecting starter:
|
|||
|
||||
### 3. Research Current Starter Options
|
||||
|
||||
Use WebSearch to find current, maintained starter templates:
|
||||
Search the web to find current, maintained starter templates:
|
||||
|
||||
```
|
||||
WebSearch: {{primary_technology}} starter template CLI create command latest 2024
|
||||
WebSearch: {{primary_technology}} boilerplate generator latest options 2024
|
||||
WebSearch: {{primary_technology}} production-ready starter best practices 2024
|
||||
Search the web: "{{primary_technology}} starter template CLI create command latest"
|
||||
Search the web: "{{primary_technology}} boilerplate generator latest options"
|
||||
Search the web: "{{primary_technology}} production-ready starter best practices"
|
||||
```
|
||||
|
||||
### 4. Investigate Top Starter Options
|
||||
|
|
@ -131,10 +131,10 @@ WebSearch: {{primary_technology}} production-ready starter best practices 2024
|
|||
For each promising starter found, investigate details:
|
||||
|
||||
```
|
||||
WebSearch: {{starter_name}} default setup technologies included latest
|
||||
WebSearch: {{starter_name}} project structure file organization
|
||||
WebSearch: {{starter_name}} production deployment capabilities
|
||||
WebSearch: {{starter_name}} recent updates maintenance status 2024
|
||||
Search the web: "{{starter_name}} default setup technologies included latest"
|
||||
Search the web: "{{starter_name}} project structure file organization"
|
||||
Search the web: "{{starter_name}} production deployment capabilities"
|
||||
Search the web: "{{starter_name}} recent updates maintenance status"
|
||||
```
|
||||
|
||||
### 5. Analyze What Each Starter Provides
|
||||
|
|
@ -200,8 +200,8 @@ This is a great starting point that follows best practices and saves us from mak
|
|||
If user shows interest in a starter, get the exact current commands:
|
||||
|
||||
```
|
||||
WebSearch: {{starter_name}} CLI command options flags latest 2024
|
||||
WebSearch: {{starter_name}} create new project command examples
|
||||
Search the web: "{{starter_name}} CLI command options flags latest"
|
||||
Search the web: "{{starter_name}} create new project command examples"
|
||||
```
|
||||
|
||||
### 8. Generate Starter Template Content
|
||||
|
|
@ -304,7 +304,7 @@ When user selects 'C', append the content directly to the document using the str
|
|||
|
||||
✅ Primary technology domain correctly identified from project context
|
||||
✅ Current, maintained starter templates researched and evaluated
|
||||
✅ All versions verified using WebSearch, not hardcoded
|
||||
✅ All versions verified using web search, not hardcoded
|
||||
✅ Architectural implications of starter choice clearly documented
|
||||
✅ User provided with clear rationale for starter selection
|
||||
✅ A/P/C menu presented and handled correctly
|
||||
|
|
@ -312,7 +312,7 @@ When user selects 'C', append the content directly to the document using the str
|
|||
|
||||
## FAILURE MODES:
|
||||
|
||||
❌ Not verifying current versions with WebSearch
|
||||
❌ Not verifying current versions with web search
|
||||
❌ Ignoring UX requirements when evaluating starters
|
||||
❌ Not documenting what architectural decisions the starter makes
|
||||
❌ Failing to consider maintenance status of starter templates
|
||||
|
|
|
|||
|
|
@ -9,13 +9,13 @@
|
|||
- ✅ ALWAYS treat this as collaborative discovery between architectural peers
|
||||
- 📋 YOU ARE A FACILITATOR, not a content generator
|
||||
- 💬 FOCUS on making critical architectural decisions collaboratively
|
||||
- 🌐 ALWAYS verify current technology versions using WebSearch
|
||||
- 🌐 ALWAYS search the web to verify current technology versions
|
||||
- ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Show your analysis before taking any action
|
||||
- 🌐 Use WebSearch to verify technology versions and options
|
||||
- 🌐 Search the web to verify technology versions and options
|
||||
- ⚠️ Present A/P/C menu after each major decision category
|
||||
- 💾 ONLY save when user chooses C (Continue)
|
||||
- 📖 Update frontmatter `stepsCompleted: [1, 2, 3, 4]` before loading next step
|
||||
|
|
@ -163,9 +163,9 @@ What feels right to you?"
|
|||
If decision involves specific technology:
|
||||
|
||||
```
|
||||
WebSearch: {{technology}} latest stable version 2024
|
||||
WebSearch: {{technology}} current LTS version
|
||||
WebSearch: {{technology}} production readiness 2024
|
||||
Search the web: "{{technology}} latest stable version"
|
||||
Search the web: "{{technology}} current LTS version"
|
||||
Search the web: "{{technology}} production readiness"
|
||||
```
|
||||
|
||||
**Get User Input:**
|
||||
|
|
@ -290,7 +290,7 @@ When user selects 'C', append the content directly to the document using the str
|
|||
## SUCCESS METRICS:
|
||||
|
||||
✅ All critical architectural decisions made collaboratively
|
||||
✅ Technology versions verified using WebSearch
|
||||
✅ Technology versions verified using web search
|
||||
✅ Decision rationale clearly documented
|
||||
✅ Cascading implications identified and addressed
|
||||
✅ User provided appropriate level of explanation for skill level
|
||||
|
|
@ -300,7 +300,7 @@ When user selects 'C', append the content directly to the document using the str
|
|||
## FAILURE MODES:
|
||||
|
||||
❌ Making recommendations instead of facilitating decisions
|
||||
❌ Not verifying technology versions with WebSearch
|
||||
❌ Not verifying technology versions with web search
|
||||
❌ Missing cascading implications between decisions
|
||||
❌ Not adapting explanations to user skill level
|
||||
❌ Forgetting to document decisions made by starter template
|
||||
|
|
|
|||
|
|
@ -196,7 +196,7 @@ Your choice [1/2/3]:
|
|||
|
||||
- Mode: {{workflow_mode}}
|
||||
- Scan Level: {{scan_level}}
|
||||
- Output: {output_folder}/bmm-index.md and related files
|
||||
- Output: {output_folder}/index.md and related files
|
||||
|
||||
{{#if status_file_found}}
|
||||
**Status Updated:**
|
||||
|
|
|
|||
|
|
@ -28,9 +28,8 @@ module.exports = {
|
|||
command: 'build [agent]',
|
||||
description: 'Build agent XML files from YAML sources',
|
||||
options: [
|
||||
['-a, --all', 'Rebuild all agents'],
|
||||
['-a, --all', 'Build all agents'],
|
||||
['-d, --directory <path>', 'Project directory', '.'],
|
||||
['--force', 'Force rebuild even if up to date'],
|
||||
],
|
||||
action: async (agentName, options) => {
|
||||
try {
|
||||
|
|
@ -54,13 +53,15 @@ module.exports = {
|
|||
|
||||
if (options.all) {
|
||||
// Build all agents
|
||||
await buildAllAgents(projectDir, options.force);
|
||||
await buildAllAgents(projectDir);
|
||||
} else if (agentName) {
|
||||
// Build specific agent
|
||||
await buildAgent(projectDir, agentName, options.force);
|
||||
await buildAgent(projectDir, agentName);
|
||||
} else {
|
||||
// No agent specified, check what needs rebuilding
|
||||
await checkBuildStatus(projectDir);
|
||||
// No agent specified, list available agents
|
||||
console.log(chalk.yellow('No agent specified. Use --all to build all agents or specify an agent name.'));
|
||||
console.log(chalk.dim('\nAvailable agents:'));
|
||||
await listAvailableAgents(projectDir);
|
||||
}
|
||||
|
||||
process.exit(0);
|
||||
|
|
@ -77,7 +78,7 @@ module.exports = {
|
|||
/**
|
||||
* Build a specific agent
|
||||
*/
|
||||
async function buildAgent(projectDir, agentName, force = false) {
|
||||
async function buildAgent(projectDir, agentName) {
|
||||
// First check standalone agents in bmad/agents/{agentname}/
|
||||
const standaloneAgentDir = path.join(projectDir, 'bmad', 'agents', agentName);
|
||||
let standaloneYamlPath = path.join(standaloneAgentDir, `${agentName}.agent.yaml`);
|
||||
|
|
@ -95,15 +96,6 @@ async function buildAgent(projectDir, agentName, force = false) {
|
|||
const yamlFileName = path.basename(standaloneYamlPath, '.agent.yaml');
|
||||
const outputPath = path.join(standaloneAgentDir, `${yamlFileName}.md`);
|
||||
|
||||
// Check if rebuild needed
|
||||
if (!force && (await fs.pathExists(outputPath))) {
|
||||
const needsRebuild = await checkIfNeedsRebuild(standaloneYamlPath, outputPath, projectDir, agentName);
|
||||
if (!needsRebuild) {
|
||||
console.log(chalk.dim(` ${agentName}: already up to date`));
|
||||
return;
|
||||
}
|
||||
}
|
||||
|
||||
// Build the standalone agent
|
||||
console.log(chalk.cyan(` Building standalone agent ${agentName}...`));
|
||||
|
||||
|
|
@ -130,15 +122,6 @@ async function buildAgent(projectDir, agentName, force = false) {
|
|||
if (await fs.pathExists(agentYamlPath)) {
|
||||
found = true;
|
||||
|
||||
// Check if rebuild needed
|
||||
if (!force && (await fs.pathExists(outputPath))) {
|
||||
const needsRebuild = await checkIfNeedsRebuild(agentYamlPath, outputPath, projectDir, agentName);
|
||||
if (!needsRebuild) {
|
||||
console.log(chalk.dim(` ${agentName}: already up to date`));
|
||||
return;
|
||||
}
|
||||
}
|
||||
|
||||
// Build the agent
|
||||
console.log(chalk.cyan(` Building ${agentName}...`));
|
||||
|
||||
|
|
@ -162,9 +145,8 @@ async function buildAgent(projectDir, agentName, force = false) {
|
|||
/**
|
||||
* Build all agents
|
||||
*/
|
||||
async function buildAllAgents(projectDir, force = false) {
|
||||
async function buildAllAgents(projectDir) {
|
||||
let builtCount = 0;
|
||||
let skippedCount = 0;
|
||||
|
||||
// First, build standalone agents in bmad/agents/
|
||||
const standaloneAgentsDir = path.join(projectDir, 'bmad', 'agents');
|
||||
|
|
@ -193,16 +175,6 @@ async function buildAllAgents(projectDir, force = false) {
|
|||
const agentName = path.basename(agentFile, '.agent.yaml');
|
||||
const outputPath = path.join(agentDir, `${agentName}.md`);
|
||||
|
||||
// Check if rebuild needed
|
||||
if (!force && (await fs.pathExists(outputPath))) {
|
||||
const needsRebuild = await checkIfNeedsRebuild(agentYamlPath, outputPath, projectDir, agentName);
|
||||
if (!needsRebuild) {
|
||||
console.log(chalk.dim(` ${agentName}: up to date`));
|
||||
skippedCount++;
|
||||
continue;
|
||||
}
|
||||
}
|
||||
|
||||
console.log(chalk.cyan(` Building standalone agent ${agentName}...`));
|
||||
|
||||
const customizePath = path.join(projectDir, 'bmad', '_cfg', 'agents', `${agentName}.customize.yaml`);
|
||||
|
|
@ -239,16 +211,6 @@ async function buildAllAgents(projectDir, force = false) {
|
|||
const agentYamlPath = path.join(agentsDir, file);
|
||||
const outputPath = path.join(agentsDir, `${agentName}.md`);
|
||||
|
||||
// Check if rebuild needed
|
||||
if (!force && (await fs.pathExists(outputPath))) {
|
||||
const needsRebuild = await checkIfNeedsRebuild(agentYamlPath, outputPath, projectDir, agentName);
|
||||
if (!needsRebuild) {
|
||||
console.log(chalk.dim(` ${agentName}: up to date`));
|
||||
skippedCount++;
|
||||
continue;
|
||||
}
|
||||
}
|
||||
|
||||
console.log(chalk.cyan(` Building ${agentName}...`));
|
||||
|
||||
const customizePath = path.join(projectDir, '.claude', '_cfg', 'agents', `${agentName}.customize.yaml`);
|
||||
|
|
@ -263,143 +225,6 @@ async function buildAllAgents(projectDir, force = false) {
|
|||
}
|
||||
|
||||
console.log(chalk.green(`\n✓ Built ${builtCount} agent(s)`));
|
||||
if (skippedCount > 0) {
|
||||
console.log(chalk.dim(` Skipped ${skippedCount} (already up to date)`));
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* Check what needs rebuilding
|
||||
*/
|
||||
async function checkBuildStatus(projectDir) {
|
||||
const needsRebuild = [];
|
||||
const upToDate = [];
|
||||
|
||||
// Check standalone agents in bmad/agents/
|
||||
const standaloneAgentsDir = path.join(projectDir, 'bmad', 'agents');
|
||||
if (await fs.pathExists(standaloneAgentsDir)) {
|
||||
const agentDirs = await fs.readdir(standaloneAgentsDir);
|
||||
|
||||
for (const agentDirName of agentDirs) {
|
||||
const agentDir = path.join(standaloneAgentsDir, agentDirName);
|
||||
|
||||
// Skip if not a directory
|
||||
const stat = await fs.stat(agentDir);
|
||||
if (!stat.isDirectory()) {
|
||||
continue;
|
||||
}
|
||||
|
||||
// Find any .agent.yaml file in the directory
|
||||
const files = await fs.readdir(agentDir);
|
||||
const agentFile = files.find((f) => f.endsWith('.agent.yaml'));
|
||||
|
||||
if (!agentFile) {
|
||||
continue;
|
||||
}
|
||||
|
||||
const agentYamlPath = path.join(agentDir, agentFile);
|
||||
const agentName = path.basename(agentFile, '.agent.yaml');
|
||||
const outputPath = path.join(agentDir, `${agentName}.md`);
|
||||
|
||||
if (!(await fs.pathExists(outputPath))) {
|
||||
needsRebuild.push(`${agentName} (standalone)`);
|
||||
} else if (await checkIfNeedsRebuild(agentYamlPath, outputPath, projectDir, agentName)) {
|
||||
needsRebuild.push(`${agentName} (standalone)`);
|
||||
} else {
|
||||
upToDate.push(`${agentName} (standalone)`);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
// Check module agents in .claude/commands/bmad/
|
||||
const bmadCommandsDir = path.join(projectDir, '.claude', 'commands', 'bmad');
|
||||
if (await fs.pathExists(bmadCommandsDir)) {
|
||||
const modules = await fs.readdir(bmadCommandsDir);
|
||||
|
||||
for (const module of modules) {
|
||||
const agentsDir = path.join(bmadCommandsDir, module, 'agents');
|
||||
|
||||
if (!(await fs.pathExists(agentsDir))) {
|
||||
continue;
|
||||
}
|
||||
|
||||
const files = await fs.readdir(agentsDir);
|
||||
|
||||
for (const file of files) {
|
||||
if (!file.endsWith('.agent.yaml')) {
|
||||
continue;
|
||||
}
|
||||
|
||||
const agentName = file.replace('.agent.yaml', '');
|
||||
const agentYamlPath = path.join(agentsDir, file);
|
||||
const outputPath = path.join(agentsDir, `${agentName}.md`);
|
||||
|
||||
if (!(await fs.pathExists(outputPath))) {
|
||||
needsRebuild.push(`${agentName} (${module})`);
|
||||
} else if (await checkIfNeedsRebuild(agentYamlPath, outputPath, projectDir, agentName)) {
|
||||
needsRebuild.push(`${agentName} (${module})`);
|
||||
} else {
|
||||
upToDate.push(`${agentName} (${module})`);
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
if (needsRebuild.length === 0) {
|
||||
console.log(chalk.green('✓ All agents are up to date'));
|
||||
} else {
|
||||
console.log(chalk.yellow(`${needsRebuild.length} agent(s) need rebuilding:`));
|
||||
for (const agent of needsRebuild) {
|
||||
console.log(chalk.dim(` - ${agent}`));
|
||||
}
|
||||
console.log(chalk.dim('\nRun "bmad build --all" to rebuild all agents'));
|
||||
}
|
||||
|
||||
if (upToDate.length > 0) {
|
||||
console.log(chalk.dim(`\n${upToDate.length} agent(s) up to date`));
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* Check if an agent needs rebuilding by comparing hashes
|
||||
*/
|
||||
async function checkIfNeedsRebuild(yamlPath, outputPath, projectDir, agentName) {
|
||||
// Read the output file to check its metadata
|
||||
const outputContent = await fs.readFile(outputPath, 'utf8');
|
||||
|
||||
// Extract hash from BUILD-META comment
|
||||
const metaMatch = outputContent.match(/source:.*\(hash: ([a-f0-9]+)\)/);
|
||||
if (!metaMatch) {
|
||||
// No metadata, needs rebuild
|
||||
return true;
|
||||
}
|
||||
|
||||
const storedHash = metaMatch[1];
|
||||
|
||||
// Calculate current hash
|
||||
const currentHash = await builder.calculateFileHash(yamlPath);
|
||||
|
||||
if (storedHash !== currentHash) {
|
||||
return true;
|
||||
}
|
||||
|
||||
// Check customize file if it exists
|
||||
const customizePath = path.join(projectDir, '.claude', '_cfg', 'agents', `${agentName}.customize.yaml`);
|
||||
if (await fs.pathExists(customizePath)) {
|
||||
const customizeMetaMatch = outputContent.match(/customize:.*\(hash: ([a-f0-9]+)\)/);
|
||||
if (!customizeMetaMatch) {
|
||||
return true;
|
||||
}
|
||||
|
||||
const storedCustomizeHash = customizeMetaMatch[1];
|
||||
const currentCustomizeHash = await builder.calculateFileHash(customizePath);
|
||||
|
||||
if (storedCustomizeHash !== currentCustomizeHash) {
|
||||
return true;
|
||||
}
|
||||
}
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
/**
|
||||
|
|
|
|||
|
|
@ -2210,8 +2210,9 @@ If AgentVibes party mode is enabled, immediately trigger TTS with agent's voice:
|
|||
const installedFilesMap = new Map();
|
||||
for (const fileEntry of existingFilesManifest) {
|
||||
if (fileEntry.path) {
|
||||
// Files in manifest are stored as relative paths starting with 'bmad/'
|
||||
// Convert to absolute path
|
||||
// Paths are relative to bmadDir. Legacy manifests incorrectly prefixed 'bmad/' -
|
||||
// strip it if present. This is safe because no real path inside bmadDir would
|
||||
// start with 'bmad/' (you'd never have .bmad/bmad/... as an actual structure).
|
||||
const relativePath = fileEntry.path.startsWith('bmad/') ? fileEntry.path.slice(5) : fileEntry.path;
|
||||
const absolutePath = path.join(bmadDir, relativePath);
|
||||
installedFilesMap.set(path.normalize(absolutePath), {
|
||||
|
|
|
|||
|
|
@ -650,13 +650,14 @@ class ManifestGenerator {
|
|||
if (this.allInstalledFiles && this.allInstalledFiles.length > 0) {
|
||||
// Process all installed files
|
||||
for (const filePath of this.allInstalledFiles) {
|
||||
const relativePath = 'bmad' + filePath.replace(this.bmadDir, '').replaceAll('\\', '/');
|
||||
// Store paths relative to bmadDir (no folder prefix)
|
||||
const relativePath = filePath.replace(this.bmadDir, '').replaceAll('\\', '/').replace(/^\//, '');
|
||||
const ext = path.extname(filePath).toLowerCase();
|
||||
const fileName = path.basename(filePath, ext);
|
||||
|
||||
// Determine module from path
|
||||
// Determine module from path (first directory component)
|
||||
const pathParts = relativePath.split('/');
|
||||
const module = pathParts.length > 1 ? pathParts[1] : 'unknown';
|
||||
const module = pathParts.length > 0 ? pathParts[0] : 'unknown';
|
||||
|
||||
// Calculate hash
|
||||
const hash = await this.calculateFileHash(filePath);
|
||||
|
|
@ -672,10 +673,13 @@ class ManifestGenerator {
|
|||
} else {
|
||||
// Fallback: use the collected workflows/agents/tasks
|
||||
for (const file of this.files) {
|
||||
const filePath = path.join(this.bmadDir, file.path.replace(this.bmadFolderName + '/', ''));
|
||||
// Strip the folder prefix if present (for consistency)
|
||||
const relPath = file.path.replace(this.bmadFolderName + '/', '');
|
||||
const filePath = path.join(this.bmadDir, relPath);
|
||||
const hash = await this.calculateFileHash(filePath);
|
||||
allFiles.push({
|
||||
...file,
|
||||
path: relPath,
|
||||
hash: hash,
|
||||
});
|
||||
}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
const fs = require('fs-extra');
|
||||
const yaml = require('js-yaml');
|
||||
const path = require('node:path');
|
||||
const packageJson = require('../../../package.json');
|
||||
|
||||
/**
|
||||
* Configuration utility class
|
||||
|
|
@ -50,7 +51,7 @@ class Config {
|
|||
const standardReplacements = {
|
||||
'{project-root}': replacements.root || '',
|
||||
'{module}': replacements.module || '',
|
||||
'{version}': replacements.version || '5.0.0',
|
||||
'{version}': replacements.version || packageJson.version,
|
||||
'{date}': new Date().toISOString().split('T')[0],
|
||||
};
|
||||
|
||||
|
|
|
|||
|
|
@ -232,21 +232,6 @@ class YamlXmlBuilder {
|
|||
return xml;
|
||||
}
|
||||
|
||||
/**
|
||||
* Build metadata comment
|
||||
*/
|
||||
buildMetadataComment(metadata) {
|
||||
const lines = ['<!-- BUILD-META', ` source: ${metadata.sourceFile || 'unknown'} (hash: ${metadata.sourceHash || 'unknown'})`];
|
||||
|
||||
if (metadata.customizeFile) {
|
||||
lines.push(` customize: ${metadata.customizeFile} (hash: ${metadata.customizeHash || 'unknown'})`);
|
||||
}
|
||||
|
||||
lines.push(` built: ${new Date().toISOString()}`, ` builder-version: ${metadata.builderVersion || '1.0.0'}`, '-->\n');
|
||||
|
||||
return lines.join('\n');
|
||||
}
|
||||
|
||||
/**
|
||||
* Build persona XML section
|
||||
*/
|
||||
|
|
|
|||
Loading…
Reference in New Issue