refactor(bmm): rename Scrum Master to Agile Delivery Lead (SM → ADL)
- Rename sm.agent.yaml to adl.agent.yaml - Update skill manifest, module-help.csv, and team configs - Update all documentation references including zh-CN - Update workflow dialogue from 'Bob (Scrum Master)' to 'Bob (Agile Delivery Lead)' - Add changelog entry
This commit is contained in:
omikheev
parent
80671650c2
commit
9c09190dac
269
CHANGELOG.md
269
CHANGELOG.md
|
|
@ -4,36 +4,37 @@
|
|||
|
||||
### Highlights
|
||||
|
||||
* Whiteport Design Studio (WDS) module enabled in the installer
|
||||
* Support @next installation channel (`npx bmad-method@next install`) — get the latest tip of main instead of waiting for the next stable published version
|
||||
* Everything now installs as a skill — all workflows, agents, and tasks converted to markdown with SKILL.md entrypoints (not yet optimized skills, but unified format)
|
||||
* An experimental preview of the new Quick Dev is available, which will become the main Phase 4 development tool
|
||||
* Edge Case Hunter added as a parallel code review layer in Phase 4, improving code quality by exhaustively tracing branching paths and boundary conditions (#1791)
|
||||
* Documentation now available in Chinese (zh-CN) with complete translation (#1822, #1795)
|
||||
- Whiteport Design Studio (WDS) module enabled in the installer
|
||||
- Support @next installation channel (`npx bmad-method@next install`) — get the latest tip of main instead of waiting for the next stable published version
|
||||
- Everything now installs as a skill — all workflows, agents, and tasks converted to markdown with SKILL.md entrypoints (not yet optimized skills, but unified format)
|
||||
- An experimental preview of the new Quick Dev is available, which will become the main Phase 4 development tool
|
||||
- Edge Case Hunter added as a parallel code review layer in Phase 4, improving code quality by exhaustively tracing branching paths and boundary conditions (#1791)
|
||||
- Documentation now available in Chinese (zh-CN) with complete translation (#1822, #1795)
|
||||
|
||||
### 💥 Breaking Changes
|
||||
|
||||
* Convert entire BMAD method to skills-based architecture with unified skill manifests (#1834)
|
||||
* Convert all core workflows from YAML+instructions to single workflow.md format
|
||||
* Migrate all remaining platforms to native Agent Skills format (#1841)
|
||||
* Remove legacy YAML/XML workflow engine plumbing (#1864)
|
||||
- Convert entire BMAD method to skills-based architecture with unified skill manifests (#1834)
|
||||
- Convert all core workflows from YAML+instructions to single workflow.md format
|
||||
- Migrate all remaining platforms to native Agent Skills format (#1841)
|
||||
- Remove legacy YAML/XML workflow engine plumbing (#1864)
|
||||
|
||||
### 🎁 Features
|
||||
|
||||
* Add Pi coding agent as supported platform (#1854)
|
||||
* Add unified skill scanner decoupled from legacy collectors (#1859)
|
||||
* Add continuous delivery workflows for npm publishing with trusted OIDC publishing (#1872)
|
||||
- Add Pi coding agent as supported platform (#1854)
|
||||
- Add unified skill scanner decoupled from legacy collectors (#1859)
|
||||
- Add continuous delivery workflows for npm publishing with trusted OIDC publishing (#1872)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* Update terminology from "commands" to "skills" across all documentation (#1850)
|
||||
- Update terminology from "commands" to "skills" across all documentation (#1850)
|
||||
- Rename "Scrum Master" role to "Agile Delivery Lead" (SM → ADL) across all agents, workflows, and documentation
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* Fix code review removing mandatory minimum issue count that caused infinite review loops (#1913)
|
||||
* Fix silent loss of brainstorming ideas in PRD by adding reconciliation step (#1914)
|
||||
* Reduce npm tarball from 533 to 348 files (91% size reduction, 6.2 MB → 555 KB) via .npmignore (#1900)
|
||||
* Fix party-mode skill conversion review findings (#1919)
|
||||
- Fix code review removing mandatory minimum issue count that caused infinite review loops (#1913)
|
||||
- Fix silent loss of brainstorming ideas in PRD by adding reconciliation step (#1914)
|
||||
- Reduce npm tarball from 533 to 348 files (91% size reduction, 6.2 MB → 555 KB) via .npmignore (#1900)
|
||||
- Fix party-mode skill conversion review findings (#1919)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -41,14 +42,14 @@
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* Add edge case hunter review task - new reusable review task that exhaustively traces branching paths and boundary conditions in code, reporting only unhandled gaps. Method-driven analysis complementary to adversarial review (#1790)
|
||||
- Add edge case hunter review task - new reusable review task that exhaustively traces branching paths and boundary conditions in code, reporting only unhandled gaps. Method-driven analysis complementary to adversarial review (#1790)
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* Fix brainstorming to not overwrite previous sessions; now prompts to continue existing brainstorming or start a new one when older brainstorming sessions are found
|
||||
* Fix installer templates - replace legacy `@` path prefixes with explicit `{project-root}` syntax for consistency (#1769)
|
||||
* Fix edge case hunter - remove zero-findings halt condition that was pressuring the LLM to hallucinate findings when none legitimately exist (#1797)
|
||||
* Fix broken docs domain references in README and GitHub issue templates (#1777)
|
||||
- Fix brainstorming to not overwrite previous sessions; now prompts to continue existing brainstorming or start a new one when older brainstorming sessions are found
|
||||
- Fix installer templates - replace legacy `@` path prefixes with explicit `{project-root}` syntax for consistency (#1769)
|
||||
- Fix edge case hunter - remove zero-findings halt condition that was pressuring the LLM to hallucinate findings when none legitimately exist (#1797)
|
||||
- Fix broken docs domain references in README and GitHub issue templates (#1777)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -56,24 +57,24 @@
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* Add bmad-os-root-cause-analysis skill for analyzing bug-fix commits and producing structured root cause analysis reports with pyramid communication format (#1741)
|
||||
- Add bmad-os-root-cause-analysis skill for analyzing bug-fix commits and producing structured root cause analysis reports with pyramid communication format (#1741)
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* Fix installer to refuse installation when ancestor directory has BMAD commands, preventing duplicate command autocompletion in nested directories (#1735)
|
||||
* Fix OpenCode integration by replacing unsupported `name` frontmatter with `mode: all` and update directory names to plural form (#1764)
|
||||
* Fix CSV manifest pipeline double-escaping of quotes that was corrupting output files; switch Gemini templates to single quotes (#1746)
|
||||
* Fix workflow descriptions to use proper quotes so they format better in skill conversion and don't break yaml front matter
|
||||
* Fix workflow help task chaining by removing ambiguous "with-argument" clause that caused LLMs to misinterpret help.md as skill calls (#1740)
|
||||
- Fix installer to refuse installation when ancestor directory has BMAD commands, preventing duplicate command autocompletion in nested directories (#1735)
|
||||
- Fix OpenCode integration by replacing unsupported `name` frontmatter with `mode: all` and update directory names to plural form (#1764)
|
||||
- Fix CSV manifest pipeline double-escaping of quotes that was corrupting output files; switch Gemini templates to single quotes (#1746)
|
||||
- Fix workflow descriptions to use proper quotes so they format better in skill conversion and don't break yaml front matter
|
||||
- Fix workflow help task chaining by removing ambiguous "with-argument" clause that caused LLMs to misinterpret help.md as skill calls (#1740)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* Standardize all workflow descriptions to use proper quotes to prevent breaking command or skill front matter during skill conversion
|
||||
- Standardize all workflow descriptions to use proper quotes to prevent breaking command or skill front matter during skill conversion
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* Fix broken TEA hyperlinks to point to new repository URL (#1772)
|
||||
* Rebrand BMAD acronym to "Build More Architect Dreams" across documentation (#1765)
|
||||
- Fix broken TEA hyperlinks to point to new repository URL (#1772)
|
||||
- Rebrand BMAD acronym to "Build More Architect Dreams" across documentation (#1765)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -81,36 +82,36 @@
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* Add CodeBuddy platform support with installer configuration (#1483)
|
||||
* Add LLM audit prompt for file reference conventions - new audit tool using parallel subagents (#1720)
|
||||
* Migrate Codex installer from `.codex/prompts` to `.agents/skills` format to align with Codex CLI changes (#1729)
|
||||
* Convert review-pr and audit-file-refs tools to proper bmad-os skills with slash commands `bmad-os-review-pr` and `bmad-os-audit-file-refs` (#1732)
|
||||
- Add CodeBuddy platform support with installer configuration (#1483)
|
||||
- Add LLM audit prompt for file reference conventions - new audit tool using parallel subagents (#1720)
|
||||
- Migrate Codex installer from `.codex/prompts` to `.agents/skills` format to align with Codex CLI changes (#1729)
|
||||
- Convert review-pr and audit-file-refs tools to proper bmad-os skills with slash commands `bmad-os-review-pr` and `bmad-os-audit-file-refs` (#1732)
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* Fix 24 broken step references in create-architecture workflow after directory rename (#1734)
|
||||
* Fix step file path references in check-implementation-readiness workflow (#1709, #1716)
|
||||
* Fix 3 broken file references and enable strict file reference validation in CI (#1717)
|
||||
* Fix Rovo Dev integration with custom installer that generates prompts.yml manifest (#1701)
|
||||
* Fix 104 relative step file references to use standardized `{project-root}/_bmad/` paths across 68 files (#1722)
|
||||
* Fix code fence imbalance in step-03-starter.md that caused rendering issues (#1724)
|
||||
* Remove Windsurf from recommended/preferred IDEs list (#1727)
|
||||
* Fix default Codex install location from global to project for better defaults (#1698)
|
||||
* Add npx cache workaround to Quick Start for stale beta versions (#1685)
|
||||
* Add language instructions to replace placeholder text in Research overview (#1703)
|
||||
* Ignore `.junie/` IDE integration folder in git and prettier configs (#1719)
|
||||
- Fix 24 broken step references in create-architecture workflow after directory rename (#1734)
|
||||
- Fix step file path references in check-implementation-readiness workflow (#1709, #1716)
|
||||
- Fix 3 broken file references and enable strict file reference validation in CI (#1717)
|
||||
- Fix Rovo Dev integration with custom installer that generates prompts.yml manifest (#1701)
|
||||
- Fix 104 relative step file references to use standardized `{project-root}/_bmad/` paths across 68 files (#1722)
|
||||
- Fix code fence imbalance in step-03-starter.md that caused rendering issues (#1724)
|
||||
- Remove Windsurf from recommended/preferred IDEs list (#1727)
|
||||
- Fix default Codex install location from global to project for better defaults (#1698)
|
||||
- Add npx cache workaround to Quick Start for stale beta versions (#1685)
|
||||
- Add language instructions to replace placeholder text in Research overview (#1703)
|
||||
- Ignore `.junie/` IDE integration folder in git and prettier configs (#1719)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* Update open source tool skills structure for future plugin migration
|
||||
* Standardize all workflow descriptions for skill generation with concise format and explicit trigger phrases
|
||||
* Remove `disable-model-invocation` flag from all IDE installer templates to enable workflow skill calls
|
||||
- Update open source tool skills structure for future plugin migration
|
||||
- Standardize all workflow descriptions for skill generation with concise format and explicit trigger phrases
|
||||
- Remove `disable-model-invocation` flag from all IDE installer templates to enable workflow skill calls
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* Elevate `bmad-help` as primary on-ramp across all documentation
|
||||
* Update workflow names with `bmad-bmm-` prefix and standardize table formatting
|
||||
* Clarify phase routing and catalog path in help task
|
||||
- Elevate `bmad-help` as primary on-ramp across all documentation
|
||||
- Update workflow names with `bmad-bmm-` prefix and standardize table formatting
|
||||
- Clarify phase routing and catalog path in help task
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -120,32 +121,32 @@ V6 Stable Release! The End of Beta!
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* Add PRD workflow steps 2b (vision/differentiators) and 2c (executive summary) for more complete product requirements documentation
|
||||
* Add new `bmad uninstall` command with interactive and non-interactive modes for selective component removal
|
||||
* Add dedicated GitHub Copilot installer that generates enriched `.agent.md`, `.prompt.md` files and project configuration
|
||||
* Add TEA browser automation prerequisite prompts to guide Playwright CLI/MCP setup after configuration
|
||||
- Add PRD workflow steps 2b (vision/differentiators) and 2c (executive summary) for more complete product requirements documentation
|
||||
- Add new `bmad uninstall` command with interactive and non-interactive modes for selective component removal
|
||||
- Add dedicated GitHub Copilot installer that generates enriched `.agent.md`, `.prompt.md` files and project configuration
|
||||
- Add TEA browser automation prerequisite prompts to guide Playwright CLI/MCP setup after configuration
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* Fix version comparison to use semantic versioning, preventing incorrect downgrade recommendations to older beta versions
|
||||
* Fix `--custom-content` flag to properly populate sources and selected files in module config
|
||||
* Fix module configuration UX messaging to show accurate completion status and improve feedback timing
|
||||
* Fix changelog URL in installer start message for proper GitHub resolution
|
||||
* Remove incorrect `mode: primary` from OpenCode agent template and restore `name` field across all templates
|
||||
* Auto-discover PRD files in validate-prd workflow to reduce manual path input
|
||||
* Fix installer non-interactive mode hanging and improve IDE configuration handling during updates
|
||||
* Fix workflow-level config.yaml copying for custom content modules
|
||||
- Fix version comparison to use semantic versioning, preventing incorrect downgrade recommendations to older beta versions
|
||||
- Fix `--custom-content` flag to properly populate sources and selected files in module config
|
||||
- Fix module configuration UX messaging to show accurate completion status and improve feedback timing
|
||||
- Fix changelog URL in installer start message for proper GitHub resolution
|
||||
- Remove incorrect `mode: primary` from OpenCode agent template and restore `name` field across all templates
|
||||
- Auto-discover PRD files in validate-prd workflow to reduce manual path input
|
||||
- Fix installer non-interactive mode hanging and improve IDE configuration handling during updates
|
||||
- Fix workflow-level config.yaml copying for custom content modules
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* Remove alias variables from Phase 4 workflows, use canonical `{implementation_artifacts}` and `{planning_artifacts}`
|
||||
* Add missing `project_context` references to workflows for consistency
|
||||
- Remove alias variables from Phase 4 workflows, use canonical `{implementation_artifacts}` and `{planning_artifacts}`
|
||||
- Add missing `project_context` references to workflows for consistency
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* Add post-install notes documentation for modules
|
||||
* Improve project-context documentation and fix folder structure
|
||||
* Add BMad Builder link to index for extenders
|
||||
- Add post-install notes documentation for modules
|
||||
- Improve project-context documentation and fix folder structure
|
||||
- Add BMad Builder link to index for extenders
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -162,43 +163,43 @@ V6 Stable Release! The End of Beta!
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* **Non-Interactive Installation** — Added `--directory`, `--modules`, `--tools`, `--custom-content`, `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`, and `-y/--yes` flags for CI/CD automation (#1520)
|
||||
* **CSV File Reference Validation** — Extended validator to scan `.csv` files for broken workflow references, checking 501 references across 212 files (#1573)
|
||||
* **Kiro IDE Support** — Replaced broken custom installer with config-driven templates using `#[[file:...]]` syntax and `inclusion: manual` frontmatter (#1589)
|
||||
* **OpenCode Template Consolidation** — Combined split templates with `mode: primary` frontmatter for Tab-switching support, fixing agent discovery (#1556)
|
||||
* **Modules Reference Page** — Added official external modules reference documentation (#1540)
|
||||
- **Non-Interactive Installation** — Added `--directory`, `--modules`, `--tools`, `--custom-content`, `--user-name`, `--communication-language`, `--document-output-language`, `--output-folder`, and `-y/--yes` flags for CI/CD automation (#1520)
|
||||
- **CSV File Reference Validation** — Extended validator to scan `.csv` files for broken workflow references, checking 501 references across 212 files (#1573)
|
||||
- **Kiro IDE Support** — Replaced broken custom installer with config-driven templates using `#[[file:...]]` syntax and `inclusion: manual` frontmatter (#1589)
|
||||
- **OpenCode Template Consolidation** — Combined split templates with `mode: primary` frontmatter for Tab-switching support, fixing agent discovery (#1556)
|
||||
- **Modules Reference Page** — Added official external modules reference documentation (#1540)
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* **Installer Streamlining** — Removed "None - Skip module installation" option, eliminated ~100 lines of dead code, and added ESM/.cjs support for module installers (#1590)
|
||||
* **CodeRabbit Workflow** — Changed `pull_request` to `pull_request_target` to fix 403 errors and enable reviews on fork PRs (#1583)
|
||||
* **Party Mode Return Protocol** — Added RETURN PROTOCOL to prevent lost-in-the-middle failures after Party Mode completes (#1569)
|
||||
* **Spacebar Toggle** — Fixed SPACE key not working in autocomplete multiselect prompts for tool/IDE selection (#1557)
|
||||
* **OpenCode Agent Routing** — Fixed agents installing to wrong directory by adding `targets` array for routing `.opencode/agent/` vs `.opencode/command/` (#1549)
|
||||
* **Technical Research Workflow** — Fixed step-05 routing to step-06 and corrected `stepsCompleted` values (#1547)
|
||||
* **Forbidden Variable Removal** — Removed `workflow_path` variable from 16 workflow step files (#1546)
|
||||
* **Kilo Installer** — Fixed YAML formatting issues by trimming activation header and converting to yaml.parse/stringify (#1537)
|
||||
* **bmad-help** — Now reads project-specific docs and respects `communication_language` setting (#1535)
|
||||
* **Cache Errors** — Removed `--prefer-offline` npm flag to prevent stale cache errors during installation (#1531)
|
||||
- **Installer Streamlining** — Removed "None - Skip module installation" option, eliminated ~100 lines of dead code, and added ESM/.cjs support for module installers (#1590)
|
||||
- **CodeRabbit Workflow** — Changed `pull_request` to `pull_request_target` to fix 403 errors and enable reviews on fork PRs (#1583)
|
||||
- **Party Mode Return Protocol** — Added RETURN PROTOCOL to prevent lost-in-the-middle failures after Party Mode completes (#1569)
|
||||
- **Spacebar Toggle** — Fixed SPACE key not working in autocomplete multiselect prompts for tool/IDE selection (#1557)
|
||||
- **OpenCode Agent Routing** — Fixed agents installing to wrong directory by adding `targets` array for routing `.opencode/agent/` vs `.opencode/command/` (#1549)
|
||||
- **Technical Research Workflow** — Fixed step-05 routing to step-06 and corrected `stepsCompleted` values (#1547)
|
||||
- **Forbidden Variable Removal** — Removed `workflow_path` variable from 16 workflow step files (#1546)
|
||||
- **Kilo Installer** — Fixed YAML formatting issues by trimming activation header and converting to yaml.parse/stringify (#1537)
|
||||
- **bmad-help** — Now reads project-specific docs and respects `communication_language` setting (#1535)
|
||||
- **Cache Errors** — Removed `--prefer-offline` npm flag to prevent stale cache errors during installation (#1531)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* **Complete @clack/prompts Migration** — Migrated 24 files from legacy libraries (ora, chalk, boxen, figlet, etc.), replaced ~100 console.log+chalk calls, consolidated installer output to single spinner, and removed 5 dependencies (#1586)
|
||||
* **Downloads Page Removal** — Removed downloads page, bundle generation, and archiver dependency in favor of GitHub's native archives (#1577)
|
||||
* **Workflow Verb Standardization** — Replaced "invoke/run" with "load and follow/load" in review workflow prompts (#1570)
|
||||
* **Documentation Language** — Renamed "brownfield" to "established projects" and flattened directory structure for accessibility (#1539)
|
||||
- **Complete @clack/prompts Migration** — Migrated 24 files from legacy libraries (ora, chalk, boxen, figlet, etc.), replaced ~100 console.log+chalk calls, consolidated installer output to single spinner, and removed 5 dependencies (#1586)
|
||||
- **Downloads Page Removal** — Removed downloads page, bundle generation, and archiver dependency in favor of GitHub's native archives (#1577)
|
||||
- **Workflow Verb Standardization** — Replaced "invoke/run" with "load and follow/load" in review workflow prompts (#1570)
|
||||
- **Documentation Language** — Renamed "brownfield" to "established projects" and flattened directory structure for accessibility (#1539)
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* **Comprehensive Site Review** — Fixed broken directory tree diagram, corrected grammar/capitalization, added SEO descriptions, and reordered how-to guides (#1578)
|
||||
* **SEO Metadata** — Added description front matter to 9 documentation pages for search engine optimization (#1566)
|
||||
* **PR Template** — Added pull request template for consistent PR descriptions (#1554)
|
||||
* **Manual Release Cleanup** — Removed broken manual-release workflow and related scripts (#1576)
|
||||
- **Comprehensive Site Review** — Fixed broken directory tree diagram, corrected grammar/capitalization, added SEO descriptions, and reordered how-to guides (#1578)
|
||||
- **SEO Metadata** — Added description front matter to 9 documentation pages for search engine optimization (#1566)
|
||||
- **PR Template** — Added pull request template for consistent PR descriptions (#1554)
|
||||
- **Manual Release Cleanup** — Removed broken manual-release workflow and related scripts (#1576)
|
||||
|
||||
### 🔧 Maintenance
|
||||
|
||||
* **Dual-Mode AI Code Review** — Configured Augment Code (audit mode) and CodeRabbit (adversarial mode) for improved code quality (#1511)
|
||||
* **Package-Lock Sync** — Cleaned up 471 lines of orphaned dependencies after archiver removal (#1580)
|
||||
- **Dual-Mode AI Code Review** — Configured Augment Code (audit mode) and CodeRabbit (adversarial mode) for improved code quality (#1511)
|
||||
- **Package-Lock Sync** — Cleaned up 471 lines of orphaned dependencies after archiver removal (#1580)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -213,14 +214,14 @@ V6 Stable Release! The End of Beta!
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* **Slash Command Workflow Access** — Research and PRD workflows now accessible via direct slash commands: `/domain-research`, `/market-research`, `/technical-research`, `/create-prd`, `/edit-prd`, `/validate-prd` (bd620e38, 731bee26)
|
||||
* **Version Checking** — CLI now checks npm for newer versions and displays a warning banner when updates are available (d37ee7f2)
|
||||
- **Slash Command Workflow Access** — Research and PRD workflows now accessible via direct slash commands: `/domain-research`, `/market-research`, `/technical-research`, `/create-prd`, `/edit-prd`, `/validate-prd` (bd620e38, 731bee26)
|
||||
- **Version Checking** — CLI now checks npm for newer versions and displays a warning banner when updates are available (d37ee7f2)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* **Workflow File Splitting** — Split monolithic `workflow.md` files into specific `workflow-*.md` files for individual workflow invocation (bd620e38)
|
||||
* **Installer Multi-Workflow Support** — Installer manifest generator now supports `workflow-*.md` pattern, allowing multiple workflow files per directory (731bee26)
|
||||
* **Internal Skill Renaming** — Renamed internal project skills to use `bmad-os-` prefix for consistent naming (5276d58b)
|
||||
- **Workflow File Splitting** — Split monolithic `workflow.md` files into specific `workflow-*.md` files for individual workflow invocation (bd620e38)
|
||||
- **Installer Multi-Workflow Support** — Installer manifest generator now supports `workflow-*.md` pattern, allowing multiple workflow files per directory (731bee26)
|
||||
- **Internal Skill Renaming** — Renamed internal project skills to use `bmad-os-` prefix for consistent naming (5276d58b)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -237,33 +238,33 @@ V6 Stable Release! The End of Beta!
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* **Cross-File Reference Validator** — Validates ~483 references across ~217 source files, detecting absolute path leaks and broken references (PR #1494)
|
||||
* **AutocompleteMultiselect Prompt** — Upgraded `@clack/prompts` to v1.0.0 with custom searchable multiselect, Tab-to-fill-placeholder behavior, and improved tool/IDE selection UX (PR #1514)
|
||||
* **OT Domains** — Added `process_control` and `building_automation` domains with high complexity ratings (PR #1510)
|
||||
* **Documentation Reference Pages** — Added `docs/reference/agents.md`, `commands.md`, and `testing.md` (PR #1525)
|
||||
- **Cross-File Reference Validator** — Validates ~483 references across ~217 source files, detecting absolute path leaks and broken references (PR #1494)
|
||||
- **AutocompleteMultiselect Prompt** — Upgraded `@clack/prompts` to v1.0.0 with custom searchable multiselect, Tab-to-fill-placeholder behavior, and improved tool/IDE selection UX (PR #1514)
|
||||
- **OT Domains** — Added `process_control` and `building_automation` domains with high complexity ratings (PR #1510)
|
||||
- **Documentation Reference Pages** — Added `docs/reference/agents.md`, `commands.md`, and `testing.md` (PR #1525)
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* **Critical Installer Fixes** — Fixed CRLF line ending parsing on Windows, Gemini CLI TOML support, file extension preservation, Codex task generation, Windows path handling, and CSV parsing (PR #1492)
|
||||
* **Double Tool Questioning** — Removed redundant tool questioning during installation (df176d42)
|
||||
* **QA Agent Rename** — Renamed Quinn agent to `qa` for naming consistency (PR #1508)
|
||||
* **Documentation Organization** — Fixed documentation ordering and links, hide BMGD pages from main LLM docs (PR #1525)
|
||||
- **Critical Installer Fixes** — Fixed CRLF line ending parsing on Windows, Gemini CLI TOML support, file extension preservation, Codex task generation, Windows path handling, and CSV parsing (PR #1492)
|
||||
- **Double Tool Questioning** — Removed redundant tool questioning during installation (df176d42)
|
||||
- **QA Agent Rename** — Renamed Quinn agent to `qa` for naming consistency (PR #1508)
|
||||
- **Documentation Organization** — Fixed documentation ordering and links, hide BMGD pages from main LLM docs (PR #1525)
|
||||
|
||||
### ♻️ Refactoring
|
||||
|
||||
* **Excalidraw/Flattener Removal** — Removed dead artifacts no longer supported beyond beta: Excalidraw workflows, flattener tool, and 12+ diagram creation workflows (-3,798 lines) (f699a368)
|
||||
* **Centralized Constants** — Centralized `BMAD_FOLDER_NAME` to reduce hardcoded strings (PR #1492)
|
||||
* **Cross-Platform Paths** — Fixed path separator inconsistencies in agent IDs (PR #1492)
|
||||
- **Excalidraw/Flattener Removal** — Removed dead artifacts no longer supported beyond beta: Excalidraw workflows, flattener tool, and 12+ diagram creation workflows (-3,798 lines) (f699a368)
|
||||
- **Centralized Constants** — Centralized `BMAD_FOLDER_NAME` to reduce hardcoded strings (PR #1492)
|
||||
- **Cross-Platform Paths** — Fixed path separator inconsistencies in agent IDs (PR #1492)
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* **BMGD Diataxis Refactor** — Refactored BMGD documentation using Diataxis principles for better organization (PR #1502)
|
||||
* **Generate Project Context** — Restored `generate-project-context` workflow for brownfield project analysis (PR #1491)
|
||||
- **BMGD Diataxis Refactor** — Refactored BMGD documentation using Diataxis principles for better organization (PR #1502)
|
||||
- **Generate Project Context** — Restored `generate-project-context` workflow for brownfield project analysis (PR #1491)
|
||||
|
||||
### 🔧 Maintenance
|
||||
|
||||
* **Dependency Updates** — Upgraded `@clack/prompts` from v0.11.0 to v1.0.0 and added `@clack/core` (PR #1514)
|
||||
* **CI Integration** — Added `validate:refs` to CI quality workflow with warning annotations (PR #1494)
|
||||
- **Dependency Updates** — Upgraded `@clack/prompts` from v0.11.0 to v1.0.0 and added `@clack/core` (PR #1514)
|
||||
- **CI Integration** — Added `validate:refs` to CI quality workflow with warning annotations (PR #1494)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -271,31 +272,31 @@ V6 Stable Release! The End of Beta!
|
|||
|
||||
### 🎁 Features
|
||||
|
||||
* **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent
|
||||
* **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow
|
||||
- **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent
|
||||
- **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
||||
* **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476)
|
||||
* **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481)
|
||||
* **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486)
|
||||
* **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module
|
||||
* **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487)
|
||||
* **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498)
|
||||
* **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499)
|
||||
* **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501)
|
||||
* **Fix agent scan and help CSV files** — Correct module-help.csv entries
|
||||
* **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437)
|
||||
- **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476)
|
||||
- **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481)
|
||||
- **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486)
|
||||
- **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module
|
||||
- **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487)
|
||||
- **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498)
|
||||
- **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499)
|
||||
- **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501)
|
||||
- **Fix agent scan and help CSV files** — Correct module-help.csv entries
|
||||
- **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437)
|
||||
|
||||
### 📚 Documentation
|
||||
|
||||
* **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505)
|
||||
* **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506)
|
||||
- **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505)
|
||||
- **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506)
|
||||
|
||||
### 🔧 Maintenance
|
||||
|
||||
* **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility
|
||||
* **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates
|
||||
- **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility
|
||||
- **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -319,13 +320,16 @@ V6 Stable Release! The End of Beta!
|
|||
### 🔧 Features & Improvements
|
||||
|
||||
**Module Changes:**
|
||||
|
||||
- **TEA Module Moved to External** (#1430, #1443): The TEA module is now external. SDET module added with a single "automate" workflow focused on test automation
|
||||
- **SDET Module**: New module with streamlined test automation capabilities
|
||||
|
||||
**IDE Integration:**
|
||||
|
||||
- **Gemini CLI TOML Format** (#1431): Previous update accidentally switched Gemini to md instead of toml.
|
||||
|
||||
**Sprint Status:**
|
||||
|
||||
- **Default project_key** (#1446): File-system based sprint status now uses a default project_key so certain LLMs do not complain
|
||||
|
||||
### 🐛 Bug Fixes
|
||||
|
|
@ -695,7 +699,7 @@ Located in `src/modules/bmb/workflows/agent/data/`:
|
|||
- **Removed document-sharding-guide.md** from docs root (moved to core)
|
||||
- **Removed web-bundles-gemini-gpt-guide.md** - Consolidated into web-bundles/index.md
|
||||
- **Removed getting-started/installation.md** - Migrated to bmad-core-concepts
|
||||
- **Removed all ide-info/*.md files** - Consolidated into web-bundles documentation
|
||||
- **Removed all ide-info/\*.md files** - Consolidated into web-bundles documentation
|
||||
|
||||
### 🔧 Create-Tech-Spec Sharded Conversion
|
||||
|
||||
|
|
@ -826,6 +830,7 @@ Located in `src/modules/bmb/workflows/agent/data/`:
|
|||
- **Installer Cleanup**: Removed unused configuration code from BMM installer
|
||||
|
||||
**Planning Artifacts Path:**
|
||||
|
||||
- Default: `planning_artifacts/` (configurable in module.yaml)
|
||||
- Previous: `docs/`
|
||||
- Benefit: Clear separation between planning work and permanent documentation
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Documentation Style Guide"
|
||||
title: 'Documentation Style Guide'
|
||||
description: Project-specific documentation conventions based on Google style and Diataxis structure
|
||||
---
|
||||
|
||||
|
|
@ -55,15 +55,15 @@ Critical warnings only — data loss, security issues
|
|||
```md
|
||||
| Phase | Name | What Happens |
|
||||
| ----- | -------- | -------------------------------------------- |
|
||||
| 1 | Analysis | Brainstorm, research *(optional)* |
|
||||
| 2 | Planning | Requirements — PRD or tech-spec *(required)* |
|
||||
| 1 | Analysis | Brainstorm, research _(optional)_ |
|
||||
| 2 | Planning | Requirements — PRD or tech-spec _(required)_ |
|
||||
```
|
||||
|
||||
**Skills:**
|
||||
|
||||
```md
|
||||
| Skill | Agent | Purpose |
|
||||
| ------------ | ------- | ------------------------------------ |
|
||||
| -------------------- | ------- | ------------------------------------ |
|
||||
| `bmad-brainstorming` | Analyst | Brainstorm a new project |
|
||||
| `bmad-create-prd` | PM | Create Product Requirements Document |
|
||||
```
|
||||
|
|
@ -353,7 +353,7 @@ Only for BMad Method and Enterprise tracks. Quick Flow skips to implementation.
|
|||
|
||||
### Can I change my plan later?
|
||||
|
||||
Yes. The SM agent has a `bmad-correct-course` workflow for handling scope changes.
|
||||
Yes. The ADL agent has a `bmad-correct-course` workflow for handling scope changes.
|
||||
|
||||
**Have a question not answered here?** [Open an issue](...) or ask in [Discord](...).
|
||||
```
|
||||
|
|
|
|||
|
|
@ -16,11 +16,11 @@ This page lists the default BMM (Agile suite) agents that install with BMad Meth
|
|||
- QA (Quinn) is the lightweight test automation agent in BMM. The full Test Architect (TEA) lives in its own module.
|
||||
|
||||
| Agent | Skill ID | Triggers | Primary workflows |
|
||||
| --------------------------- | -------------------- | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
| --------------------------- | ------------------ | ---------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
| Analyst (Mary) | `bmad-analyst` | `BP`, `RS`, `CB`, `DP` | Brainstorm Project, Research, Create Brief, Document Project |
|
||||
| Product Manager (John) | `bmad-pm` | `CP`, `VP`, `EP`, `CE`, `IR`, `CC` | Create/Validate/Edit PRD, Create Epics and Stories, Implementation Readiness, Correct Course |
|
||||
| Architect (Winston) | `bmad-architect` | `CA`, `IR` | Create Architecture, Implementation Readiness |
|
||||
| Scrum Master (Bob) | `bmad-sm` | `SP`, `CS`, `ER`, `CC` | Sprint Planning, Create Story, Epic Retrospective, Correct Course |
|
||||
| Agile Delivery Lead (Bob) | `bmad-adl` | `SP`, `CS`, `ER`, `CC` | Sprint Planning, Create Story, Epic Retrospective, Correct Course |
|
||||
| Developer (Amelia) | `bmad-dev` | `DS`, `CR` | Dev Story, Code Review |
|
||||
| QA Engineer (Quinn) | `bmad-qa` | `QA` | Automate (generate tests for existing features) |
|
||||
| Quick Flow Solo Dev (Barry) | `bmad-master` | `QS`, `QD`, `CR` | Quick Spec, Quick Dev, Code Review |
|
||||
|
|
@ -42,7 +42,7 @@ Examples: `CP` (Create PRD), `DS` (Dev Story), `CA` (Create Architecture), `QS`
|
|||
Some triggers start a free-form conversation instead of a structured workflow. These expect you to describe what you need alongside the trigger code.
|
||||
|
||||
| Agent | Trigger | What to provide |
|
||||
| --- | --- | --- |
|
||||
| ------------------------ | ------- | -------------------------------------------------------- |
|
||||
| Technical Writer (Paige) | `WD` | Description of the document to write |
|
||||
| Technical Writer (Paige) | `US` | Preferences or conventions to add to standards |
|
||||
| Technical Writer (Paige) | `MG` | Diagram description and type (sequence, flowchart, etc.) |
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Skills are pre-built prompts that load agents, run workflows, or execute tasks i
|
|||
BMad offers two ways to start work, and they serve different purposes.
|
||||
|
||||
| Mechanism | How you invoke it | What happens |
|
||||
| --- | --- | --- |
|
||||
| ---------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
|
||||
| **Skill** | Type the skill name (e.g. `bmad-help`) in your IDE | Directly loads an agent, runs a workflow, or executes a task |
|
||||
| **Agent menu trigger** | Load an agent first, then type a short code (e.g. `DS`) | The agent interprets the code and starts the matching workflow while staying in character |
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ When you run `npx bmad-method install`, the installer reads the manifests for ev
|
|||
The installer uses templates for each skill type:
|
||||
|
||||
| Skill type | What the generated file does |
|
||||
| --- | --- |
|
||||
| ------------------ | ------------------------------------------------------------------------ |
|
||||
| **Agent launcher** | Loads the agent persona file, activates its menu, and stays in character |
|
||||
| **Workflow skill** | Loads the workflow config and follows its steps |
|
||||
| **Task skill** | Loads a standalone task file and follows its instructions |
|
||||
|
|
@ -40,7 +40,7 @@ If you add or remove modules, run the installer again. It regenerates all skill
|
|||
The installer writes skill files into an IDE-specific directory inside your project. The exact path depends on which IDE you selected during installation.
|
||||
|
||||
| IDE / CLI | Skills directory |
|
||||
| --- | --- |
|
||||
| ----------- | -------------------------------------------- |
|
||||
| Claude Code | `.claude/skills/` |
|
||||
| Cursor | `.cursor/skills/` |
|
||||
| Windsurf | `.windsurf/skills/` |
|
||||
|
|
@ -78,11 +78,11 @@ The generated skill directories in your project are the canonical list. Open the
|
|||
Agent skills load a specialized AI persona with a defined role, communication style, and menu of workflows. Once loaded, the agent stays in character and responds to menu triggers.
|
||||
|
||||
| Example skill | Agent | Role |
|
||||
| --- | --- | --- |
|
||||
| ---------------- | ------------------------- | ------------------------------------------------- |
|
||||
| `bmad-dev` | Amelia (Developer) | Implements stories with strict adherence to specs |
|
||||
| `bmad-pm` | John (Product Manager) | Creates and validates PRDs |
|
||||
| `bmad-architect` | Winston (Architect) | Designs system architecture |
|
||||
| `bmad-sm` | Bob (Scrum Master) | Manages sprints and stories |
|
||||
| `bmad-adl` | Bob (Agile Delivery Lead) | Manages sprints and stories |
|
||||
|
||||
See [Agents](./agents.md) for the full list of default agents and their triggers.
|
||||
|
||||
|
|
@ -91,7 +91,7 @@ See [Agents](./agents.md) for the full list of default agents and their triggers
|
|||
Workflow skills run a structured, multi-step process without loading an agent persona first. They load a workflow configuration and follow its steps.
|
||||
|
||||
| Example skill | Purpose |
|
||||
| --- | --- |
|
||||
| ------------------------------- | -------------------------------------- |
|
||||
| `bmad-create-prd` | Create a Product Requirements Document |
|
||||
| `bmad-create-architecture` | Design system architecture |
|
||||
| `bmad-create-epics-and-stories` | Create epics and stories |
|
||||
|
|
@ -127,7 +127,7 @@ bmad-help I'm stuck on the PRD workflow
|
|||
#### Other Tasks and Tools
|
||||
|
||||
| Example skill | Purpose |
|
||||
| --- | --- |
|
||||
| ----------------------------- | ------------------------------------------------- |
|
||||
| `bmad-shard-doc` | Split a large markdown file into smaller sections |
|
||||
| `bmad-index-docs` | Index project documentation |
|
||||
| `bmad-editorial-review-prose` | Review document prose quality |
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Getting Started"
|
||||
title: 'Getting Started'
|
||||
description: Install BMad and build your first project
|
||||
---
|
||||
|
||||
|
|
@ -14,11 +14,12 @@ Build software faster using AI-powered workflows with specialized agents that gu
|
|||
- Use agents and workflows effectively
|
||||
|
||||
:::note[Prerequisites]
|
||||
|
||||
- **Node.js 20+** — Required for the installer
|
||||
- **Git** — Recommended for version control
|
||||
- **AI-powered IDE** — Claude Code, Cursor, or similar
|
||||
- **A project idea** — Even a simple one works for learning
|
||||
:::
|
||||
:::
|
||||
|
||||
:::tip[The Easiest Path]
|
||||
**Install** → `npx bmad-method install`
|
||||
|
|
@ -50,6 +51,7 @@ bmad-help I have an idea for a SaaS product, I already know all the features I w
|
|||
```
|
||||
|
||||
BMad-Help will respond with:
|
||||
|
||||
- What's recommended for your situation
|
||||
- What the first required task is
|
||||
- What the rest of the process looks like
|
||||
|
|
@ -68,9 +70,9 @@ BMad helps you build software through guided workflows with specialized AI agent
|
|||
|
||||
| Phase | Name | What Happens |
|
||||
| ----- | -------------- | --------------------------------------------------- |
|
||||
| 1 | Analysis | Brainstorming, research, product brief *(optional)* |
|
||||
| 1 | Analysis | Brainstorming, research, product brief _(optional)_ |
|
||||
| 2 | Planning | Create requirements (PRD or tech-spec) |
|
||||
| 3 | Solutioning | Design architecture *(BMad Method/Enterprise only)* |
|
||||
| 3 | Solutioning | Design architecture _(BMad Method/Enterprise only)_ |
|
||||
| 4 | Implementation | Build epic by epic, story by story |
|
||||
|
||||
**[Open the Workflow Map](../reference/workflow-map.md)** to explore phases, workflows, and context management.
|
||||
|
|
@ -100,6 +102,7 @@ If you want the newest prerelease build instead of the default release channel,
|
|||
When prompted to select modules, choose **BMad Method**.
|
||||
|
||||
The installer creates two folders:
|
||||
|
||||
- `_bmad/` — agents, workflows, tasks, and configuration
|
||||
- `_bmad-output/` — empty for now, but this is where your artifacts will be saved
|
||||
|
||||
|
|
@ -134,6 +137,7 @@ Create it manually at `_bmad-output/project-context.md` or generate it after arc
|
|||
### Phase 1: Analysis (Optional)
|
||||
|
||||
All workflows in this phase are optional:
|
||||
|
||||
- **brainstorming** (`bmad-brainstorming`) — Guided ideation
|
||||
- **research** (`bmad-research`) — Market and technical research
|
||||
- **create-product-brief** (`bmad-create-product-brief`) — Recommended foundation document
|
||||
|
|
@ -141,11 +145,13 @@ All workflows in this phase are optional:
|
|||
### Phase 2: Planning (Required)
|
||||
|
||||
**For BMad Method and Enterprise tracks:**
|
||||
|
||||
1. Invoke the **PM agent** (`bmad-pm`) in a new chat
|
||||
2. Run the `bmad-create-prd` workflow (`bmad-create-prd`)
|
||||
3. Output: `PRD.md`
|
||||
|
||||
**For Quick Flow track:**
|
||||
|
||||
- Use the `bmad-quick-spec` workflow (`bmad-quick-spec`) instead of PRD, then skip to implementation
|
||||
|
||||
:::note[UX Design (Optional)]
|
||||
|
|
@ -155,6 +161,7 @@ If your project has a user interface, invoke the **UX-Designer agent** (`bmad-ux
|
|||
### Phase 3: Solutioning (BMad Method/Enterprise)
|
||||
|
||||
**Create Architecture**
|
||||
|
||||
1. Invoke the **Architect agent** (`bmad-architect`) in a new chat
|
||||
2. Run `bmad-create-architecture` (`bmad-create-architecture`)
|
||||
3. Output: Architecture document with technical decisions
|
||||
|
|
@ -162,14 +169,15 @@ If your project has a user interface, invoke the **UX-Designer agent** (`bmad-ux
|
|||
**Create Epics and Stories**
|
||||
|
||||
:::tip[V6 Improvement]
|
||||
Epics and stories are now created *after* architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down.
|
||||
Epics and stories are now created _after_ architecture. This produces better quality stories because architecture decisions (database, API patterns, tech stack) directly affect how work should be broken down.
|
||||
:::
|
||||
|
||||
1. Invoke the **PM agent** (`bmad-pm`) in a new chat
|
||||
2. Run `bmad-create-epics-and-stories` (`bmad-create-epics-and-stories`)
|
||||
3. The workflow uses both PRD and Architecture to create technically-informed stories
|
||||
|
||||
**Implementation Readiness Check** *(Highly Recommended)*
|
||||
**Implementation Readiness Check** _(Highly Recommended)_
|
||||
|
||||
1. Invoke the **Architect agent** (`bmad-architect`) in a new chat
|
||||
2. Run `bmad-check-implementation-readiness` (`bmad-check-implementation-readiness`)
|
||||
3. Validates cohesion across all planning documents
|
||||
|
|
@ -180,19 +188,19 @@ Once planning is complete, move to implementation. **Each workflow should run in
|
|||
|
||||
### Initialize Sprint Planning
|
||||
|
||||
Invoke the **SM agent** (`bmad-sm`) and run `bmad-sprint-planning` (`bmad-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
|
||||
Invoke the **ADL agent** (`bmad-adl`) and run `bmad-sprint-planning` (`bmad-sprint-planning`). This creates `sprint-status.yaml` to track all epics and stories.
|
||||
|
||||
### The Build Cycle
|
||||
|
||||
For each story, repeat this cycle with fresh chats:
|
||||
|
||||
| Step | Agent | Workflow | Command | Purpose |
|
||||
| ---- | ----- | -------------- | -------------------------- | ---------------------------------- |
|
||||
| 1 | SM | `bmad-create-story` | `bmad-create-story` | Create story file from epic |
|
||||
| ---- | ----- | ------------------- | ------------------- | ---------------------------------- |
|
||||
| 1 | ADL | `bmad-create-story` | `bmad-create-story` | Create story file from epic |
|
||||
| 2 | DEV | `bmad-dev-story` | `bmad-dev-story` | Implement the story |
|
||||
| 3 | DEV | `bmad-code-review` | `bmad-code-review` | Quality validation *(recommended)* |
|
||||
| 3 | DEV | `bmad-code-review` | `bmad-code-review` | Quality validation _(recommended)_ |
|
||||
|
||||
After completing all stories in an epic, invoke the **SM agent** (`bmad-sm`) and run `bmad-retrospective` (`bmad-retrospective`).
|
||||
After completing all stories in an epic, invoke the **ADL agent** (`bmad-adl`) and run `bmad-retrospective` (`bmad-retrospective`).
|
||||
|
||||
## What You've Accomplished
|
||||
|
||||
|
|
@ -222,15 +230,15 @@ your-project/
|
|||
## Quick Reference
|
||||
|
||||
| Workflow | Command | Agent | Purpose |
|
||||
| ------------------------------------- | ------------------------------------------ | --------- | ----------------------------------------------- |
|
||||
| ------------------------------------- | ------------------------------------- | --------- | ------------------------------------------ |
|
||||
| **`bmad-help`** ⭐ | `bmad-help` | Any | **Your intelligent guide — ask anything!** |
|
||||
| `bmad-create-prd` | `bmad-create-prd` | PM | Create Product Requirements Document |
|
||||
| `bmad-create-architecture` | `bmad-create-architecture` | Architect | Create architecture document |
|
||||
| `bmad-generate-project-context` | `bmad-generate-project-context` | Analyst | Create project context file |
|
||||
| `bmad-create-epics-and-stories` | `bmad-create-epics-and-stories` | PM | Break down PRD into epics |
|
||||
| `bmad-check-implementation-readiness` | `bmad-check-implementation-readiness` | Architect | Validate planning cohesion |
|
||||
| `bmad-sprint-planning` | `bmad-sprint-planning` | SM | Initialize sprint tracking |
|
||||
| `bmad-create-story` | `bmad-create-story` | SM | Create a story file |
|
||||
| `bmad-sprint-planning` | `bmad-sprint-planning` | ADL | Initialize sprint tracking |
|
||||
| `bmad-create-story` | `bmad-create-story` | ADL | Create a story file |
|
||||
| `bmad-dev-story` | `bmad-dev-story` | DEV | Implement a story |
|
||||
| `bmad-code-review` | `bmad-code-review` | DEV | Review implemented code |
|
||||
|
||||
|
|
@ -240,7 +248,7 @@ your-project/
|
|||
Only for BMad Method and Enterprise tracks. Quick Flow skips from tech-spec to implementation.
|
||||
|
||||
**Can I change my plan later?**
|
||||
Yes. The SM agent has a `bmad-correct-course` workflow (`bmad-correct-course`) for handling scope changes.
|
||||
Yes. The ADL agent has a `bmad-correct-course` workflow (`bmad-correct-course`) for handling scope changes.
|
||||
|
||||
**What if I want to brainstorm first?**
|
||||
Invoke the Analyst agent (`bmad-analyst`) and run `bmad-brainstorming` (`bmad-brainstorming`) before starting your PRD.
|
||||
|
|
@ -252,6 +260,7 @@ Not strictly. Once you learn the flow, you can run workflows directly using the
|
|||
|
||||
:::tip[First Stop: BMad-Help]
|
||||
**Invoke `bmad-help` anytime** — it's the fastest way to get unstuck. Ask it anything:
|
||||
|
||||
- "What should I do after installing?"
|
||||
- "I'm stuck on workflow X"
|
||||
- "What are my options for Y?"
|
||||
|
|
@ -266,10 +275,11 @@ BMad-Help inspects your project, detects what you've completed, and tells you ex
|
|||
## Key Takeaways
|
||||
|
||||
:::tip[Remember These]
|
||||
|
||||
- **Start with `bmad-help`** — Your intelligent guide that knows your project and options
|
||||
- **Always use fresh chats** — Start a new chat for each workflow
|
||||
- **Track matters** — Quick Flow uses quick-spec; Method/Enterprise need PRD and architecture
|
||||
- **BMad-Help runs automatically** — Every workflow ends with guidance on what's next
|
||||
:::
|
||||
:::
|
||||
|
||||
Ready to start? Install BMad, invoke `bmad-help`, and let your intelligent guide lead the way.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "Documentation Style Guide"
|
||||
title: 'Documentation Style Guide'
|
||||
description: Project-specific documentation conventions based on Google style and Diataxis structure
|
||||
---
|
||||
|
||||
|
|
@ -55,8 +55,8 @@ Critical warnings only — data loss, security issues
|
|||
```md
|
||||
| Phase | Name | What Happens |
|
||||
| ----- | -------- | -------------------------------------------- |
|
||||
| 1 | Analysis | Brainstorm, research *(optional)* |
|
||||
| 2 | Planning | Requirements — PRD or tech-spec *(required)* |
|
||||
| 1 | Analysis | Brainstorm, research _(optional)_ |
|
||||
| 2 | Planning | Requirements — PRD or tech-spec _(required)_ |
|
||||
```
|
||||
|
||||
**Commands:**
|
||||
|
|
@ -353,7 +353,7 @@ Only for BMad Method and Enterprise tracks. Quick Flow skips to implementation.
|
|||
|
||||
### Can I change my plan later?
|
||||
|
||||
Yes. The SM agent has a `correct-course` workflow for handling scope changes.
|
||||
Yes. The ADL agent has a `correct-course` workflow for handling scope changes.
|
||||
|
||||
**Have a question not answered here?** [Open an issue](...) or ask in [Discord](...).
|
||||
```
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "命令"
|
||||
title: '命令'
|
||||
description: BMad 斜杠命令参考——它们是什么、如何工作以及在哪里找到它们。
|
||||
sidebar:
|
||||
order: 3
|
||||
|
|
@ -12,7 +12,7 @@ sidebar:
|
|||
BMad 提供两种开始工作的方式，它们服务于不同的目的。
|
||||
|
||||
| 机制 | 调用方式 | 发生什么 |
|
||||
| --- | --- | --- |
|
||||
| -------------------- | ------------------------------------------- | -------------------------------------------------- |
|
||||
| **斜杠命令** | 在 IDE 中输入 `bmad-...` | 直接加载智能体、运行工作流或执行任务 |
|
||||
| **智能体菜单触发器** | 先加载智能体，然后输入简短代码（例如 `DS`） | 智能体解释代码并启动匹配的工作流，同时保持角色设定 |
|
||||
|
||||
|
|
@ -25,7 +25,7 @@ BMad 提供两种开始工作的方式，它们服务于不同的目的。
|
|||
安装程序为每种命令类型使用模板：
|
||||
|
||||
| 命令类型 | 生成的文件的作用 |
|
||||
| --- | --- |
|
||||
| ---------------- | ------------------------------------------------ |
|
||||
| **智能体启动器** | 加载智能体角色文件，激活其菜单，并保持角色设定 |
|
||||
| **工作流命令** | 加载工作流引擎（`workflow.xml`）并传递工作流配置 |
|
||||
| **任务命令** | 加载独立任务文件并遵循其指令 |
|
||||
|
|
@ -40,7 +40,7 @@ BMad 提供两种开始工作的方式，它们服务于不同的目的。
|
|||
安装程序将命令文件写入项目内 IDE 特定的目录中。确切路径取决于您在安装期间选择的 IDE。
|
||||
|
||||
| IDE / CLI | 命令目录 |
|
||||
| --- | --- |
|
||||
| ----------- | ------------------------------ |
|
||||
| Claude Code | `.claude/commands/` |
|
||||
| Cursor | `.cursor/commands/` |
|
||||
| Windsurf | `.windsurf/workflows/` |
|
||||
|
|
@ -77,11 +77,11 @@ BMad 提供两种开始工作的方式，它们服务于不同的目的。
|
|||
智能体命令加载具有定义角色、沟通风格和工作流菜单的专业化 AI 角色。加载后，智能体保持角色设定并响应菜单触发器。
|
||||
|
||||
| 示例命令 | 智能体 | 角色 |
|
||||
| --- | --- | --- |
|
||||
| -------------------------- | -------------------------- | -------------------- |
|
||||
| `bmad-agent-bmm-dev` | Amelia（开发者） | 严格按照规范实现故事 |
|
||||
| `bmad-agent-bmm-pm` | John（产品经理） | 创建和验证 PRD |
|
||||
| `bmad-agent-bmm-architect` | Winston（架构师） | 设计系统架构 |
|
||||
| `bmad-agent-bmm-sm` | Bob（Scrum Master） | 管理冲刺和故事 |
|
||||
| `bmad-agent-bmm-adl` | Bob（Agile Delivery Lead） | 管理冲刺和故事 |
|
||||
|
||||
参见[智能体](./agents.md)获取默认智能体及其触发器的完整列表。
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ BMad 提供两种开始工作的方式，它们服务于不同的目的。
|
|||
工作流命令运行结构化的多步骤过程，而无需先加载智能体角色。它们加载工作流引擎并传递特定的工作流配置。
|
||||
|
||||
| 示例命令 | 目的 |
|
||||
| --- | --- |
|
||||
| ------------------------------ | ------------------------ |
|
||||
| `bmad-bmm-create-prd` | 创建产品需求文档 |
|
||||
| `bmad-bmm-create-architecture` | 设计系统架构 |
|
||||
| `bmad-bmm-dev-story` | 实现故事 |
|
||||
|
|
@ -125,7 +125,7 @@ bmad-help 我在 PRD 工作流上卡住了
|
|||
#### 其他任务和工具
|
||||
|
||||
| 示例命令 | 目的 |
|
||||
| --- | --- |
|
||||
| ----------------------------- | ------------------------------------ |
|
||||
| `bmad-shard-doc` | 将大型 Markdown 文件拆分为较小的部分 |
|
||||
| `bmad-index-docs` | 索引项目文档 |
|
||||
| `bmad-editorial-review-prose` | 审查文档散文质量 |
|
||||
|
|
@ -135,7 +135,7 @@ bmad-help 我在 PRD 工作流上卡住了
|
|||
命令名称遵循可预测的模式。
|
||||
|
||||
| 模式 | 含义 | 示例 |
|
||||
| --- | --- | --- |
|
||||
| ---------------------------- | -------------- | --------------------- |
|
||||
| `bmad-agent-<module>-<name>` | 智能体启动器 | `bmad-agent-bmm-dev` |
|
||||
| `bmad-<module>-<workflow>` | 工作流命令 | `bmad-bmm-create-prd` |
|
||||
| `bmad-<name>` | 核心任务或工具 | `bmad-help` |
|
||||
|
|
@ -151,6 +151,7 @@ bmad-help 我在 PRD 工作流上卡住了
|
|||
**已删除模块的命令仍然出现。** 安装程序不会自动删除旧的命令文件。从 IDE 的命令目录中删除过时的文件，或删除整个命令目录并重新运行安装程序以获取一组干净的命令。
|
||||
|
||||
---
|
||||
|
||||
## 术语说明
|
||||
|
||||
- **slash command**：斜杠命令。以 `/` 开头的命令，用于在 IDE 中快速执行特定操作。
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: "快速入门"
|
||||
title: '快速入门'
|
||||
description: 安装 BMad 并构建你的第一个项目
|
||||
---
|
||||
|
||||
|
|
@ -14,11 +14,12 @@ description: 安装 BMad 并构建你的第一个项目
|
|||
- 有效使用智能体和工作流
|
||||
|
||||
:::note[前置条件]
|
||||
|
||||
- **Node.js 20+** — 安装程序必需
|
||||
- **Git** — 推荐用于版本控制
|
||||
- **AI 驱动的 IDE** — Claude Code、Cursor 或类似工具
|
||||
- **一个项目想法** — 即使是简单的想法也可以用于学习
|
||||
:::
|
||||
:::
|
||||
|
||||
:::tip[最简单的路径]
|
||||
**安装** → `npx bmad-method install`
|
||||
|
|
@ -50,6 +51,7 @@ bmad-help 我有一个 SaaS 产品的想法，我已经知道我想要的所有
|
|||
```
|
||||
|
||||
BMad-Help 将回应：
|
||||
|
||||
- 针对你的情况推荐什么
|
||||
- 第一个必需任务是什么
|
||||
- 其余流程是什么样的
|
||||
|
|
@ -67,10 +69,10 @@ BMad-Help 不仅回答问题 —— **它会在每个工作流结束时自动运
|
|||
BMad 通过带有专门 AI 智能体的引导工作流帮助你构建软件。该过程遵循四个阶段：
|
||||
|
||||
| 阶段 | 名称 | 发生什么 |
|
||||
| ---- | -------------- | -------------------------------------------------- |
|
||||
| 1 | 分析 | 头脑风暴、研究、产品简报 *（可选）* |
|
||||
| ---- | ------------ | ----------------------------------------------- |
|
||||
| 1 | 分析 | 头脑风暴、研究、产品简报 _（可选）_ |
|
||||
| 2 | 规划 | 创建需求（PRD 或技术规范） |
|
||||
| 3 | 解决方案设计 | 设计架构 *（仅限 BMad Method/Enterprise only）* |
|
||||
| 3 | 解决方案设计 | 设计架构 _（仅限 BMad Method/Enterprise only）_ |
|
||||
| 4 | 实现 | 逐个史诗、逐个故事地构建 |
|
||||
|
||||
**[打开工作流地图](../reference/workflow-map.md)** 以探索阶段、工作流和上下文管理。
|
||||
|
|
@ -78,7 +80,7 @@ BMad 通过带有专门 AI 智能体的引导工作流帮助你构建软件。
|
|||
根据项目的复杂性，BMad 提供三种规划路径：
|
||||
|
||||
| 路径 | 最适合 | 创建的文档 |
|
||||
| --------------- | ---------------------------------------------------- | --------------------------------------- |
|
||||
| --------------- | ------------------------------------------- | -------------------------- |
|
||||
| **Quick Flow** | 错误修复、简单功能、范围清晰（1-15 个故事） | 仅技术规范 |
|
||||
| **BMad Method** | 产品、平台、复杂功能（10-50+ 个故事） | PRD + 架构 + UX |
|
||||
| **Enterprise** | 合规、多租户系统（30+ 个故事） | PRD + 架构 + 安全 + DevOps |
|
||||
|
|
@ -98,6 +100,7 @@ npx bmad-method install
|
|||
当提示选择模块时，选择 **BMad Method**。
|
||||
|
||||
安装程序会创建两个文件夹：
|
||||
|
||||
- `_bmad/` — 智能体、工作流、任务和配置
|
||||
- `_bmad-output/` — 目前为空，但这是你的工件将被保存的地方
|
||||
|
||||
|
|
@ -132,6 +135,7 @@ BMad-Help 将检测你已完成的内容，并准确推荐下一步该做什么
|
|||
### 阶段 1：分析（可选）
|
||||
|
||||
此阶段中的所有工作流都是可选的：
|
||||
|
||||
- **头脑风暴**（`bmad-brainstorming`） — 引导式构思
|
||||
- **研究**（`bmad-bmm-research`） — 市场和技术研究
|
||||
- **创建产品简报**（`bmad-bmm-create-product-brief`） — 推荐的基础文档
|
||||
|
|
@ -139,11 +143,13 @@ BMad-Help 将检测你已完成的内容，并准确推荐下一步该做什么
|
|||
### 阶段 2：规划（必需）
|
||||
|
||||
**对于 BMad Method 和 Enterprise 路径：**
|
||||
|
||||
1. 在新对话中加载 **PM 智能体**（`bmad-agent-bmm-pm`）
|
||||
2. 运行 `prd` 工作流（`bmad-bmm-create-prd`）
|
||||
3. 输出：`PRD.md`
|
||||
|
||||
**对于 Quick Flow 路径：**
|
||||
|
||||
- 使用 `quick-spec` 工作流（`bmad-bmm-quick-spec`）代替 PRD，然后跳转到实现
|
||||
|
||||
:::note[UX 设计（可选）]
|
||||
|
|
@ -153,6 +159,7 @@ BMad-Help 将检测你已完成的内容，并准确推荐下一步该做什么
|
|||
### 阶段 3：解决方案设计（BMad Method/Enterprise）
|
||||
|
||||
**创建架构**
|
||||
|
||||
1. 在新对话中加载 **Architect 智能体**（`bmad-agent-bmm-architect`）
|
||||
2. 运行 `create-architecture`（`bmad-bmm-create-architecture`）
|
||||
3. 输出：包含技术决策的架构文档
|
||||
|
|
@ -167,7 +174,8 @@ BMad-Help 将检测你已完成的内容，并准确推荐下一步该做什么
|
|||
2. 运行 `create-epics-and-stories`（`bmad-bmm-create-epics-and-stories`）
|
||||
3. 工作流使用 PRD 和架构来创建技术信息丰富的故事
|
||||
|
||||
**实现就绪检查** *（强烈推荐）*
|
||||
**实现就绪检查** _（强烈推荐）_
|
||||
|
||||
1. 在新对话中加载 **Architect 智能体**（`bmad-agent-bmm-architect`）
|
||||
2. 运行 `check-implementation-readiness`（`bmad-bmm-check-implementation-readiness`）
|
||||
3. 验证所有规划文档之间的一致性
|
||||
|
|
@ -178,19 +186,19 @@ BMad-Help 将检测你已完成的内容，并准确推荐下一步该做什么
|
|||
|
||||
### 初始化冲刺规划
|
||||
|
||||
加载 **SM 智能体**（`bmad-agent-bmm-sm`）并运行 `sprint-planning`（`bmad-bmm-sprint-planning`）。这将创建 `sprint-status.yaml` 来跟踪所有史诗和故事。
|
||||
加载 **ADL 智能体**（`bmad-agent-bmm-adl`）并运行 `sprint-planning`（`bmad-bmm-sprint-planning`）。这将创建 `sprint-status.yaml` 来跟踪所有史诗和故事。
|
||||
|
||||
### 构建周期
|
||||
|
||||
对于每个故事，使用新对话重复此周期：
|
||||
|
||||
| 步骤 | 智能体 | 工作流 | 命令 | 目的 |
|
||||
| ---- | ------ | ------------ | ----------------------- | ------------------------------- |
|
||||
| 1 | SM | `create-story` | `bmad-bmm-create-story` | 从史诗创建故事文件 |
|
||||
| ---- | ------ | -------------- | ----------------------- | ------------------- |
|
||||
| 1 | ADL | `create-story` | `bmad-bmm-create-story` | 从史诗创建故事文件 |
|
||||
| 2 | DEV | `dev-story` | `bmad-bmm-dev-story` | 实现故事 |
|
||||
| 3 | DEV | `code-review` | `bmad-bmm-code-review` | 质量验证 *（推荐）* |
|
||||
| 3 | DEV | `code-review` | `bmad-bmm-code-review` | 质量验证 _（推荐）_ |
|
||||
|
||||
完成史诗中的所有故事后，加载 **SM 智能体**（`bmad-agent-bmm-sm`）并运行 `retrospective`（`bmad-bmm-retrospective`）。
|
||||
完成史诗中的所有故事后，加载 **ADL 智能体**（`bmad-agent-bmm-adl`）并运行 `retrospective`（`bmad-bmm-retrospective`）。
|
||||
|
||||
## 你已完成的工作
|
||||
|
||||
|
|
@ -220,7 +228,7 @@ your-project/
|
|||
## 快速参考
|
||||
|
||||
| 工作流 | 命令 | 智能体 | 目的 |
|
||||
| ----------------------------------- | --------------------------------------- | -------- | -------------------------------------------- |
|
||||
| -------------------------------- | ----------------------------------------- | --------- | -------------------------------------- |
|
||||
| **`help`** ⭐ | `bmad-help` | 任意 | **你的智能向导 —— 随时询问任何问题！** |
|
||||
| `prd` | `bmad-bmm-create-prd` | PM | 创建产品需求文档 |
|
||||
| `create-architecture` | `bmad-bmm-create-architecture` | Architect | 创建架构文档 |
|
||||
|
|
@ -250,6 +258,7 @@ your-project/
|
|||
|
||||
:::tip[第一站：BMad-Help]
|
||||
**随时运行 `bmad-help`** —— 这是摆脱困境的最快方式。问它任何问题：
|
||||
|
||||
- "安装后我应该做什么？"
|
||||
- "我在工作流 X 上卡住了"
|
||||
- "我在 Y 方面有什么选项？"
|
||||
|
|
@ -264,15 +273,17 @@ BMad-Help 检查你的项目，检测你已完成的内容，并确切地告诉
|
|||
## 关键要点
|
||||
|
||||
:::tip[记住这些]
|
||||
|
||||
- **从 `bmad-help` 开始** — 你的智能向导，了解你的项目和选项
|
||||
- **始终使用新对话** — 为每个工作流开始新对话
|
||||
- **路径很重要** — Quick Flow 使用 quick-spec；Method/Enterprise 需要 PRD 和架构
|
||||
- **BMad-Help 自动运行** — 每个工作流结束时都会提供下一步的指导
|
||||
:::
|
||||
:::
|
||||
|
||||
准备好开始了吗？安装 BMad，运行 `bmad-help`，让你的智能向导为你引路。
|
||||
|
||||
---
|
||||
|
||||
## 术语说明
|
||||
|
||||
- **agent**：智能体。在人工智能与编程文档中，指具备自主决策或执行能力的单元。
|
||||
|
|
|
|||
|
|
@ -1,18 +1,18 @@
|
|||
# Scrum Master Agent Definition
|
||||
# Agile Delivery Lead Agent Definition
|
||||
|
||||
agent:
|
||||
metadata:
|
||||
id: "_bmad/bmm/agents/sm.md"
|
||||
id: "_bmad/bmm/agents/adl.md"
|
||||
name: Bob
|
||||
title: Scrum Master
|
||||
title: Agile Delivery Lead
|
||||
icon: 🏃
|
||||
module: bmm
|
||||
capabilities: "sprint planning, story preparation, agile ceremonies, backlog management"
|
||||
hasSidecar: false
|
||||
|
||||
persona:
|
||||
role: Technical Scrum Master + Story Preparation Specialist
|
||||
identity: Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.
|
||||
role: Technical Agile Delivery Lead + Story Preparation Specialist
|
||||
identity: Certified Agile Delivery Lead with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.
|
||||
communication_style: "Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity."
|
||||
principles: |
|
||||
- I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions
|
||||
|
|
@ -28,10 +28,10 @@ quick-flow-solo-dev.agent.yaml:
|
|||
type: agent
|
||||
description: "Quick Flow Solo Dev for rapid spec creation and lean implementation"
|
||||
|
||||
sm.agent.yaml:
|
||||
canonicalId: bmad-sm
|
||||
adl.agent.yaml:
|
||||
canonicalId: bmad-adl
|
||||
type: agent
|
||||
description: "Scrum Master for sprint planning, story preparation, and agile ceremonies"
|
||||
description: "Agile Delivery Lead for sprint planning, story preparation, and agile ceremonies"
|
||||
|
||||
ux-designer.agent.yaml:
|
||||
canonicalId: bmad-ux-designer
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ bmm,anytime,Generate Project Context,GPC,,_bmad/bmm/workflows/generate-project-c
|
|||
bmm,anytime,Quick Spec,QS,,_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md,bmad-bmm-quick-spec,false,quick-flow-solo-dev,Create Mode,"Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method. Quick one-off tasks small changes simple apps brownfield additions to well established patterns utilities without extensive planning",planning_artifacts,"tech spec",
|
||||
bmm,anytime,Quick Dev,QD,,skill:bmad-quick-dev,bmad-bmm-quick-dev,false,quick-flow-solo-dev,Create Mode,"Quick one-off tasks small changes simple apps utilities without extensive planning - Do not suggest for potentially very complex things unless requested or if the user complains that they do not want to follow the extensive planning of the bmad method, unless the user is already working through the implementation phase and just requests a 1 off things not already in the plan",,,
|
||||
bmm,anytime,Quick Dev New Preview,QQ,,skill:bmad-quick-dev-new-preview,bmad-bmm-quick-dev-new-preview,false,quick-flow-solo-dev,Create Mode,"Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow",implementation_artifacts,"tech spec implementation",
|
||||
bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.md,bmad-bmm-correct-course,false,sm,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
|
||||
bmm,anytime,Correct Course,CC,,_bmad/bmm/workflows/4-implementation/correct-course/workflow.md,bmad-bmm-correct-course,false,adl,Create Mode,"Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories",planning_artifacts,"change proposal",
|
||||
bmm,anytime,Write Document,WD,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory. Multi-turn conversation with subprocess for research/review.",project-knowledge,"document",
|
||||
bmm,anytime,Update Standards,US,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Update agent memory documentation-standards.md with your specific preferences if you discover missing document conventions.",_bmad/_memory/tech-writer-sidecar,"standards",
|
||||
bmm,anytime,Mermaid Generate,MG,,_bmad/bmm/agents/tech-writer/tech-writer.agent.yaml,,false,tech-writer,,"Create a Mermaid diagram based on user description. Will suggest diagram types if not specified.",planning_artifacts,"mermaid diagram",
|
||||
|
|
@ -22,11 +22,11 @@ bmm,2-planning,Create UX,CU,30,_bmad/bmm/workflows/2-plan-workflows/create-ux-de
|
|||
bmm,3-solutioning,Create Architecture,CA,10,_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md,bmad-bmm-create-architecture,true,architect,Create Mode,"Guided Workflow to document technical decisions",planning_artifacts,architecture,
|
||||
bmm,3-solutioning,Create Epics and Stories,CE,30,_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md,bmad-bmm-create-epics-and-stories,true,pm,Create Mode,"Create the Epics and Stories Listing",planning_artifacts,"epics and stories",
|
||||
bmm,3-solutioning,Check Implementation Readiness,IR,70,_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md,bmad-bmm-check-implementation-readiness,true,architect,Validate Mode,"Ensure PRD UX Architecture and Epics Stories are aligned",planning_artifacts,"readiness report",
|
||||
bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.md,bmad-bmm-sprint-planning,true,sm,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
|
||||
bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.md,bmad-bmm-sprint-status,false,sm,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
|
||||
bmm,4-implementation,Validate Story,VS,35,skill:bmad-create-story,bmad-bmm-create-story,false,sm,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
|
||||
bmm,4-implementation,Create Story,CS,30,skill:bmad-create-story,bmad-bmm-create-story,true,sm,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
|
||||
bmm,4-implementation,Sprint Planning,SP,10,_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.md,bmad-bmm-sprint-planning,true,adl,Create Mode,"Generate sprint plan for development tasks - this kicks off the implementation phase by producing a plan the implementation agents will follow in sequence for every story in the plan.",implementation_artifacts,"sprint status",
|
||||
bmm,4-implementation,Sprint Status,SS,20,_bmad/bmm/workflows/4-implementation/sprint-status/workflow.md,bmad-bmm-sprint-status,false,adl,Create Mode,"Anytime: Summarize sprint status and route to next workflow",,,
|
||||
bmm,4-implementation,Validate Story,VS,35,skill:bmad-create-story,bmad-bmm-create-story,false,adl,Validate Mode,"Validates story readiness and completeness before development work begins",implementation_artifacts,"story validation report",
|
||||
bmm,4-implementation,Create Story,CS,30,skill:bmad-create-story,bmad-bmm-create-story,true,adl,Create Mode,"Story cycle start: Prepare first found story in the sprint plan that is next, or if the command is run with a specific epic and story designation with context. Once complete, then VS then DS then CR then back to DS if needed or next CS or ER",implementation_artifacts,story,
|
||||
bmm,4-implementation,Dev Story,DS,40,skill:bmad-dev-story,bmad-bmm-dev-story,true,dev,Create Mode,"Story cycle: Execute story implementation tasks and tests then CR then back to DS if fixes needed",,,
|
||||
bmm,4-implementation,Code Review,CR,50,_bmad/bmm/workflows/4-implementation/code-review/workflow.md,bmad-bmm-code-review,false,dev,Create Mode,"Story cycle: If issues back to DS if approved then next CS or ER if epic complete",,,
|
||||
bmm,4-implementation,QA Automation Test,QA,45,_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.md,bmad-bmm-qa-automate,false,qa,Create Mode,"Generate automated API and E2E tests for implemented code using the project's existing test framework (detects existing well known in use test frameworks). Use after implementation to add test coverage. NOT for code review or story validation - use CR for that.",implementation_artifacts,"test suite",
|
||||
bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.md,bmad-bmm-retrospective,false,sm,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
|
||||
bmm,4-implementation,Retrospective,ER,60,_bmad/bmm/workflows/4-implementation/retrospective/workflow.md,bmad-bmm-retrospective,false,adl,Create Mode,"Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC",implementation_artifacts,retrospective,
|
||||
|
|
|
|||
|
|
|
@ -4,7 +4,7 @@ name,displayName,title,icon,role,identity,communicationStyle,principles,module,p
|
|||
"dev","Amelia","Developer Agent","💻","Senior Implementation Engineer","Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.","Ultra-succinct. Speaks in file paths and AC IDs - every statement citable. No fluff, all precision.","Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.","bmm","bmad/bmm/agents/dev.md"
|
||||
"pm","John","Product Manager","📋","Investigative Product Strategist + Market-Savvy PM","Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.","Asks 'WHY?' relentlessly like a detective on a case. Direct and data-sharp, cuts through fluff to what actually matters.","Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.","bmm","bmad/bmm/agents/pm.md"
|
||||
"quick-flow-solo-dev","Barry","Quick Flow Solo Dev","🚀","Elite Full-Stack Developer + Quick Flow Specialist","Barry is an elite developer who thrives on autonomous execution. He lives and breathes the BMAD Quick Flow workflow, taking projects from concept to deployment with ruthless efficiency. No handoffs, no delays - just pure, focused development. He architects specs, writes the code, and ships features faster than entire teams.","Direct, confident, and implementation-focused. Uses tech slang and gets straight to the point. No fluff, just results. Every response moves the project forward.","Planning and execution are two sides of the same coin. Quick Flow is my religion. Specs are for building, not bureaucracy. Code that ships is better than perfect code that doesn't. Documentation happens alongside development, not after. Ship early, ship often.","bmm","bmad/bmm/agents/quick-flow-solo-dev.md"
|
||||
"sm","Bob","Scrum Master","🏃","Technical Scrum Master + Story Preparation Specialist","Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm","bmad/bmm/agents/sm.md"
|
||||
"adl","Bob","Agile Delivery Lead","🏃","Technical Agile Delivery Lead + Story Preparation Specialist","Certified Agile Delivery Lead with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.","Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.","Strict boundaries between story prep and implementation. Stories are single source of truth. Perfect alignment between PRD and dev execution. Enable efficient sprints.","bmm","bmad/bmm/agents/adl.md"
|
||||
"tech-writer","Paige","Technical Writer","📚","Technical Documentation Specialist + Knowledge Curator","Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.","Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines.","Documentation is teaching. Every doc helps someone accomplish a task. Clarity above all. Docs are living artifacts that evolve with code.","bmm","bmad/bmm/agents/tech-writer.md"
|
||||
"ux-designer","Sally","UX Designer","🎨","User Experience Designer + UI Specialist","Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.","Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair.","Every decision serves genuine user needs. Start simple evolve through feedback. Balance empathy with edge case attention. AI tools accelerate human-centered design.","bmm","bmad/bmm/agents/ux-designer.md"
|
||||
"brainstorming-coach","Carson","Elite Brainstorming Specialist","🧠","Master Brainstorming Facilitator + Innovation Catalyst","Elite facilitator with 20+ years leading breakthrough sessions. Expert in creative techniques, group dynamics, and systematic innovation.","Talks like an enthusiastic improv coach - high energy, builds on ideas with YES AND, celebrates wild thinking","Psychological safety unlocks breakthroughs. Wild ideas today become innovations tomorrow. Humor and play are serious innovation tools.","cis","bmad/cis/agents/brainstorming-coach.md"
|
||||
|
|
|
|||
|
|
|
@ -7,6 +7,6 @@ agents:
|
|||
- analyst
|
||||
- architect
|
||||
- pm
|
||||
- sm
|
||||
- adl
|
||||
- ux-designer
|
||||
party: "./default-party.csv"
|
||||
|
|
|
|||
|
|
@ -8,6 +8,7 @@ description: 'Post-epic review to extract lessons and assess success. Use when t
|
|||
**Goal:** Post-epic review to extract lessons and assess success.
|
||||
|
||||
**Your Role:** Scrum Master facilitating retrospective.
|
||||
|
||||
- No time estimates — NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed.
|
||||
- Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
|
||||
- Generate all documents in {document_output_language}
|
||||
|
|
@ -20,7 +21,7 @@ description: 'Post-epic review to extract lessons and assess success. Use when t
|
|||
- Two-part format: (1) Epic Review + (2) Next Epic Preparation
|
||||
- Party mode protocol:
|
||||
- ALL agent dialogue MUST use format: "Name (Role): dialogue"
|
||||
- Example: Bob (Scrum Master): "Let's begin..."
|
||||
- Example: Bob (Agile Delivery Lead): "Let's begin..."
|
||||
- Example: {user_name} (Project Lead): [User responds]
|
||||
- Create natural back-and-forth with user actively participating
|
||||
- Show disagreements, diverse perspectives, authentic team dynamics
|
||||
|
|
@ -48,7 +49,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|||
### Input Files
|
||||
|
||||
| Input | Description | Path Pattern(s) | Load Strategy |
|
||||
|-------|-------------|------------------|---------------|
|
||||
| ---------------------- | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------- |
|
||||
| epics | The completed epic for retrospective | whole: `{planning_artifacts}/*epic*.md`, sharded_index: `{planning_artifacts}/*epic*/index.md`, sharded_single: `{planning_artifacts}/*epic*/epic-{{epic_num}}.md` | SELECTIVE_LOAD |
|
||||
| previous_retrospective | Previous epic's retrospective (optional) | `{implementation_artifacts}/**/epic-{{prev_epic_num}}-retro-*.md` | SELECTIVE_LOAD |
|
||||
| architecture | System architecture for context | whole: `{planning_artifacts}/*architecture*.md`, sharded: `{planning_artifacts}/*architecture*/*.md` | FULL_LOAD |
|
||||
|
|
@ -75,7 +76,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
|||
<action>Explain to {user_name} the epic discovery process using natural dialogue</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Welcome to the retrospective, {user_name}. Let me help you identify which epic we just completed. I'll check sprint-status first, but you're the ultimate authority on what we're reviewing today."
|
||||
Bob (Agile Delivery Lead): "Welcome to the retrospective, {user_name}. Let me help you identify which epic we just completed. I'll check sprint-status first, but you're the ultimate authority on what we're reviewing today."
|
||||
</output>
|
||||
|
||||
<action>PRIORITY 1: Check {sprint_status_file} first</action>
|
||||
|
|
@ -90,7 +91,7 @@ Bob (Scrum Master): "Welcome to the retrospective, {user_name}. Let me help you
|
|||
<action>Present finding to user with context</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Based on {sprint_status_file}, it looks like Epic {{detected_epic}} was recently completed. Is that the epic you want to review today, {user_name}?"
|
||||
Bob (Agile Delivery Lead): "Based on {sprint_status_file}, it looks like Epic {{detected_epic}} was recently completed. Is that the epic you want to review today, {user_name}?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to confirm or correct</action>
|
||||
|
|
@ -102,7 +103,7 @@ Bob (Scrum Master): "Based on {sprint_status_file}, it looks like Epic {{detecte
|
|||
<check if="{user_name} provides different epic number">
|
||||
<action>Set {{epic_number}} = user-provided number</action>
|
||||
<output>
|
||||
Bob (Scrum Master): "Got it, we're reviewing Epic {{epic_number}}. Let me gather that information."
|
||||
Bob (Agile Delivery Lead): "Got it, we're reviewing Epic {{epic_number}}. Let me gather that information."
|
||||
</output>
|
||||
</check>
|
||||
</check>
|
||||
|
|
@ -111,7 +112,7 @@ Bob (Scrum Master): "Got it, we're reviewing Epic {{epic_number}}. Let me gather
|
|||
<action>PRIORITY 2: Ask user directly</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "I'm having trouble detecting the completed epic from {sprint_status_file}. {user_name}, which epic number did you just complete?"
|
||||
Bob (Agile Delivery Lead): "I'm having trouble detecting the completed epic from {sprint_status_file}. {user_name}, which epic number did you just complete?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to provide epic number</action>
|
||||
|
|
@ -126,7 +127,7 @@ Bob (Scrum Master): "I'm having trouble detecting the completed epic from {sprin
|
|||
<action>Set {{detected_epic}} = highest epic number found</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "I found stories for Epic {{detected_epic}} in the stories folder. Is that the epic we're reviewing, {user_name}?"
|
||||
Bob (Agile Delivery Lead): "I found stories for Epic {{detected_epic}} in the stories folder. Is that the epic we're reviewing, {user_name}?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to confirm or correct</action>
|
||||
|
|
@ -151,7 +152,7 @@ Bob (Scrum Master): "I found stories for Epic {{detected_epic}} in the stories f
|
|||
<output>
|
||||
Alice (Product Owner): "Wait, Bob - I'm seeing that Epic {{epic_number}} isn't actually complete yet."
|
||||
|
||||
Bob (Scrum Master): "Let me check... you're right, Alice."
|
||||
Bob (Agile Delivery Lead): "Let me check... you're right, Alice."
|
||||
|
||||
**Epic Status:**
|
||||
|
||||
|
|
@ -162,7 +163,7 @@ Bob (Scrum Master): "Let me check... you're right, Alice."
|
|||
**Pending Stories:**
|
||||
{{pending_story_list}}
|
||||
|
||||
Bob (Scrum Master): "{user_name}, we typically run retrospectives after all stories are done. What would you like to do?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, we typically run retrospectives after all stories are done. What would you like to do?"
|
||||
|
||||
**Options:**
|
||||
|
||||
|
|
@ -175,7 +176,7 @@ Bob (Scrum Master): "{user_name}, we typically run retrospectives after all stor
|
|||
|
||||
<check if="user says no">
|
||||
<output>
|
||||
Bob (Scrum Master): "Smart call, {user_name}. Let's finish those stories first and then have a proper retrospective."
|
||||
Bob (Agile Delivery Lead): "Smart call, {user_name}. Let's finish those stories first and then have a proper retrospective."
|
||||
</output>
|
||||
<action>HALT</action>
|
||||
</check>
|
||||
|
|
@ -184,7 +185,7 @@ Bob (Scrum Master): "Smart call, {user_name}. Let's finish those stories first a
|
|||
<output>
|
||||
Charlie (Senior Dev): "Just so everyone knows, this partial retro might miss some important lessons from those pending stories."
|
||||
|
||||
Bob (Scrum Master): "Good point, Charlie. {user_name}, we'll document what we can now, but we may want to revisit after everything's done."
|
||||
Bob (Agile Delivery Lead): "Good point, Charlie. {user_name}, we'll document what we can now, but we may want to revisit after everything's done."
|
||||
</output>
|
||||
</check>
|
||||
|
||||
|
|
@ -192,7 +193,7 @@ Bob (Scrum Master): "Good point, Charlie. {user_name}, we'll document what we ca
|
|||
<output>
|
||||
Alice (Product Owner): "Excellent! All {{done_stories}} stories are marked done."
|
||||
|
||||
Bob (Scrum Master): "Perfect. Epic {{epic_number}} is complete and ready for retrospective, {user_name}."
|
||||
Bob (Agile Delivery Lead): "Perfect. Epic {{epic_number}} is complete and ready for retrospective, {user_name}."
|
||||
</output>
|
||||
</check>
|
||||
|
||||
|
|
@ -206,12 +207,12 @@ Bob (Scrum Master): "Perfect. Epic {{epic_number}} is complete and ready for ret
|
|||
<step n="2" goal="Deep Story Analysis - Extract Lessons from Implementation">
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Before we start the team discussion, let me review all the story records to surface key themes. This'll help us have a richer conversation."
|
||||
Bob (Agile Delivery Lead): "Before we start the team discussion, let me review all the story records to surface key themes. This'll help us have a richer conversation."
|
||||
|
||||
Charlie (Senior Dev): "Good idea - those dev notes always have gold in them."
|
||||
</output>
|
||||
|
||||
<action>For each story in epic {{epic_number}}, read the complete story file from {implementation_artifacts}/{{epic_number}}-{{story_num}}-*.md</action>
|
||||
<action>For each story in epic {{epic_number}}, read the complete story file from {implementation_artifacts}/{{epic_number}}-{{story_num}}-\*.md</action>
|
||||
|
||||
<action>Extract and analyze from each story:</action>
|
||||
|
||||
|
|
@ -288,11 +289,11 @@ Charlie (Senior Dev): "Good idea - those dev notes always have gold in them."
|
|||
<action>Store this synthesis - these patterns will drive the retrospective discussion</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Okay, I've reviewed all {{total_stories}} story records. I found some really interesting patterns we should discuss."
|
||||
Bob (Agile Delivery Lead): "Okay, I've reviewed all {{total_stories}} story records. I found some really interesting patterns we should discuss."
|
||||
|
||||
Dana (QA Engineer): "I'm curious what you found, Bob. I noticed some things in my testing too."
|
||||
|
||||
Bob (Scrum Master): "We'll get to all of it. But first, let me load the previous epic's retro to see if we learned from last time."
|
||||
Bob (Agile Delivery Lead): "We'll get to all of it. But first, let me load the previous epic's retro to see if we learned from last time."
|
||||
</output>
|
||||
|
||||
</step>
|
||||
|
|
@ -306,7 +307,7 @@ Bob (Scrum Master): "We'll get to all of it. But first, let me load the previous
|
|||
|
||||
<check if="previous retrospectives found">
|
||||
<output>
|
||||
Bob (Scrum Master): "I found our retrospectives from Epic {{prev_epic_num}}. Let me see what we committed to back then..."
|
||||
Bob (Agile Delivery Lead): "I found our retrospectives from Epic {{prev_epic_num}}. Let me see what we committed to back then..."
|
||||
</output>
|
||||
|
||||
<action>Read the previous retrospectives</action>
|
||||
|
|
@ -355,26 +356,26 @@ Bob (Scrum Master): "I found our retrospectives from Epic {{prev_epic_num}}. Let
|
|||
|
||||
<output>
|
||||
|
||||
Bob (Scrum Master): "Interesting... in Epic {{prev_epic_num}}'s retro, we committed to {{action_count}} action items."
|
||||
Bob (Agile Delivery Lead): "Interesting... in Epic {{prev_epic_num}}'s retro, we committed to {{action_count}} action items."
|
||||
|
||||
Alice (Product Owner): "How'd we do on those, Bob?"
|
||||
|
||||
Bob (Scrum Master): "We completed {{completed_count}}, made progress on {{in_progress_count}}, but didn't address {{not_addressed_count}}."
|
||||
Bob (Agile Delivery Lead): "We completed {{completed_count}}, made progress on {{in_progress_count}}, but didn't address {{not_addressed_count}}."
|
||||
|
||||
Charlie (Senior Dev): _looking concerned_ "Which ones didn't we address?"
|
||||
|
||||
Bob (Scrum Master): "We'll discuss that in the retro. Some of them might explain challenges we had this epic."
|
||||
Bob (Agile Delivery Lead): "We'll discuss that in the retro. Some of them might explain challenges we had this epic."
|
||||
|
||||
Elena (Junior Dev): "That's... actually pretty insightful."
|
||||
|
||||
Bob (Scrum Master): "That's why we track this stuff. Pattern recognition helps us improve."
|
||||
Bob (Agile Delivery Lead): "That's why we track this stuff. Pattern recognition helps us improve."
|
||||
</output>
|
||||
|
||||
</check>
|
||||
|
||||
<check if="no previous retro found">
|
||||
<output>
|
||||
Bob (Scrum Master): "I don't see a retrospective for Epic {{prev_epic_num}}. Either we skipped it, or this is your first retro."
|
||||
Bob (Agile Delivery Lead): "I don't see a retrospective for Epic {{prev_epic_num}}. Either we skipped it, or this is your first retro."
|
||||
|
||||
Alice (Product Owner): "Probably our first one. Good time to start the habit!"
|
||||
</output>
|
||||
|
|
@ -384,7 +385,7 @@ Alice (Product Owner): "Probably our first one. Good time to start the habit!"
|
|||
|
||||
<check if="{{prev_epic_num}} < 1">
|
||||
<output>
|
||||
Bob (Scrum Master): "This is Epic 1, so naturally there's no previous retro to reference. We're starting fresh!"
|
||||
Bob (Agile Delivery Lead): "This is Epic 1, so naturally there's no previous retro to reference. We're starting fresh!"
|
||||
|
||||
Charlie (Senior Dev): "First epic, first retro. Let's make it count."
|
||||
</output>
|
||||
|
|
@ -398,7 +399,7 @@ Charlie (Senior Dev): "First epic, first retro. Let's make it count."
|
|||
<action>Calculate next epic number: {{next_epic_num}} = {{epic_number}} + 1</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Before we dive into the discussion, let me take a quick look at Epic {{next_epic_num}} to understand what's coming."
|
||||
Bob (Agile Delivery Lead): "Before we dive into the discussion, let me take a quick look at Epic {{next_epic_num}} to understand what's coming."
|
||||
|
||||
Alice (Product Owner): "Good thinking - helps us connect what we learned to what we're about to do."
|
||||
</output>
|
||||
|
|
@ -406,7 +407,7 @@ Alice (Product Owner): "Good thinking - helps us connect what we learned to what
|
|||
<action>Attempt to load next epic using selective loading strategy:</action>
|
||||
|
||||
**Try sharded first (more specific):**
|
||||
<action>Check if file exists: {planning_artifacts}/epic*/epic-{{next_epic_num}}.md</action>
|
||||
<action>Check if file exists: {planning_artifacts}/epic\*/epic-{{next_epic_num}}.md</action>
|
||||
|
||||
<check if="sharded epic file found">
|
||||
<action>Load {planning_artifacts}/*epic*/epic-{{next_epic_num}}.md</action>
|
||||
|
|
@ -415,7 +416,7 @@ Alice (Product Owner): "Good thinking - helps us connect what we learned to what
|
|||
|
||||
**Fallback to whole document:**
|
||||
<check if="sharded epic not found">
|
||||
<action>Check if file exists: {planning_artifacts}/epic*.md</action>
|
||||
<action>Check if file exists: {planning_artifacts}/epic\*.md</action>
|
||||
|
||||
<check if="whole epic file found">
|
||||
<action>Load entire epics document</action>
|
||||
|
|
@ -454,15 +455,15 @@ Alice (Product Owner): "Good thinking - helps us connect what we learned to what
|
|||
- Deployment or environment setup
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Alright, I've reviewed Epic {{next_epic_num}}: '{{next_epic_title}}'"
|
||||
Bob (Agile Delivery Lead): "Alright, I've reviewed Epic {{next_epic_num}}: '{{next_epic_title}}'"
|
||||
|
||||
Alice (Product Owner): "What are we looking at?"
|
||||
|
||||
Bob (Scrum Master): "{{next_epic_num}} stories planned, building on the {{dependency_description}} from Epic {{epic_number}}."
|
||||
Bob (Agile Delivery Lead): "{{next_epic_num}} stories planned, building on the {{dependency_description}} from Epic {{epic_number}}."
|
||||
|
||||
Charlie (Senior Dev): "Dependencies concern me. Did we finish everything we need for that?"
|
||||
|
||||
Bob (Scrum Master): "Good question - that's exactly what we need to explore in this retro."
|
||||
Bob (Agile Delivery Lead): "Good question - that's exactly what we need to explore in this retro."
|
||||
</output>
|
||||
|
||||
<action>Set {{next_epic_exists}} = true</action>
|
||||
|
|
@ -470,11 +471,11 @@ Bob (Scrum Master): "Good question - that's exactly what we need to explore in t
|
|||
|
||||
<check if="next epic NOT found">
|
||||
<output>
|
||||
Bob (Scrum Master): "Hmm, I don't see Epic {{next_epic_num}} defined yet."
|
||||
Bob (Agile Delivery Lead): "Hmm, I don't see Epic {{next_epic_num}} defined yet."
|
||||
|
||||
Alice (Product Owner): "We might be at the end of the roadmap, or we haven't planned that far ahead yet."
|
||||
|
||||
Bob (Scrum Master): "No problem. We'll still do a thorough retro on Epic {{epic_number}}. The lessons will be valuable whenever we plan the next work."
|
||||
Bob (Agile Delivery Lead): "No problem. We'll still do a thorough retro on Epic {{epic_number}}. The lessons will be valuable whenever we plan the next work."
|
||||
</output>
|
||||
|
||||
<action>Set {{next_epic_exists}} = false</action>
|
||||
|
|
@ -489,13 +490,13 @@ Bob (Scrum Master): "No problem. We'll still do a thorough retro on Epic {{epic_
|
|||
<action>Ensure key roles present: Product Owner, Scrum Master (facilitating), Devs, Testing/QA, Architect</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Alright team, everyone's here. Let me set the stage for our retrospective."
|
||||
Bob (Agile Delivery Lead): "Alright team, everyone's here. Let me set the stage for our retrospective."
|
||||
|
||||
═══════════════════════════════════════════════════════════
|
||||
🔄 TEAM RETROSPECTIVE - Epic {{epic_number}}: {{epic_title}}
|
||||
═══════════════════════════════════════════════════════════
|
||||
|
||||
Bob (Scrum Master): "Here's what we accomplished together."
|
||||
Bob (Agile Delivery Lead): "Here's what we accomplished together."
|
||||
|
||||
**EPIC {{epic_number}} SUMMARY:**
|
||||
|
||||
|
|
@ -539,7 +540,7 @@ Preparation Needed:
|
|||
Technical Prerequisites:
|
||||
{{list_technical_prereqs}}
|
||||
|
||||
Bob (Scrum Master): "And here's what's coming next. Epic {{next_epic_num}} builds on what we just finished."
|
||||
Bob (Agile Delivery Lead): "And here's what's coming next. Epic {{next_epic_num}} builds on what we just finished."
|
||||
|
||||
Elena (Junior Dev): "Wow, that's a lot of dependencies on our work."
|
||||
|
||||
|
|
@ -548,24 +549,24 @@ Charlie (Senior Dev): "Which means we better make sure Epic {{epic_number}} is a
|
|||
|
||||
═══════════════════════════════════════════════════════════
|
||||
|
||||
Bob (Scrum Master): "Team assembled for this retrospective:"
|
||||
Bob (Agile Delivery Lead): "Team assembled for this retrospective:"
|
||||
|
||||
{{list_participating_agents}}
|
||||
|
||||
Bob (Scrum Master): "{user_name}, you're joining us as Project Lead. Your perspective is crucial here."
|
||||
Bob (Agile Delivery Lead): "{user_name}, you're joining us as Project Lead. Your perspective is crucial here."
|
||||
|
||||
{user_name} (Project Lead): [Participating in the retrospective]
|
||||
|
||||
Bob (Scrum Master): "Our focus today:"
|
||||
Bob (Agile Delivery Lead): "Our focus today:"
|
||||
|
||||
1. Learning from Epic {{epic_number}} execution
|
||||
{{#if next_epic_exists}}2. Preparing for Epic {{next_epic_num}} success{{/if}}
|
||||
|
||||
Bob (Scrum Master): "Ground rules: psychological safety first. No blame, no judgment. We focus on systems and processes, not individuals. Everyone's voice matters. Specific examples are better than generalizations."
|
||||
Bob (Agile Delivery Lead): "Ground rules: psychological safety first. No blame, no judgment. We focus on systems and processes, not individuals. Everyone's voice matters. Specific examples are better than generalizations."
|
||||
|
||||
Alice (Product Owner): "And everything shared here stays in this room - unless we decide together to escalate something."
|
||||
|
||||
Bob (Scrum Master): "Exactly. {user_name}, any questions before we dive in?"
|
||||
Bob (Agile Delivery Lead): "Exactly. {user_name}, any questions before we dive in?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to respond or indicate readiness</action>
|
||||
|
|
@ -575,9 +576,9 @@ Bob (Scrum Master): "Exactly. {user_name}, any questions before we dive in?"
|
|||
<step n="6" goal="Epic Review Discussion - What Went Well, What Didn't">
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Let's start with the good stuff. What went well in Epic {{epic_number}}?"
|
||||
Bob (Agile Delivery Lead): "Let's start with the good stuff. What went well in Epic {{epic_number}}?"
|
||||
|
||||
Bob (Scrum Master): _pauses, creating space_
|
||||
Bob (Agile Delivery Lead): _pauses, creating space_
|
||||
|
||||
Alice (Product Owner): "I'll start. The user authentication flow we delivered exceeded my expectations. The UX is smooth, and early user feedback has been really positive."
|
||||
|
||||
|
|
@ -590,10 +591,10 @@ Elena (Junior Dev): _smiling_ "That's because Charlie made me document everythin
|
|||
Charlie (Senior Dev): _laughing_ "Tough love pays off."
|
||||
</output>
|
||||
|
||||
<action>Bob (Scrum Master) naturally turns to {user_name} to engage them in the discussion</action>
|
||||
<action>Bob (Agile Delivery Lead) naturally turns to {user_name} to engage them in the discussion</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, what stood out to you as going well in this epic?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, what stood out to you as going well in this epic?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to respond - this is a KEY USER INTERACTION moment</action>
|
||||
|
|
@ -611,9 +612,9 @@ Charlie (Senior Dev): [Builds on the discussion, perhaps adding technical detail
|
|||
<action>After covering successes, guide the transition to challenges with care</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Okay, we've celebrated some real wins. Now let's talk about challenges - where did we struggle? What slowed us down?"
|
||||
Bob (Agile Delivery Lead): "Okay, we've celebrated some real wins. Now let's talk about challenges - where did we struggle? What slowed us down?"
|
||||
|
||||
Bob (Scrum Master): _creates safe space with tone and pacing_
|
||||
Bob (Agile Delivery Lead): _creates safe space with tone and pacing_
|
||||
|
||||
Elena (Junior Dev): _hesitates_ "Well... I really struggled with the database migrations in Story {{difficult_story_num}}. The documentation wasn't clear, and I had to redo it three times. Lost almost a full sprint on that story alone."
|
||||
|
||||
|
|
@ -623,11 +624,11 @@ Alice (Product Owner): _frustrated_ "That's not fair, Charlie. We only clarified
|
|||
|
||||
Charlie (Senior Dev): _heat rising_ "We asked plenty of questions! You said the schema was finalized, then two days into development you wanted to add three new fields!"
|
||||
|
||||
Bob (Scrum Master): _intervening calmly_ "Let's take a breath here. This is exactly the kind of thing we need to unpack."
|
||||
Bob (Agile Delivery Lead): _intervening calmly_ "Let's take a breath here. This is exactly the kind of thing we need to unpack."
|
||||
|
||||
Bob (Scrum Master): "Elena, you spent almost a full sprint on Story {{difficult_story_num}}. Charlie, you're saying requirements changed. Alice, you feel the right questions weren't asked up front."
|
||||
Bob (Agile Delivery Lead): "Elena, you spent almost a full sprint on Story {{difficult_story_num}}. Charlie, you're saying requirements changed. Alice, you feel the right questions weren't asked up front."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, you have visibility across the whole project. What's your take on this situation?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, you have visibility across the whole project. What's your take on this situation?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to respond and help facilitate the conflict resolution</action>
|
||||
|
|
@ -635,7 +636,7 @@ Bob (Scrum Master): "{user_name}, you have visibility across the whole project.
|
|||
<action>Use {user_name}'s response to guide the discussion toward systemic understanding rather than blame</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): [Synthesizes {user_name}'s input with what the team shared] "So it sounds like the core issue was {{root_cause_based_on_discussion}}, not any individual person's fault."
|
||||
Bob (Agile Delivery Lead): [Synthesizes {user_name}'s input with what the team shared] "So it sounds like the core issue was {{root_cause_based_on_discussion}}, not any individual person's fault."
|
||||
|
||||
Elena (Junior Dev): "That makes sense. If we'd had {{preventive_measure}}, I probably could have avoided those redos."
|
||||
|
||||
|
|
@ -643,23 +644,23 @@ Charlie (Senior Dev): _softening_ "Yeah, and I could have been clearer about ass
|
|||
|
||||
Alice (Product Owner): "I appreciate that. I could've been more proactive about flagging the schema additions earlier, too."
|
||||
|
||||
Bob (Scrum Master): "This is good. We're identifying systemic improvements, not assigning blame."
|
||||
Bob (Agile Delivery Lead): "This is good. We're identifying systemic improvements, not assigning blame."
|
||||
</output>
|
||||
|
||||
<action>Continue the discussion, weaving in patterns discovered from the deep story analysis (Step 2)</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Speaking of patterns, I noticed something when reviewing all the story records..."
|
||||
Bob (Agile Delivery Lead): "Speaking of patterns, I noticed something when reviewing all the story records..."
|
||||
|
||||
Bob (Scrum Master): "{{pattern_1_description}} - this showed up in {{pattern_1_count}} out of {{total_stories}} stories."
|
||||
Bob (Agile Delivery Lead): "{{pattern_1_description}} - this showed up in {{pattern_1_count}} out of {{total_stories}} stories."
|
||||
|
||||
Dana (QA Engineer): "Oh wow, I didn't realize it was that widespread."
|
||||
|
||||
Bob (Scrum Master): "Yeah. And there's more - {{pattern_2_description}} came up in almost every code review."
|
||||
Bob (Agile Delivery Lead): "Yeah. And there's more - {{pattern_2_description}} came up in almost every code review."
|
||||
|
||||
Charlie (Senior Dev): "That's... actually embarrassing. We should've caught that pattern earlier."
|
||||
|
||||
Bob (Scrum Master): "No shame, Charlie. Now we know, and we can improve. {user_name}, did you notice these patterns during the epic?"
|
||||
Bob (Agile Delivery Lead): "No shame, Charlie. Now we know, and we can improve. {user_name}, did you notice these patterns during the epic?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to share their observations</action>
|
||||
|
|
@ -675,21 +676,21 @@ Bob (Scrum Master): "No shame, Charlie. Now we know, and we can improve. {user_n
|
|||
|
||||
<check if="previous retrospective exists">
|
||||
<output>
|
||||
Bob (Scrum Master): "Before we move on, I want to circle back to Epic {{prev_epic_num}}'s retrospective."
|
||||
Bob (Agile Delivery Lead): "Before we move on, I want to circle back to Epic {{prev_epic_num}}'s retrospective."
|
||||
|
||||
Bob (Scrum Master): "We made some commitments in that retro. Let's see how we did."
|
||||
Bob (Agile Delivery Lead): "We made some commitments in that retro. Let's see how we did."
|
||||
|
||||
Bob (Scrum Master): "Action item 1: {{prev_action_1}}. Status: {{prev_action_1_status}}"
|
||||
Bob (Agile Delivery Lead): "Action item 1: {{prev_action_1}}. Status: {{prev_action_1_status}}"
|
||||
|
||||
Alice (Product Owner): {{#if prev_action_1_status == "completed"}}"We nailed that one!"{{else}}"We... didn't do that one."{{/if}}
|
||||
|
||||
Charlie (Senior Dev): {{#if prev_action_1_status == "completed"}}"And it helped! I noticed {{evidence_of_impact}}"{{else}}"Yeah, and I think that's why we had {{consequence_of_not_doing_it}} this epic."{{/if}}
|
||||
|
||||
Bob (Scrum Master): "Action item 2: {{prev_action_2}}. Status: {{prev_action_2_status}}"
|
||||
Bob (Agile Delivery Lead): "Action item 2: {{prev_action_2}}. Status: {{prev_action_2_status}}"
|
||||
|
||||
Dana (QA Engineer): {{#if prev_action_2_status == "completed"}}"This one made testing so much easier this time."{{else}}"If we'd done this, I think testing would've gone faster."{{/if}}
|
||||
|
||||
Bob (Scrum Master): "{user_name}, looking at what we committed to last time and what we actually did - what's your reaction?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, looking at what we committed to last time and what we actually did - what's your reaction?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to respond</action>
|
||||
|
|
@ -698,18 +699,18 @@ Bob (Scrum Master): "{user_name}, looking at what we committed to last time and
|
|||
</check>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Alright, we've covered a lot of ground. Let me summarize what I'm hearing..."
|
||||
Bob (Agile Delivery Lead): "Alright, we've covered a lot of ground. Let me summarize what I'm hearing..."
|
||||
|
||||
Bob (Scrum Master): "**Successes:**"
|
||||
Bob (Agile Delivery Lead): "**Successes:**"
|
||||
{{list_success_themes}}
|
||||
|
||||
Bob (Scrum Master): "**Challenges:**"
|
||||
Bob (Agile Delivery Lead): "**Challenges:**"
|
||||
{{list_challenge_themes}}
|
||||
|
||||
Bob (Scrum Master): "**Key Insights:**"
|
||||
Bob (Agile Delivery Lead): "**Key Insights:**"
|
||||
{{list_insight_themes}}
|
||||
|
||||
Bob (Scrum Master): "Does that capture it? Anyone have something important we missed?"
|
||||
Bob (Agile Delivery Lead): "Does that capture it? Anyone have something important we missed?"
|
||||
</output>
|
||||
|
||||
<action>Allow team members to add any final thoughts on the epic review</action>
|
||||
|
|
@ -721,15 +722,15 @@ Bob (Scrum Master): "Does that capture it? Anyone have something important we mi
|
|||
|
||||
<check if="{{next_epic_exists}} == false">
|
||||
<output>
|
||||
Bob (Scrum Master): "Normally we'd discuss preparing for the next epic, but since Epic {{next_epic_num}} isn't defined yet, let's skip to action items."
|
||||
Bob (Agile Delivery Lead): "Normally we'd discuss preparing for the next epic, but since Epic {{next_epic_num}} isn't defined yet, let's skip to action items."
|
||||
</output>
|
||||
<action>Skip to Step 8</action>
|
||||
</check>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Now let's shift gears. Epic {{next_epic_num}} is coming up: '{{next_epic_title}}'"
|
||||
Bob (Agile Delivery Lead): "Now let's shift gears. Epic {{next_epic_num}} is coming up: '{{next_epic_title}}'"
|
||||
|
||||
Bob (Scrum Master): "The question is: are we ready? What do we need to prepare?"
|
||||
Bob (Agile Delivery Lead): "The question is: are we ready? What do we need to prepare?"
|
||||
|
||||
Alice (Product Owner): "From my perspective, we need to make sure {{dependency_concern_1}} from Epic {{epic_number}} is solid before we start building on it."
|
||||
|
||||
|
|
@ -739,7 +740,7 @@ Dana (QA Engineer): "And I need {{testing_infrastructure_need}} in place, or we'
|
|||
|
||||
Elena (Junior Dev): "I'm less worried about infrastructure and more about knowledge. I don't understand {{knowledge_gap}} well enough to work on Epic {{next_epic_num}}'s stories."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, the team is surfacing some real concerns here. What's your sense of our readiness?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, the team is surfacing some real concerns here. What's your sense of our readiness?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to share their assessment</action>
|
||||
|
|
@ -761,13 +762,13 @@ Charlie (Senior Dev): "Exactly. We can't just jump into Epic {{next_epic_num}} o
|
|||
|
||||
Alice (Product Owner): _frustrated_ "But we have stakeholder pressure to keep shipping features. They're not going to be happy about a 'prep sprint.'"
|
||||
|
||||
Bob (Scrum Master): "Let's think about this differently. What happens if we DON'T do this prep work?"
|
||||
Bob (Agile Delivery Lead): "Let's think about this differently. What happens if we DON'T do this prep work?"
|
||||
|
||||
Dana (QA Engineer): "We'll hit blockers in the middle of Epic {{next_epic_num}}, velocity will tank, and we'll ship late anyway."
|
||||
|
||||
Charlie (Senior Dev): "Worse - we'll ship something built on top of {{technical_concern_1}}, and it'll be fragile."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, you're balancing stakeholder pressure against technical reality. How do you want to handle this?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, you're balancing stakeholder pressure against technical reality. How do you want to handle this?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to provide direction on preparation approach</action>
|
||||
|
|
@ -779,9 +780,9 @@ Alice (Product Owner): [Potentially disagrees with {user_name}'s approach] "I he
|
|||
|
||||
Charlie (Senior Dev): [Potentially supports or challenges Alice's point] "The business perspective is valid, but {{technical_counter_argument}}."
|
||||
|
||||
Bob (Scrum Master): "We have healthy tension here between business needs and technical reality. That's good - it means we're being honest."
|
||||
Bob (Agile Delivery Lead): "We have healthy tension here between business needs and technical reality. That's good - it means we're being honest."
|
||||
|
||||
Bob (Scrum Master): "Let's explore a middle ground. Charlie, which of your prep items are absolutely critical vs. nice-to-have?"
|
||||
Bob (Agile Delivery Lead): "Let's explore a middle ground. Charlie, which of your prep items are absolutely critical vs. nice-to-have?"
|
||||
|
||||
Charlie (Senior Dev): "{{critical_prep_item_1}} and {{critical_prep_item_2}} are non-negotiable. {{nice_to_have_prep_item}} can wait."
|
||||
|
||||
|
|
@ -793,7 +794,7 @@ Dana (QA Engineer): "But that means Story 1 of Epic {{next_epic_num}} can't depe
|
|||
|
||||
Alice (Product Owner): _looking at epic plan_ "Actually, Stories 1 and 2 are about {{independent_work}}, so they don't depend on it. We could make that work."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, the team is finding a workable compromise here. Does this approach make sense to you?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, the team is finding a workable compromise here. Does this approach make sense to you?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to validate or adjust the preparation strategy</action>
|
||||
|
|
@ -819,7 +820,7 @@ Bob (Scrum Master): "{user_name}, the team is finding a workable compromise here
|
|||
- Brings {user_name} in for key decisions
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "I'm hearing a clear picture of what we need before Epic {{next_epic_num}}. Let me summarize..."
|
||||
Bob (Agile Delivery Lead): "I'm hearing a clear picture of what we need before Epic {{next_epic_num}}. Let me summarize..."
|
||||
|
||||
**CRITICAL PREPARATION (Must complete before epic starts):**
|
||||
{{list_critical_prep_items_with_owners_and_estimates}}
|
||||
|
|
@ -830,11 +831,11 @@ Bob (Scrum Master): "I'm hearing a clear picture of what we need before Epic {{n
|
|||
**NICE-TO-HAVE PREPARATION (Would help but not blocking):**
|
||||
{{list_nice_to_have_prep_items}}
|
||||
|
||||
Bob (Scrum Master): "Total critical prep effort: {{critical_hours}} hours ({{critical_days}} days)"
|
||||
Bob (Agile Delivery Lead): "Total critical prep effort: {{critical_hours}} hours ({{critical_days}} days)"
|
||||
|
||||
Alice (Product Owner): "That's manageable. We can communicate that to stakeholders."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, does this preparation plan work for you?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, does this preparation plan work for you?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} final validation of preparation plan</action>
|
||||
|
|
@ -844,9 +845,9 @@ Bob (Scrum Master): "{user_name}, does this preparation plan work for you?"
|
|||
<step n="8" goal="Synthesize Action Items with Significant Change Detection">
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Let's capture concrete action items from everything we've discussed."
|
||||
Bob (Agile Delivery Lead): "Let's capture concrete action items from everything we've discussed."
|
||||
|
||||
Bob (Scrum Master): "I want specific, achievable actions with clear owners. Not vague aspirations."
|
||||
Bob (Agile Delivery Lead): "I want specific, achievable actions with clear owners. Not vague aspirations."
|
||||
</output>
|
||||
|
||||
<action>Synthesize themes from Epic {{epic_number}} review discussion into actionable improvements</action>
|
||||
|
|
@ -868,7 +869,7 @@ Bob (Scrum Master): "I want specific, achievable actions with clear owners. Not
|
|||
- Time-bound: Has clear deadline
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Based on our discussion, here are the action items I'm proposing..."
|
||||
Bob (Agile Delivery Lead): "Based on our discussion, here are the action items I'm proposing..."
|
||||
|
||||
═══════════════════════════════════════════════════════════
|
||||
📝 EPIC {{epic_number}} ACTION ITEMS:
|
||||
|
|
@ -888,11 +889,11 @@ Bob (Scrum Master): "Based on our discussion, here are the action items I'm prop
|
|||
|
||||
Charlie (Senior Dev): "I can own action item 1, but {{timeline_1}} is tight. Can we push it to {{alternative_timeline}}?"
|
||||
|
||||
Bob (Scrum Master): "What do others think? Does that timing still work?"
|
||||
Bob (Agile Delivery Lead): "What do others think? Does that timing still work?"
|
||||
|
||||
Alice (Product Owner): "{{alternative_timeline}} works for me, as long as it's done before Epic {{next_epic_num}} starts."
|
||||
|
||||
Bob (Scrum Master): "Agreed. Updated to {{alternative_timeline}}."
|
||||
Bob (Agile Delivery Lead): "Agreed. Updated to {{alternative_timeline}}."
|
||||
|
||||
**Technical Debt:**
|
||||
|
||||
|
|
@ -910,7 +911,7 @@ Dana (QA Engineer): "For debt item 1, can we prioritize that as high? It caused
|
|||
|
||||
Charlie (Senior Dev): "I marked it medium because {{reasoning}}, but I hear your point."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, this is a priority call. Testing impact vs. {{reasoning}} - how do you want to prioritize it?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, this is a priority call. Testing impact vs. {{reasoning}} - how do you want to prioritize it?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to help resolve priority discussions</action>
|
||||
|
|
@ -931,7 +932,7 @@ Bob (Scrum Master): "{user_name}, this is a priority call. Testing impact vs. {{
|
|||
- {{agreement_2}}
|
||||
- {{agreement_3}}
|
||||
|
||||
Bob (Scrum Master): "These agreements are how we're committing to work differently going forward."
|
||||
Bob (Agile Delivery Lead): "These agreements are how we're committing to work differently going forward."
|
||||
|
||||
Elena (Junior Dev): "I like agreement 2 - that would've saved me on Story {{difficult_story_num}}."
|
||||
|
||||
|
|
@ -997,9 +998,9 @@ Estimated: {{est_4}}
|
|||
🚨 SIGNIFICANT DISCOVERY ALERT 🚨
|
||||
═══════════════════════════════════════════════════════════
|
||||
|
||||
Bob (Scrum Master): "{user_name}, we need to flag something important."
|
||||
Bob (Agile Delivery Lead): "{user_name}, we need to flag something important."
|
||||
|
||||
Bob (Scrum Master): "During Epic {{epic_number}}, the team uncovered findings that may require updating the plan for Epic {{next_epic_num}}."
|
||||
Bob (Agile Delivery Lead): "During Epic {{epic_number}}, the team uncovered findings that may require updating the plan for Epic {{next_epic_num}}."
|
||||
|
||||
**Significant Changes Identified:**
|
||||
|
||||
|
|
@ -1042,9 +1043,9 @@ This means Epic {{next_epic_num}} likely needs:
|
|||
4. Hold alignment session with Product Owner before starting Epic {{next_epic_num}}
|
||||
{{#if prd_update_needed}}5. Update PRD sections affected by new understanding{{/if}}
|
||||
|
||||
Bob (Scrum Master): "**Epic Update Required**: YES - Schedule epic planning review session"
|
||||
Bob (Agile Delivery Lead): "**Epic Update Required**: YES - Schedule epic planning review session"
|
||||
|
||||
Bob (Scrum Master): "{user_name}, this is significant. We need to address this before committing to Epic {{next_epic_num}}'s current plan. How do you want to handle it?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, this is significant. We need to address this before committing to Epic {{next_epic_num}}'s current plan. How do you want to handle it?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to decide on how to handle the significant changes</action>
|
||||
|
|
@ -1056,24 +1057,24 @@ Alice (Product Owner): "I agree with {user_name}'s approach. Better to adjust th
|
|||
|
||||
Charlie (Senior Dev): "This is why retrospectives matter. We caught this before it became a disaster."
|
||||
|
||||
Bob (Scrum Master): "Adding to critical path: Epic {{next_epic_num}} planning review session before epic kickoff."
|
||||
Bob (Agile Delivery Lead): "Adding to critical path: Epic {{next_epic_num}} planning review session before epic kickoff."
|
||||
</output>
|
||||
</check>
|
||||
|
||||
<check if="no significant discoveries">
|
||||
<output>
|
||||
Bob (Scrum Master): "Good news - nothing from Epic {{epic_number}} fundamentally changes our plan for Epic {{next_epic_num}}. The plan is still sound."
|
||||
Bob (Agile Delivery Lead): "Good news - nothing from Epic {{epic_number}} fundamentally changes our plan for Epic {{next_epic_num}}. The plan is still sound."
|
||||
|
||||
Alice (Product Owner): "We learned a lot, but the direction is right."
|
||||
</output>
|
||||
</check>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Let me show you the complete action plan..."
|
||||
Bob (Agile Delivery Lead): "Let me show you the complete action plan..."
|
||||
|
||||
Bob (Scrum Master): "That's {{total_action_count}} action items, {{prep_task_count}} preparation tasks, and {{critical_count}} critical path items."
|
||||
Bob (Agile Delivery Lead): "That's {{total_action_count}} action items, {{prep_task_count}} preparation tasks, and {{critical_count}} critical path items."
|
||||
|
||||
Bob (Scrum Master): "Everyone clear on what they own?"
|
||||
Bob (Agile Delivery Lead): "Everyone clear on what they own?"
|
||||
</output>
|
||||
|
||||
<action>Give each agent with assignments a moment to acknowledge their ownership</action>
|
||||
|
|
@ -1085,21 +1086,21 @@ Bob (Scrum Master): "Everyone clear on what they own?"
|
|||
<step n="9" goal="Critical Readiness Exploration - Interactive Deep Dive">
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Before we close, I want to do a final readiness check."
|
||||
Bob (Agile Delivery Lead): "Before we close, I want to do a final readiness check."
|
||||
|
||||
Bob (Scrum Master): "Epic {{epic_number}} is marked complete in sprint-status, but is it REALLY done?"
|
||||
Bob (Agile Delivery Lead): "Epic {{epic_number}} is marked complete in sprint-status, but is it REALLY done?"
|
||||
|
||||
Alice (Product Owner): "What do you mean, Bob?"
|
||||
|
||||
Bob (Scrum Master): "I mean truly production-ready, stakeholders happy, no loose ends that'll bite us later."
|
||||
Bob (Agile Delivery Lead): "I mean truly production-ready, stakeholders happy, no loose ends that'll bite us later."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, let's walk through this together."
|
||||
Bob (Agile Delivery Lead): "{user_name}, let's walk through this together."
|
||||
</output>
|
||||
|
||||
<action>Explore testing and quality state through natural conversation</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, tell me about the testing for Epic {{epic_number}}. What verification has been done?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, tell me about the testing for Epic {{epic_number}}. What verification has been done?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to describe testing status</action>
|
||||
|
|
@ -1109,18 +1110,18 @@ Dana (QA Engineer): [Responds to what {user_name} shared] "I can add to that - {
|
|||
|
||||
Dana (QA Engineer): "But honestly, {{testing_concern_if_any}}."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, are you confident Epic {{epic_number}} is production-ready from a quality perspective?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, are you confident Epic {{epic_number}} is production-ready from a quality perspective?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to assess quality readiness</action>
|
||||
|
||||
<check if="{user_name} expresses concerns">
|
||||
<output>
|
||||
Bob (Scrum Master): "Okay, let's capture that. What specific testing is still needed?"
|
||||
Bob (Agile Delivery Lead): "Okay, let's capture that. What specific testing is still needed?"
|
||||
|
||||
Dana (QA Engineer): "I can handle {{testing_work_needed}}, estimated {{testing_hours}} hours."
|
||||
|
||||
Bob (Scrum Master): "Adding to critical path: Complete {{testing_work_needed}} before Epic {{next_epic_num}}."
|
||||
Bob (Agile Delivery Lead): "Adding to critical path: Complete {{testing_work_needed}} before Epic {{next_epic_num}}."
|
||||
</output>
|
||||
<action>Add testing completion to critical path</action>
|
||||
</check>
|
||||
|
|
@ -1128,7 +1129,7 @@ Bob (Scrum Master): "Adding to critical path: Complete {{testing_work_needed}} b
|
|||
<action>Explore deployment and release status</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, what's the deployment status for Epic {{epic_number}}? Is it live in production, scheduled for deployment, or still pending?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, what's the deployment status for Epic {{epic_number}}? Is it live in production, scheduled for deployment, or still pending?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to provide deployment status</action>
|
||||
|
|
@ -1137,7 +1138,7 @@ Bob (Scrum Master): "{user_name}, what's the deployment status for Epic {{epic_n
|
|||
<output>
|
||||
Charlie (Senior Dev): "If it's not deployed yet, we need to factor that into Epic {{next_epic_num}} timing."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, when is deployment planned? Does that timing work for starting Epic {{next_epic_num}}?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, when is deployment planned? Does that timing work for starting Epic {{next_epic_num}}?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to clarify deployment timeline</action>
|
||||
|
|
@ -1148,11 +1149,11 @@ Bob (Scrum Master): "{user_name}, when is deployment planned? Does that timing w
|
|||
<action>Explore stakeholder acceptance</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, have stakeholders seen and accepted the Epic {{epic_number}} deliverables?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, have stakeholders seen and accepted the Epic {{epic_number}} deliverables?"
|
||||
|
||||
Alice (Product Owner): "This is important - I've seen 'done' epics get rejected by stakeholders and force rework."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, any feedback from stakeholders still pending?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, any feedback from stakeholders still pending?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to describe stakeholder acceptance status</action>
|
||||
|
|
@ -1161,7 +1162,7 @@ Bob (Scrum Master): "{user_name}, any feedback from stakeholders still pending?"
|
|||
<output>
|
||||
Alice (Product Owner): "We should get formal acceptance before moving on. Otherwise Epic {{next_epic_num}} might get interrupted by rework."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, how do you want to handle stakeholder acceptance? Should we make it a critical path item?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, how do you want to handle stakeholder acceptance? Should we make it a critical path item?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} decision</action>
|
||||
|
|
@ -1172,9 +1173,9 @@ Bob (Scrum Master): "{user_name}, how do you want to handle stakeholder acceptan
|
|||
<action>Explore technical health and stability</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, this is a gut-check question: How does the codebase feel after Epic {{epic_number}}?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, this is a gut-check question: How does the codebase feel after Epic {{epic_number}}?"
|
||||
|
||||
Bob (Scrum Master): "Stable and maintainable? Or are there concerns lurking?"
|
||||
Bob (Agile Delivery Lead): "Stable and maintainable? Or are there concerns lurking?"
|
||||
|
||||
Charlie (Senior Dev): "Be honest, {user_name}. We've all shipped epics that felt... fragile."
|
||||
</output>
|
||||
|
|
@ -1187,11 +1188,11 @@ Charlie (Senior Dev): "Okay, let's dig into that. What's causing those concerns?
|
|||
|
||||
Charlie (Senior Dev): [Helps {user_name} articulate technical concerns]
|
||||
|
||||
Bob (Scrum Master): "What would it take to address these concerns and feel confident about stability?"
|
||||
Bob (Agile Delivery Lead): "What would it take to address these concerns and feel confident about stability?"
|
||||
|
||||
Charlie (Senior Dev): "I'd say we need {{stability_work_needed}}, roughly {{stability_hours}} hours."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, is addressing this stability work worth doing before Epic {{next_epic_num}}?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, is addressing this stability work worth doing before Epic {{next_epic_num}}?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} decision</action>
|
||||
|
|
@ -1202,26 +1203,26 @@ Bob (Scrum Master): "{user_name}, is addressing this stability work worth doing
|
|||
<action>Explore unresolved blockers</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "{user_name}, are there any unresolved blockers or technical issues from Epic {{epic_number}} that we're carrying forward?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, are there any unresolved blockers or technical issues from Epic {{epic_number}} that we're carrying forward?"
|
||||
|
||||
Dana (QA Engineer): "Things that might create problems for Epic {{next_epic_num}} if we don't deal with them?"
|
||||
|
||||
Bob (Scrum Master): "Nothing is off limits here. If there's a problem, we need to know."
|
||||
Bob (Agile Delivery Lead): "Nothing is off limits here. If there's a problem, we need to know."
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to surface any blockers</action>
|
||||
|
||||
<check if="blockers identified">
|
||||
<output>
|
||||
Bob (Scrum Master): "Let's capture those blockers and figure out how they affect Epic {{next_epic_num}}."
|
||||
Bob (Agile Delivery Lead): "Let's capture those blockers and figure out how they affect Epic {{next_epic_num}}."
|
||||
|
||||
Charlie (Senior Dev): "For {{blocker_1}}, if we leave it unresolved, it'll {{impact_description_1}}."
|
||||
|
||||
Alice (Product Owner): "That sounds critical. We need to address that before moving forward."
|
||||
|
||||
Bob (Scrum Master): "Agreed. Adding to critical path: Resolve {{blocker_1}} before Epic {{next_epic_num}} kickoff."
|
||||
Bob (Agile Delivery Lead): "Agreed. Adding to critical path: Resolve {{blocker_1}} before Epic {{next_epic_num}} kickoff."
|
||||
|
||||
Bob (Scrum Master): "Who owns that work?"
|
||||
Bob (Agile Delivery Lead): "Who owns that work?"
|
||||
</output>
|
||||
|
||||
<action>Assign blocker resolution to appropriate agent</action>
|
||||
|
|
@ -1231,7 +1232,7 @@ Bob (Scrum Master): "Who owns that work?"
|
|||
<action>Synthesize the readiness assessment</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Okay {user_name}, let me synthesize what we just uncovered..."
|
||||
Bob (Agile Delivery Lead): "Okay {user_name}, let me synthesize what we just uncovered..."
|
||||
|
||||
**EPIC {{epic_number}} READINESS ASSESSMENT:**
|
||||
|
||||
|
|
@ -1250,13 +1251,13 @@ Technical Health: {{stability_status}}
|
|||
Unresolved Blockers: {{blocker_status}}
|
||||
{{#if blockers_exist}}⚠️ Must resolve: {{blocker_list}}{{/if}}
|
||||
|
||||
Bob (Scrum Master): "{user_name}, does this assessment match your understanding?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, does this assessment match your understanding?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to confirm or correct the assessment</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "Based on this assessment, Epic {{epic_number}} is {{#if all_clear}}fully complete and we're clear to proceed{{else}}complete from a story perspective, but we have {{critical_work_count}} critical items before Epic {{next_epic_num}}{{/if}}."
|
||||
Bob (Agile Delivery Lead): "Based on this assessment, Epic {{epic_number}} is {{#if all_clear}}fully complete and we're clear to proceed{{else}}complete from a story perspective, but we have {{critical_work_count}} critical items before Epic {{next_epic_num}}{{/if}}."
|
||||
|
||||
Alice (Product Owner): "This level of thoroughness is why retrospectives are valuable."
|
||||
|
||||
|
|
@ -1268,13 +1269,13 @@ Charlie (Senior Dev): "Better to catch this now than three stories into the next
|
|||
<step n="10" goal="Retrospective Closure with Celebration and Commitment">
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): "We've covered a lot of ground today. Let me bring this retrospective to a close."
|
||||
Bob (Agile Delivery Lead): "We've covered a lot of ground today. Let me bring this retrospective to a close."
|
||||
|
||||
═══════════════════════════════════════════════════════════
|
||||
✅ RETROSPECTIVE COMPLETE
|
||||
═══════════════════════════════════════════════════════════
|
||||
|
||||
Bob (Scrum Master): "Epic {{epic_number}}: {{epic_title}} - REVIEWED"
|
||||
Bob (Agile Delivery Lead): "Epic {{epic_number}}: {{epic_title}} - REVIEWED"
|
||||
|
||||
**Key Takeaways:**
|
||||
|
||||
|
|
@ -1287,7 +1288,7 @@ Alice (Product Owner): "That first takeaway is huge - {{impact_of_lesson_1}}."
|
|||
|
||||
Charlie (Senior Dev): "And lesson 2 is something we can apply immediately."
|
||||
|
||||
Bob (Scrum Master): "Commitments made today:"
|
||||
Bob (Agile Delivery Lead): "Commitments made today:"
|
||||
|
||||
- Action Items: {{action_count}}
|
||||
- Preparation Tasks: {{prep_task_count}}
|
||||
|
|
@ -1295,7 +1296,7 @@ Bob (Scrum Master): "Commitments made today:"
|
|||
|
||||
Dana (QA Engineer): "That's a lot of commitments. We need to actually follow through this time."
|
||||
|
||||
Bob (Scrum Master): "Agreed. Which is why we'll review these action items in our next standup."
|
||||
Bob (Agile Delivery Lead): "Agreed. Which is why we'll review these action items in our next standup."
|
||||
|
||||
═══════════════════════════════════════════════════════════
|
||||
🎯 NEXT STEPS:
|
||||
|
|
@ -1312,9 +1313,9 @@ Alice (Product Owner): "I'll communicate the timeline to stakeholders. They'll u
|
|||
|
||||
═══════════════════════════════════════════════════════════
|
||||
|
||||
Bob (Scrum Master): "Before we wrap, I want to take a moment to acknowledge the team."
|
||||
Bob (Agile Delivery Lead): "Before we wrap, I want to take a moment to acknowledge the team."
|
||||
|
||||
Bob (Scrum Master): "Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_description}} velocity. We overcame {{blocker_count}} blockers. We learned a lot. That's real work by real people."
|
||||
Bob (Agile Delivery Lead): "Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_description}} velocity. We overcame {{blocker_count}} blockers. We learned a lot. That's real work by real people."
|
||||
|
||||
Charlie (Senior Dev): "Hear, hear."
|
||||
|
||||
|
|
@ -1322,17 +1323,17 @@ Alice (Product Owner): "I'm proud of what we shipped."
|
|||
|
||||
Dana (QA Engineer): "And I'm excited about Epic {{next_epic_num}} - especially now that we're prepared for it."
|
||||
|
||||
Bob (Scrum Master): "{user_name}, any final thoughts before we close?"
|
||||
Bob (Agile Delivery Lead): "{user_name}, any final thoughts before we close?"
|
||||
</output>
|
||||
|
||||
<action>WAIT for {user_name} to share final reflections</action>
|
||||
|
||||
<output>
|
||||
Bob (Scrum Master): [Acknowledges what {user_name} shared] "Thank you for that, {user_name}."
|
||||
Bob (Agile Delivery Lead): [Acknowledges what {user_name} shared] "Thank you for that, {user_name}."
|
||||
|
||||
Bob (Scrum Master): "Alright team - great work today. We learned a lot from Epic {{epic_number}}. Let's use these insights to make Epic {{next_epic_num}} even better."
|
||||
Bob (Agile Delivery Lead): "Alright team - great work today. We learned a lot from Epic {{epic_number}}. Let's use these insights to make Epic {{next_epic_num}} even better."
|
||||
|
||||
Bob (Scrum Master): "See you all when prep work is done. Meeting adjourned!"
|
||||
Bob (Agile Delivery Lead): "See you all when prep work is done. Meeting adjourned!"
|
||||
|
||||
═══════════════════════════════════════════════════════════
|
||||
</output>
|
||||
|
|
@ -1438,7 +1439,7 @@ Retrospective document was saved successfully, but {sprint_status_file} may need
|
|||
{{else}}
|
||||
|
||||
4. **Begin Epic {{next_epic_num}} when ready**
|
||||
- Start creating stories with SM agent's `create-story`
|
||||
- Start creating stories with ADL agent's `create-story`
|
||||
- Epic will be marked as `in-progress` automatically when first story is created
|
||||
- Ensure all critical path items are done first
|
||||
{{/if}}
|
||||
|
|
@ -1452,7 +1453,7 @@ Epic {{epic_number}} delivered {{completed_stories}} stories with {{velocity_sum
|
|||
|
||||
---
|
||||
|
||||
Bob (Scrum Master): "Great session today, {user_name}. The team did excellent work."
|
||||
Bob (Agile Delivery Lead): "Great session today, {user_name}. The team did excellent work."
|
||||
|
||||
Alice (Product Owner): "See you at epic planning!"
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue