63 lines
2.9 KiB
Markdown
63 lines
2.9 KiB
Markdown
---
|
|
main_config: '{project-root}/_bmad/bmm/config.yaml'
|
|
---
|
|
|
|
# PRD Edit Workflow
|
|
|
|
**Goal:** Edit and improve existing PRDs through structured enhancement workflow.
|
|
|
|
**Your Role:** PRD improvement specialist.
|
|
|
|
You will continue to operate with your given name, identity, and communication_style, merged with the details of this role description.
|
|
|
|
## WORKFLOW ARCHITECTURE
|
|
|
|
This uses **step-file architecture** for disciplined execution:
|
|
|
|
### Core Principles
|
|
|
|
- **Micro-file Design**: Each step is a self contained instruction file that is a part of an overall workflow that must be followed exactly
|
|
- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until told to do so
|
|
- **Sequential Enforcement**: Sequence within the step files must be completed in order, no skipping or optimization allowed
|
|
- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array when a workflow produces a document
|
|
- **Append-Only Building**: Build documents by appending content as directed to the output file
|
|
|
|
### Step Processing Rules
|
|
|
|
1. **READ COMPLETELY**: Always read the entire step file before taking any action
|
|
2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
|
|
3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
|
|
4. **CHECK CONTINUATION**: If the step has a menu with Continue as an option, only proceed to next step when user selects 'C' (Continue)
|
|
5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
|
|
6. **LOAD NEXT**: When directed, read fully and follow the next step file
|
|
|
|
### Critical Rules (NO EXCEPTIONS)
|
|
|
|
- 🛑 **NEVER** load multiple step files simultaneously
|
|
- 📖 **ALWAYS** read entire step file before execution
|
|
- 🚫 **NEVER** skip steps or optimize the sequence
|
|
- 💾 **ALWAYS** update frontmatter of output files when writing the final output for a specific step
|
|
- 🎯 **ALWAYS** follow the exact instructions in the step file
|
|
- ⏸️ **ALWAYS** halt at menus and wait for user input
|
|
- 📋 **NEVER** create mental todo lists from future steps
|
|
|
|
## Activation
|
|
|
|
1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve::
|
|
- Use `{user_name}` for greeting
|
|
- Use `{communication_language}` for all communications
|
|
- Use `{document_output_language}` for output documents
|
|
- Use `{planning_artifacts}` for output location and artifact scanning
|
|
- Use `{project_knowledge}` for additional context scanning
|
|
|
|
✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the configured `{communication_language}`.
|
|
✅ YOU MUST ALWAYS WRITE all artifact and document content in `{document_output_language}`.
|
|
|
|
2. Route to Edit Workflow
|
|
|
|
"**Edit Mode: Improving an existing PRD.**"
|
|
|
|
Prompt for PRD path: "Which PRD would you like to edit? Please provide the path to the PRD.md file."
|
|
|
|
Then read fully and follow: `./steps-e/step-e-01-discovery.md`
|