Compare commits
3 Commits
35c7ec55d1
...
95bc86c939
| Author | SHA1 | Date |
|---|---|---|
Alex Verkhovsky
|
95bc86c939 | |
|
Alex Verkhovsky
|
fb26467069 | |
|
Alex Verkhovsky
|
a13f399997 |
|
|
@ -153,8 +153,11 @@ Prepare the following structure for document append:
|
|||
I've drafted the executive summary and core vision based on our conversation. This captures the essence of {{project_name}} and what makes it special.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
|
||||
</display>
|
||||
|
||||
|
|
|
|||
|
|
@ -156,8 +156,11 @@ Prepare the following structure for document append:
|
|||
I've mapped out who {{project_name}} serves and how they'll interact with it. This helps us ensure we're building something that real people will love to use.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 5]
|
||||
|
||||
<display>
|
||||
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
|
||||
</display>
|
||||
|
||||
|
|
|
|||
|
|
@ -159,8 +159,11 @@ Prepare the following structure for document append:
|
|||
I've defined success metrics that will help us track whether {{project_name}} is creating real value for users and achieving business objectives.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
|
||||
</display>
|
||||
|
||||
|
|
|
|||
|
|
@ -173,8 +173,11 @@ Prepare the following structure for document append:
|
|||
I've defined the MVP scope for {{project_name}} that balances delivering real value with realistic boundaries. This gives us a clear path forward while keeping our options open for future growth.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue
|
||||
</display>
|
||||
|
||||
|
|
|
|||
|
|
@ -57,18 +57,18 @@ Complete the product brief workflow, update status files, and provide guidance o
|
|||
|
||||
**Completion Announcement:**
|
||||
<display>
|
||||
**Product Brief Complete, {{user_name}}!**
|
||||
🎉 **Product Brief Complete, {{user_name}}!**
|
||||
|
||||
I've successfully collaborated with you to create a comprehensive Product Brief for {{project_name}}.
|
||||
|
||||
**What we've accomplished:**
|
||||
|
||||
- Executive Summary with clear vision and problem statement
|
||||
- Core Vision with solution definition and unique differentiators
|
||||
- Target Users with rich personas and user journeys
|
||||
- Success Metrics with measurable outcomes and business objectives
|
||||
- MVP Scope with focused feature set and clear boundaries
|
||||
- Future Vision that inspires while maintaining current focus
|
||||
- ✅ Executive Summary with clear vision and problem statement
|
||||
- ✅ Core Vision with solution definition and unique differentiators
|
||||
- ✅ Target Users with rich personas and user journeys
|
||||
- ✅ Success Metrics with measurable outcomes and business objectives
|
||||
- ✅ MVP Scope with focused feature set and clear boundaries
|
||||
- ✅ Future Vision that inspires while maintaining current focus
|
||||
|
||||
**The complete Product Brief is now available at:** `{outputFile}`
|
||||
|
||||
|
|
|
|||
|
|
@ -99,7 +99,6 @@ From step 1, I have loaded:
|
|||
|
||||
**Project Type Lookup:**
|
||||
|
||||
<display>
|
||||
Your task: Lookup data in {projectTypesCSV}
|
||||
|
||||
**Search criteria:**
|
||||
|
|
@ -110,11 +109,9 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
|
|||
project_type, detection_signals
|
||||
|
||||
**Do NOT return the entire CSV - only the matching row.**
|
||||
</display>
|
||||
|
||||
**Domain Complexity Lookup:**
|
||||
|
||||
<display>
|
||||
Your task: Lookup data in {domainComplexityCSV}
|
||||
|
||||
**Search criteria:**
|
||||
|
|
@ -125,7 +122,6 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
|
|||
domain, complexity, typical_concerns, compliance_requirements
|
||||
|
||||
**Do NOT return the entire CSV - only the matching row.**
|
||||
</display>
|
||||
|
||||
**Graceful degradation (if Task tool unavailable):**
|
||||
- Load the CSV files directly
|
||||
|
|
|
|||
|
|
@ -95,7 +95,6 @@ Proceed with domain exploration.
|
|||
|
||||
**Attempt subprocess data lookup:**
|
||||
|
||||
<display>
|
||||
Your task: Lookup data in {domainComplexityCSV}
|
||||
|
||||
**Search criteria:**
|
||||
|
|
@ -106,7 +105,6 @@ Return ONLY the matching row as a YAML-formatted object with these fields:
|
|||
domain, complexity, typical_concerns, compliance_requirements
|
||||
|
||||
**Do NOT return the entire CSV - only the matching row.**
|
||||
</display>
|
||||
|
||||
**Graceful degradation (if Task tool unavailable):**
|
||||
- Load the CSV file directly
|
||||
|
|
|
|||
|
|
@ -165,9 +165,11 @@ Present the project-type content for review, then display menu:
|
|||
Based on our conversation and best practices for this product type, I've documented the {project_type}-specific requirements for {{project_name}}.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from section 5]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
</display>
|
||||
|
||||
|
|
|
|||
|
|
@ -98,7 +98,6 @@ ls -t {prd_folder_path}/validation-report-*.md 2>/dev/null | head -1
|
|||
|
||||
**If validation report found:**
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**📋 Found Validation Report**
|
||||
|
||||
|
|
@ -189,7 +188,6 @@ Analyze the loaded PRD:
|
|||
|
||||
**IF validation report provided OR PRD is BMAD Standard/Variant:**
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Edit Requirements Understood**
|
||||
|
||||
|
|
@ -204,7 +202,6 @@ Read fully and follow: next step (step-e-02-review.md)
|
|||
|
||||
**IF PRD is Legacy (Non-Standard) AND no validation report:**
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Format Detected:** Legacy PRD
|
||||
|
||||
|
|
@ -231,7 +228,7 @@ Present MENU OPTIONS below for user selection
|
|||
#### Menu Handling Logic:
|
||||
|
||||
- IF C (Convert): Read fully and follow: {altStepFile} (step-e-01b-legacy-conversion.md)
|
||||
- IF E (Edit As-Is): Display "Proceeding with edits..." then load next step
|
||||
- IF E (Edit As-Is): <display>Proceeding with edits...</display> then load next step
|
||||
- IF X (Exit): Display summary and exit
|
||||
- IF Any other: help user, then redisplay menu
|
||||
|
||||
|
|
|
|||
|
|
@ -126,8 +126,6 @@ Return conversion assessment with gap analysis and effort estimate."
|
|||
|
||||
### 3. Present Conversion Assessment
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Legacy PRD Conversion Assessment**
|
||||
|
||||
|
|
@ -177,7 +175,6 @@ Store conversion decision for next step:
|
|||
- **Edit requirements:** [user's requirements from step e-01]
|
||||
- **Gap analysis:** [summary of gaps identified]
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Conversion Strategy Documented**
|
||||
|
||||
|
|
|
|||
|
|
@ -144,8 +144,6 @@ Return detailed change plan with section breakdown."
|
|||
|
||||
### 4. Present Change Plan to User
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Deep Review Complete - Change Plan**
|
||||
|
||||
|
|
@ -200,7 +198,6 @@ Store approved change plan for next step:
|
|||
- **Priority order:** Sequence to apply changes
|
||||
- **User confirmed:** Yes
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Change Plan Approved**
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,6 @@ From step e-02, retrieve:
|
|||
- **Priority order:** Sequence to apply changes
|
||||
- **User requirements:** Edit goals from step e-01
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Starting PRD Edits**
|
||||
|
||||
|
|
@ -150,7 +149,6 @@ Changes: {brief summary}
|
|||
8. Functional Requirements
|
||||
9. Non-Functional Requirements
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**PRD Restructured**
|
||||
BMAD standard structure applied.
|
||||
|
|
@ -200,8 +198,6 @@ editHistory:
|
|||
|
||||
### 7. Confirm Completion
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**PRD Edits Complete**
|
||||
|
||||
|
|
@ -232,7 +228,7 @@ Display:
|
|||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF V (Validate): Display "Starting validation workflow..." then read fully and follow: steps-v/step-v-01-discovery.md
|
||||
- IF V (Validate): <display>Starting validation workflow...</display> then read fully and follow: steps-v/step-v-01-discovery.md
|
||||
- IF S (Summary): Present edit summary and exit
|
||||
- IF A (Adjust): Accept additional requirements, loop back to editing
|
||||
- IF X (Exit): Display summary and exit
|
||||
|
|
|
|||
|
|
@ -78,8 +78,6 @@ From step e-03 change execution, compile:
|
|||
|
||||
### 2. Present Completion Summary
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**✓ PRD Edit Complete**
|
||||
|
||||
|
|
@ -103,12 +101,12 @@ Display:
|
|||
|
||||
### 3. Present MENU OPTIONS
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**[V] Run Full Validation** - Execute complete validation workflow (steps-v) to verify PRD quality
|
||||
**[E] Edit More** - Make additional edits to the PRD
|
||||
**[S] Summary** - End with detailed summary of changes
|
||||
**[X] Exit** - Exit edit workflow
|
||||
</display>
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
|
|
@ -118,8 +116,7 @@ Display:
|
|||
#### Menu Handling Logic:
|
||||
|
||||
- **IF V (Run Full Validation):**
|
||||
- Display:
|
||||
<display>
|
||||
- <display>
|
||||
**Starting Validation Workflow**
|
||||
|
||||
This will run all 13 validation checks on the updated PRD.
|
||||
|
|
@ -134,7 +131,7 @@ Display:
|
|||
- **IF E (Edit More):**
|
||||
- <display>**Additional Edits**</display>
|
||||
- Ask: "What additional edits would you like to make?"
|
||||
- Accept input, then display: "**Returning to edit step...**"
|
||||
- Accept input, then <display>**Returning to edit step...**</display>
|
||||
- Read fully and follow: step-e-03-edit.md again
|
||||
|
||||
- **IF S (Summary):**
|
||||
|
|
|
|||
|
|
@ -184,8 +184,6 @@ validationStatus: IN_PROGRESS
|
|||
|
||||
### 9. Present MENU OPTIONS
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Format Detection
|
||||
</display>
|
||||
|
|
|
|||
|
|
@ -132,8 +132,6 @@ Append to validation report:
|
|||
|
||||
**IF format is BMAD Standard or BMAD Variant:**
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Format Detected:** {classification}
|
||||
|
||||
|
|
@ -144,8 +142,6 @@ Without delay, read fully and follow: {nextStepFile} (step-v-03-density-validati
|
|||
|
||||
**IF format is Non-Standard (< 3 core sections):**
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Format Detected:** Non-Standard PRD
|
||||
|
||||
|
|
@ -170,7 +166,7 @@ Present MENU OPTIONS below for user selection
|
|||
#### Menu Handling Logic:
|
||||
|
||||
- IF A (Parity Check): Read fully and follow: {altStepFile} (step-v-02b-parity-check.md)
|
||||
- IF B (Validate As-Is): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
|
||||
- IF B (Validate As-Is): <display>Proceeding with validation...</display> then read fully and follow: {nextStepFile}
|
||||
- IF C (Exit): Display format findings summary and exit validation
|
||||
- IF Any other: help user respond, then redisplay menu
|
||||
|
||||
|
|
|
|||
|
|
@ -153,8 +153,6 @@ Append to validation report:
|
|||
|
||||
### 4. Present Parity Analysis and Options
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Parity Analysis Complete**
|
||||
|
||||
|
|
@ -182,7 +180,7 @@ Your PRD is missing {count} of 6 core BMAD PRD sections. The overall effort to r
|
|||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF C (Continue): Display "Proceeding with validation..." then read fully and follow: {nextStepFile}
|
||||
- IF C (Continue): <display>Proceeding with validation...</display> then read fully and follow: {nextStepFile}
|
||||
- IF E (Exit): Display parity summary and exit validation
|
||||
- IF S (Save): Confirm saved, display summary, exit
|
||||
- IF Any other: help user respond, then redisplay menu
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ Validate PRD meets BMAD information density standards by scanning for conversati
|
|||
|
||||
- 🎯 Scan PRD for density anti-patterns systematically
|
||||
- 💾 Append density findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -142,8 +142,6 @@ Append to validation report:
|
|||
|
||||
### 5. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Information Density Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ Validate that PRD covers all content from Product Brief (if brief was used as in
|
|||
- 💬 If no brief: Skip this check and report "N/A - No Product Brief"
|
||||
- 🎯 If brief exists: Map brief content to PRD sections
|
||||
- 💾 Append coverage findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -72,8 +72,6 @@ Append to validation report:
|
|||
**Status:** N/A - No Product Brief was provided as input
|
||||
```
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Product Brief Coverage: Skipped** (No Product Brief provided)
|
||||
|
||||
|
|
@ -184,8 +182,6 @@ Append to validation report:
|
|||
|
||||
### 6. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Product Brief Coverage Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Validate that all Functional Requirements (FRs) and Non-Functional Requirements
|
|||
- 🎯 Extract all FRs and NFRs from PRD
|
||||
- 💾 Validate each for measurability and format
|
||||
- 📖 Append findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -195,8 +195,6 @@ Append to validation report:
|
|||
|
||||
### 5. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Measurability Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Validate the traceability chain from Executive Summary → Success Criteria →
|
|||
- 🎯 Build and validate traceability matrix
|
||||
- 💾 Identify broken chains and orphan requirements
|
||||
- 📖 Append findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -183,8 +183,6 @@ Append to validation report:
|
|||
|
||||
### 5. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Traceability Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Ensure Functional Requirements and Non-Functional Requirements don't include imp
|
|||
- 🎯 Scan FRs and NFRs for implementation terms
|
||||
- 💾 Distinguish capability-relevant vs leakage
|
||||
- 📖 Append findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -172,8 +172,6 @@ Append to validation report:
|
|||
|
||||
### 5. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Implementation Leakage Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Validate domain-specific requirements are present for high-complexity domains (H
|
|||
- 💬 If low complexity (general): Skip detailed checks
|
||||
- 🎯 If high complexity: Validate required special sections
|
||||
- 💾 Append compliance findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -155,8 +155,6 @@ Append to validation report:
|
|||
**Note:** This PRD is for a standard domain without regulatory compliance requirements.
|
||||
```
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Domain Compliance Validation Skipped**
|
||||
|
||||
|
|
@ -210,8 +208,6 @@ Append to validation report:
|
|||
|
||||
### 7. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Domain Compliance Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Validate project-type specific requirements are properly documented - different
|
|||
- 🎯 Validate required sections for that project type are present
|
||||
- 🎯 Validate excluded sections for that project type are absent
|
||||
- 💾 Append compliance findings to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -227,8 +227,6 @@ Append to validation report:
|
|||
|
||||
### 7. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Project-Type Compliance Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ Validate Functional Requirements meet SMART quality criteria (Specific, Measurab
|
|||
- 🎯 Score each FR on SMART criteria (Specific, Measurable, Attainable, Relevant, Traceable)
|
||||
- 💾 Flag FRs with score < 3 in any category
|
||||
- 📖 Append scoring table and suggestions to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -173,8 +173,6 @@ Append to validation report:
|
|||
|
||||
### 5. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**SMART Requirements Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ Assess the PRD as a cohesive, compelling document - evaluating document flow, du
|
|||
- 🎯 Use Advanced Elicitation for multi-perspective assessment
|
||||
- 🎯 Evaluate document flow, dual audience, BMAD principles
|
||||
- 💾 Append comprehensive assessment to validation report
|
||||
- 📖 Display "Proceeding to next check..." and load next step
|
||||
- 📖 <display>Proceeding to next check...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -226,8 +226,6 @@ Append to validation report:
|
|||
|
||||
### 4. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Holistic Quality Assessment Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Final comprehensive completeness check - validate no template variables remain,
|
|||
- 🎯 Validate section-specific completeness
|
||||
- 🎯 Validate frontmatter completeness
|
||||
- 💾 Append completeness matrix to validation report
|
||||
- 📖 Display "Proceeding to final step..." and load next step
|
||||
- 📖 <display>Proceeding to final step...</display> and load next step
|
||||
- 🚫 FORBIDDEN to pause or request user input
|
||||
|
||||
## CONTEXT BOUNDARIES:
|
||||
|
|
@ -206,8 +206,6 @@ Append to validation report:
|
|||
|
||||
### 4. Display Progress and Auto-Proceed
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**Completeness Validation Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -123,8 +123,6 @@ overallStatus: '{Pass/Warning/Critical based on all findings}'
|
|||
|
||||
### 4. Present Summary to User Conversationally
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**✓ PRD Validation Complete**
|
||||
|
||||
|
|
@ -160,12 +158,12 @@ Display:
|
|||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
**[R] Review Detailed Findings** - Walk through validation report section by section
|
||||
**[E] Use Edit Workflow** - Use validation report with Edit workflow for systematic improvements
|
||||
**[F] Fix Simpler Items** - Immediate fixes for simple issues (anti-patterns, leakage, missing headers)
|
||||
**[X] Exit** - Exit and Suggest Next Steps.
|
||||
</display>
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
|
|
@ -197,7 +195,6 @@ Display:
|
|||
- Return to menu
|
||||
|
||||
- **IF X (Exit):**
|
||||
- Display:
|
||||
<display>
|
||||
**Validation Report Saved:** {validationReportPath}
|
||||
|
||||
|
|
|
|||
|
|
@ -152,9 +152,11 @@ Show the generated project understanding content and present choices:
|
|||
I've documented our understanding of {{project_name}} from a UX perspective. This will guide all our design decisions moving forward.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 5]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[C] Continue - Save this to the document and move to core experience definition
|
||||
</display>
|
||||
|
|
|
|||
|
|
@ -160,9 +160,11 @@ Show the generated core experience content and present choices:
|
|||
I've defined the core user experience for {{project_name}} based on our conversation. This establishes the foundation for all our UX design decisions.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine the core experience definition
|
||||
[P] Party Mode - Bring different perspectives on the user experience
|
||||
|
|
|
|||
|
|
@ -163,9 +163,11 @@ Show the generated emotional response content and present choices:
|
|||
I've defined the desired emotional responses for {{project_name}}. These emotional goals will guide our design decisions to create the right user experience.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine the emotional response definition
|
||||
[P] Party Mode - Bring different perspectives on user emotional needs
|
||||
|
|
|
|||
|
|
@ -178,9 +178,11 @@ Show the generated inspiration analysis content and present choices:
|
|||
I've analyzed inspiring UX patterns and products to inform our design strategy for {{project_name}}. This gives us a solid foundation of proven patterns to build upon.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's deepen our UX pattern analysis
|
||||
[P] Party Mode - Bring different perspectives on inspiration sources
|
||||
|
|
|
|||
|
|
@ -196,9 +196,11 @@ Show the generated design system content and present choices:
|
|||
I've documented our design system choice for {{project_name}}. This foundation will ensure consistency and speed up development.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our design system decision
|
||||
[P] Party Mode - Bring technical perspectives on design systems
|
||||
|
|
|
|||
|
|
@ -198,9 +198,11 @@ Show the generated defining experience content and present choices:
|
|||
I've defined the core experience for {{project_name}} - the interaction that will make users love this product.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine the core experience definition
|
||||
[P] Party Mode - Bring different perspectives on the defining interaction
|
||||
|
|
|
|||
|
|
@ -168,9 +168,11 @@ Show the generated visual foundation content and present choices:
|
|||
I've established the visual design foundation for {{project_name}}. This provides the building blocks for consistent, beautiful design.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our visual foundation
|
||||
[P] Party Mode - Bring design perspectives on visual choices
|
||||
|
|
|
|||
|
|
@ -168,9 +168,11 @@ Show the generated design direction content and present choices:
|
|||
I've documented our design direction decision for {{project_name}}. This visual approach will guide all our detailed design work.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our design direction
|
||||
[P] Party Mode - Bring different perspectives on visual choices
|
||||
|
|
|
|||
|
|
@ -186,9 +186,11 @@ Show the generated user journey content and present choices:
|
|||
I've designed detailed user journey flows for {{project_name}}. These flows will guide the detailed design of each user interaction.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our user journey designs
|
||||
[P] Party Mode - Bring different perspectives on user flows
|
||||
|
|
|
|||
|
|
@ -190,9 +190,11 @@ Show the generated component strategy content and present choices:
|
|||
I've defined the component strategy for {{project_name}}. This balances using proven design system components with custom components for your unique needs.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our component strategy
|
||||
[P] Party Mode - Bring technical perspectives on component design
|
||||
|
|
|
|||
|
|
@ -177,9 +177,11 @@ Show the generated UX patterns content and present choices:
|
|||
I've established UX consistency patterns for {{project_name}}. These patterns ensure users have a consistent, predictable experience across all interactions.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our UX patterns
|
||||
[P] Party Mode - Bring different perspectives on consistency patterns
|
||||
|
|
|
|||
|
|
@ -208,9 +208,11 @@ Show the generated responsive and accessibility content and present choices:
|
|||
I've defined the responsive design and accessibility strategy for {{project_name}}. This ensures your product works beautifully across all devices and is accessible to all users.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's refine our responsive/accessibility strategy
|
||||
[P] Party Mode - Bring different perspectives on inclusive design
|
||||
|
|
|
|||
|
|
@ -106,7 +106,6 @@ This assessment identified [X] issues across [Y] categories. Address the critica
|
|||
|
||||
### 5. Present Completion
|
||||
|
||||
Display:
|
||||
<display>
|
||||
**Implementation Readiness Assessment Complete**
|
||||
|
||||
|
|
|
|||
|
|
@ -161,9 +161,11 @@ Show the generated content and present choices:
|
|||
I've drafted the Project Context Analysis based on your requirements. This sets the foundation for our architectural decisions.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 4]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Let's dive deeper into architectural implications
|
||||
[P] Party Mode - Bring different perspectives to analyze requirements
|
||||
|
|
|
|||
|
|
@ -266,8 +266,6 @@ Prepare the content to append to the document:
|
|||
|
||||
**Note:** Project initialization using this command should be the first implementation story.
|
||||
|
||||
```
|
||||
|
||||
### 9. Present Content and Menu
|
||||
|
||||
Show the generated content and present choices:
|
||||
|
|
@ -276,9 +274,11 @@ Show the generated content and present choices:
|
|||
I've analyzed starter template options for {{project_type}} projects.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 8]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Explore custom approaches or unconventional starters
|
||||
[P] Party Mode - Evaluate trade-offs from different perspectives
|
||||
|
|
@ -340,4 +340,3 @@ When user selects 'C', append the content directly to the document using the str
|
|||
After user selects 'C' and content is saved to document, load `./step-04-decisions.md` to begin making specific architectural decisions.
|
||||
|
||||
Remember: Do NOT proceed to step-04 until user explicitly selects 'C' from the A/P/C menu and content is saved!
|
||||
```
|
||||
|
|
|
|||
|
|
@ -265,9 +265,11 @@ Show the generated decisions content and present choices:
|
|||
I've documented all the core architectural decisions we've made together.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 5]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Explore innovative approaches to any specific decisions
|
||||
[P] Party Mode - Review decisions from multiple perspectives
|
||||
|
|
|
|||
|
|
@ -300,9 +300,11 @@ Show the generated patterns content and present choices:
|
|||
I've documented implementation patterns that will prevent conflicts between AI agents working on this project.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 4]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Explore additional consistency patterns
|
||||
[P] Party Mode - Review patterns from different implementation perspectives
|
||||
|
|
|
|||
|
|
@ -322,9 +322,11 @@ Show the generated project structure content and present choices:
|
|||
I've created a complete project structure based on all our architectural decisions.
|
||||
|
||||
**Here's what I'll add to the document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Explore innovative project organization approaches
|
||||
[P] Party Mode - Review structure from different development perspectives
|
||||
|
|
|
|||
|
|
@ -300,9 +300,11 @@ I've completed a comprehensive validation of your architecture.
|
|||
- ✅ Readiness: AI agents can implement consistently
|
||||
|
||||
**Here's what I'll add to complete the architecture document:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content from step 6]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Address any complex architectural concerns
|
||||
[P] Party Mode - Review validation from different implementation perspectives
|
||||
|
|
|
|||
|
|
@ -140,12 +140,12 @@ For each epic in the approved epics_list:
|
|||
|
||||
#### A. Epic Overview
|
||||
|
||||
Display:
|
||||
|
||||
<display>
|
||||
- Epic number and title
|
||||
- Epic goal statement
|
||||
- FRs covered by this epic
|
||||
- Any NFRs or additional requirements relevant
|
||||
</display>
|
||||
|
||||
#### B. Story Breakdown
|
||||
|
||||
|
|
|
|||
|
|
@ -106,13 +106,15 @@ Use holistic judgment, not mechanical keyword matching.
|
|||
|
||||
### Escalation Triggered - Level 0-2
|
||||
|
||||
Present: "This looks like a focused feature with multiple components."
|
||||
|
||||
Display:
|
||||
<display>
|
||||
This looks like a focused feature with multiple components.
|
||||
</display>
|
||||
|
||||
<display>
|
||||
**[P] Plan first (tech-spec)** (recommended)
|
||||
**[W] Seems bigger than quick-dev** - Recommend the Full BMad Flow PRD Process
|
||||
**[E] Execute directly**
|
||||
</display>
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
|
|
@ -129,13 +131,15 @@ Display:
|
|||
|
||||
### Escalation Triggered - Level 3+
|
||||
|
||||
Present: "This sounds like platform/system work."
|
||||
|
||||
Display:
|
||||
<display>
|
||||
This sounds like platform/system work.
|
||||
</display>
|
||||
|
||||
<display>
|
||||
**[W] Start BMad Method** (recommended)
|
||||
**[P] Plan first (tech-spec)** (lighter planning)
|
||||
**[E] Execute directly** - feeling lucky
|
||||
</display>
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
|
|
|
|||
|
|
@ -74,8 +74,7 @@ If `{execution_mode}` is "tech-spec":
|
|||
|
||||
## IMPLEMENTATION SUMMARY
|
||||
|
||||
Present summary to transition to review:
|
||||
|
||||
<display>
|
||||
```
|
||||
**Implementation Complete!**
|
||||
|
||||
|
|
@ -86,6 +85,7 @@ Present summary to transition to review:
|
|||
|
||||
Proceeding to adversarial code review...
|
||||
```
|
||||
</display>
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -25,13 +25,15 @@ From previous steps:
|
|||
|
||||
## RESOLUTION OPTIONS
|
||||
|
||||
Present: "How would you like to handle these findings?"
|
||||
|
||||
Display:
|
||||
<display>
|
||||
How would you like to handle these findings?
|
||||
</display>
|
||||
|
||||
<display>
|
||||
**[W] Walk through** - Discuss each finding individually
|
||||
**[F] Fix automatically** - Automatically fix issues classified as "real"
|
||||
**[S] Skip** - Acknowledge and proceed to commit
|
||||
</display>
|
||||
|
||||
### Menu Handling Logic:
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ First, check if project context already exists:
|
|||
|
||||
- Look for file at `{project_knowledge}/project-context.md or {project-root}/**/project-context.md`
|
||||
- If exists: Read complete file to understand existing rules
|
||||
- Present to user: "Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?"
|
||||
- <display>Found existing project context with {number_of_sections} sections. Would you like to update this or create a new one?</display>
|
||||
|
||||
### 2. Discover Project Technology Stack
|
||||
|
||||
|
|
|
|||
|
|
@ -274,9 +274,11 @@ After each category, show the generated rules and present choices:
|
|||
I've drafted the {{category_name}} rules for your project context.
|
||||
|
||||
**Here's what I'll add:**
|
||||
</display>
|
||||
|
||||
[Show the complete markdown content for this category]
|
||||
|
||||
<display>
|
||||
**What would you like to do?**
|
||||
[A] Advanced Elicitation - Explore nuanced rules for this category
|
||||
[P] Party Mode - Review from different implementation perspectives
|
||||
|
|
|
|||
|
|
@ -168,7 +168,7 @@ Your project context is complete and optimized for AI agents!
|
|||
|
||||
**Beginner Mode:**
|
||||
<display>
|
||||
Excellent! Your project context guide is ready!
|
||||
Excellent! Your project context guide is ready! 🎉
|
||||
|
||||
**What this does:**
|
||||
Think of this as a 'rules of the road' guide for AI agents working on your project. It ensures they all follow the same patterns and avoid common mistakes.
|
||||
|
|
@ -232,26 +232,26 @@ Final checks before completion:
|
|||
Present final completion to user:
|
||||
|
||||
<display>
|
||||
**Project Context Generation Complete!**
|
||||
✅ **Project Context Generation Complete!**
|
||||
|
||||
Your optimized project context file is ready at:
|
||||
`{output_folder}/project-context.md`
|
||||
|
||||
**Context Summary:**
|
||||
**📊 Context Summary:**
|
||||
|
||||
- {{rule_count}} critical rules for AI agents
|
||||
- {{section_count}} comprehensive sections
|
||||
- Optimized for LLM context efficiency
|
||||
- Ready for immediate agent integration
|
||||
|
||||
**Key Benefits:**
|
||||
**🎯 Key Benefits:**
|
||||
|
||||
- Consistent implementation across all AI agents
|
||||
- Reduced common mistakes and edge cases
|
||||
- Clear guidance for project-specific patterns
|
||||
- Minimal LLM context usage
|
||||
|
||||
**Next Steps:**
|
||||
**📋 Next Steps:**
|
||||
|
||||
1. AI agents will automatically read this file when implementing
|
||||
2. Update this file when your technology stack or patterns evolve
|
||||
|
|
|
|||
|
|
@ -105,7 +105,7 @@ When an agent asks the user a specific question:
|
|||
|
||||
- End that response round immediately after the question
|
||||
- Clearly highlight: **[Agent Name] asks: [Their question]**
|
||||
- Display: _[Awaiting user response...]_
|
||||
- <display>_[Awaiting user response...]_</display>
|
||||
- WAIT for user input before continuing
|
||||
|
||||
**Rhetorical Questions:**
|
||||
|
|
|
|||
Loading…
Reference in New Issue