Summary
Add role-based sections in specs to differentiate contributions from Product, Architecture, and Engineering stakeholders.
Problem
InfoQ article emphasizes: "Different stakeholders participate differently" - Product (what/why), Architect (technical approach), Engineer (task execution).
Proposal
1. Role Markers in Specs
Add explicit sections:
- Product Perspective: Business value, user stories, acceptance criteria
- Architecture Perspective: Technical decisions, constraints, patterns
- Engineering Perspective: Implementation tasks, test strategy
2. Role-Specific Templates
- Opt-in template variants for different stakeholders
- Guidance on who approves what in workflow
3. Stakeholder Views
- Commands to filter/specify view (e.g.,
/spec.plan --stakeholder product)
Priority
Medium - Aligns with InfoQ enterprise patterns
Summary
Add role-based sections in specs to differentiate contributions from Product, Architecture, and Engineering stakeholders.
Problem
InfoQ article emphasizes: "Different stakeholders participate differently" - Product (what/why), Architect (technical approach), Engineer (task execution).
Proposal
1. Role Markers in Specs
Add explicit sections:
2. Role-Specific Templates
3. Stakeholder Views
/spec.plan --stakeholder product)Priority
Medium - Aligns with InfoQ enterprise patterns