ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

feat(enterprise): add StRS and SyRS transition guidance to completion steps 

Product Brief completion (D3): Added Enterprise track guidance for StRS
creation as the logical next step, explaining how Product Brief sections
map to ISO 29148 Clause 7 StRS requirements.

Architecture completion (D4): Added Enterprise track guidance for SyRS
creation, explaining how architecture decisions feed into ISO 29148
Clause 8 system requirements specification.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Tolga Karatas 2026-02-16 01:29:01 +03:00
parent e8f76504af
commit 66bae0ece4
No known key found for this signature in database
GPG Key ID: C8389C243D70C4C9
2 changed files with 27 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
src/bmm/workflows/1-analysis/create-product-brief/steps/step-06-complete.md
View File

@ -107,9 +107,22 @@ Provide guidance on logical next workflows:
1. `create-ux-design` - UX research and design (can run parallel with PRD) 1. `create-ux-design` - UX research and design (can run parallel with PRD)
2. `domain-research` - Deep market or domain research (if needed) 2. `domain-research` - Deep market or domain research (if needed)
**Enterprise Track: StRS Creation (ISO 29148)**
If the project follows the **Enterprise** track, the Product Brief serves as the primary input for creating an ISO 29148 compliant Stakeholder Requirements Specification (StRS):
1. `create-strs` - Create Stakeholder Requirements Specification
- Product Brief vision → StRS business purpose and objectives
- Product Brief target users → StRS stakeholder profiles and user requirements
- Product Brief features → StRS operational requirements and system concept
- Product Brief constraints → StRS project constraints
The StRS extends the Product Brief with formal stakeholder analysis, operational scenarios, and project constraints required by ISO 29148 Clause 7. This is recommended before starting the PRD for Enterprise track projects.
**Strategic Considerations:** **Strategic Considerations:**
- The PRD workflow builds directly on this brief for detailed planning - The PRD workflow builds directly on this brief for detailed planning
- Enterprise track: Consider creating StRS before PRD for full traceability chain
- Consider team capacity and immediate priorities - Consider team capacity and immediate priorities
- Use brief to validate concept before committing to detailed work - Use brief to validate concept before committing to detailed work
- Brief can guide early technical feasibility discussions - Brief can guide early technical feasibility discussions

15
src/bmm/workflows/3-solutioning/create-architecture/steps/step-08-complete.md
View File

@ -39,7 +39,20 @@ status: 'complete'
completedAt: '{{current_date}}' completedAt: '{{current_date}}'
``` ```
### 3. Next Steps Guidance ### 3. Enterprise Track: SyRS Creation Guidance
If the project follows the **Enterprise** track (check PRD frontmatter for `track: enterprise`), inform the user:
"**Enterprise Track Note:** Your Architecture Document serves as a key input for the System Requirements Specification (SyRS). The SyRS extends your architectural decisions with ISO 29148 compliant system-level requirements including:
- System functional requirements derived from PRD FRs
- System interface specifications from your architecture interfaces
- Quality requirements (performance, security) with measurable targets
- Verification plan for each system requirement
**Recommended next step:** `create-syrs` (Create SyRS) to establish the system requirements baseline before proceeding to Epics & Stories."
### 4. Next Steps Guidance
Architecture complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create Architecture`. Architecture complete. Read fully and follow: `_bmad/core/tasks/help.md` with argument `Create Architecture`.