External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

architecture name standardization

Browse Source
This commit is contained in:
Brian Madison
2025-10-20 19:01:18 -05:00
parent 60475ac6f8
commit b8db0806ed
21 changed files with 42 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/modules/bmm/workflows/4-implementation/epic-tech-context/README.md
View File

@@ -2,7 +2,7 @@
## Overview
Generate a comprehensive Technical Specification for a single epic from PRD, Epics file and Solution Architecture to produce a document with full acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
Generate a comprehensive Technical Specification for a single epic from PRD, Epics file and Architecture to produce a document with full acceptance criteria and traceability mapping. Creates detailed implementation guidance that bridges business requirements with technical execution.
## Key Features
@@ -35,7 +35,7 @@ workflow tech-spec --input PRD.md --input architecture.md --input front-end-spec
- **output_folder**: Location for generated technical specification
- **epic_id**: Used in output filename (extracted from PRD or prompted)
- **recommended_inputs**: PRD, solution-architecture, front-end spec, brownfield notes
- **recommended_inputs**: PRD, architecture, front-end spec, brownfield notes
## Workflow Structure
@@ -104,7 +104,7 @@ tech-spec/
### Output Structure
1. **Overview and Scope** - Project context and boundaries
2. **System Architecture Alignment** - Connection to solution-architecture
2. **System Architecture Alignment** - Connection to architecture
3. **Detailed Design** - Services, data models, APIs, and workflows
4. **Non-Functional Requirements** - Performance, security, reliability, observability
5. **Dependencies and Integrations** - External systems and technical dependencies
@@ -116,7 +116,7 @@ tech-spec/
## Requirements
- **PRD Document**: Product Requirements Document with clear acceptance criteria
- **Architecture Document**: solution-architecture or technical design
- **Architecture Document**: architecture or technical design
- **Repository Access**: For dependency analysis and framework detection
- **Epic Context**: Clear epic identification and scope definition

6
src/modules/bmm/workflows/4-implementation/epic-tech-context/instructions.md
View File

@@ -30,11 +30,11 @@
Status file shows project_level = {{project_level}}.
Tech-spec workflow is typically only needed for Level 3-4 projects.
For Level 0-2, solution-architecture usually generates tech specs automatically.
For Level 0-2, architecture usually generates tech specs automatically.
Options:
1. Continue anyway (manual tech spec generation)
2. Exit (check if solution-architecture already generated tech specs)
2. Exit (check if architecture already generated tech specs)
3. Run workflow-status to verify project configuration
What would you like to do?</ask>
@@ -47,7 +47,7 @@ What would you like to do?</ask>
The status file tracks progress across all workflows and stores project configuration.
Note: This workflow is typically invoked automatically by solution-architecture, or manually for JIT epic tech specs.
Note: This workflow is typically invoked automatically by architecture, or manually for JIT epic tech specs.
Options:
1. Run workflow-status first to create the status file (recommended)