Initial commit
This commit is contained in:
128
skills/spec-author/templates/business-requirement.md
Normal file
128
skills/spec-author/templates/business-requirement.md
Normal file
@@ -0,0 +1,128 @@
|
||||
# <!-- TODO: [BRD-XXX] Business Requirement Title -->
|
||||
|
||||
## Metadata
|
||||
|
||||
- **Document ID**: <!-- TODO: BRD-XXX-short-name -->
|
||||
- **Status**: <!-- TODO: Draft | In Review | Approved | Implemented -->
|
||||
- **Author**: <!-- TODO: Your Name -->
|
||||
- **Created**: <!-- TODO: YYYY-MM-DD -->
|
||||
- **Last Updated**: <!-- TODO: YYYY-MM-DD -->
|
||||
- **Stakeholders**: <!-- TODO: List key stakeholders -->
|
||||
- **Priority**: <!-- TODO: Critical | High | Medium | Low -->
|
||||
|
||||
## Description
|
||||
|
||||
<!-- TODO: Describe the business problem or opportunity. What challenge are we addressing? -->
|
||||
|
||||
### Background
|
||||
|
||||
<!-- TODO: Provide context about the current situation and why this requirement emerged. -->
|
||||
|
||||
### Problem Statement
|
||||
|
||||
<!-- TODO: Clear, concise statement of the problem this requirement solves. -->
|
||||
|
||||
## Business Value
|
||||
|
||||
<!-- TODO: Explain the expected business impact and benefits. -->
|
||||
|
||||
### Expected Outcomes
|
||||
|
||||
<!-- TODO: List expected outcomes, e.g.:
|
||||
- **Outcome 1**: Brief description of expected result
|
||||
- **Outcome 2**: Brief description of expected result
|
||||
-->
|
||||
|
||||
### Strategic Alignment
|
||||
|
||||
<!-- TODO: How does this align with broader business goals or strategy? -->
|
||||
|
||||
## Stakeholders
|
||||
|
||||
<!-- TODO: Document stakeholders in table format:
|
||||
| Role | Name/Team | Responsibility | Contact |
|
||||
|------|-----------|----------------|---------|
|
||||
| Business Owner | | Decision maker | |
|
||||
| Product Owner | | Requirements definition | |
|
||||
| End Users | | Primary users | |
|
||||
| Technical Lead | | Implementation oversight | |
|
||||
-->
|
||||
|
||||
## User Stories
|
||||
|
||||
<!-- TODO: Document user stories in table format:
|
||||
| ID | As a... | I want to... | So that... | Priority |
|
||||
|----|---------|--------------|------------|----------|
|
||||
| US-1 | [role] | [capability] | [benefit] | High |
|
||||
| US-2 | [role] | [capability] | [benefit] | Medium |
|
||||
-->
|
||||
|
||||
## Assumptions
|
||||
|
||||
<!-- TODO: List assumptions being made about users, systems, or business conditions.
|
||||
1. Assumption about user behavior or system capability
|
||||
2. Assumption about resources or timeline
|
||||
3. Assumption about business context
|
||||
-->
|
||||
|
||||
## Constraints
|
||||
|
||||
<!-- TODO: Identify limitations or restrictions that must be respected. -->
|
||||
|
||||
### Business Constraints
|
||||
|
||||
<!-- TODO: Document business constraints, e.g., budget limitations, regulatory requirements, market timing -->
|
||||
|
||||
### Technical Constraints
|
||||
|
||||
<!-- TODO: Document technical constraints, e.g., system limitations, integration requirements, platform restrictions -->
|
||||
|
||||
### Organizational Constraints
|
||||
|
||||
<!-- TODO: Document organizational constraints, e.g., team capacity, skill requirements, policy limitations -->
|
||||
|
||||
## Dependencies
|
||||
|
||||
<!-- TODO: List dependencies on other projects, systems, or decisions in table format:
|
||||
| Dependency | Type | Status | Impact if Blocked |
|
||||
|------------|------|--------|-------------------|
|
||||
| [Project/System] | Internal/External | In Progress | High/Medium/Low |
|
||||
-->
|
||||
|
||||
## Risks
|
||||
|
||||
<!-- TODO: Identify potential risks and mitigation strategies in table format:
|
||||
| Risk | Likelihood | Impact | Mitigation Strategy |
|
||||
|------|------------|--------|---------------------|
|
||||
| [Risk description] | High/Med/Low | High/Med/Low | [How to mitigate] |
|
||||
-->
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
<!-- TODO: Define what "done" looks like from a business perspective.
|
||||
1. **Criterion 1**: Specific, measurable condition that must be met
|
||||
2. **Criterion 2**: Specific, measurable condition that must be met
|
||||
3. **Criterion 3**: Specific, measurable condition that must be met
|
||||
-->
|
||||
|
||||
## Success Metrics
|
||||
|
||||
<!-- TODO: Define how success will be measured after implementation in table format:
|
||||
| Metric | Current Baseline | Target | Measurement Method |
|
||||
|--------|------------------|--------|-------------------|
|
||||
| [KPI name] | [Current value] | [Target value] | [How measured] |
|
||||
-->
|
||||
|
||||
### Time to Value
|
||||
|
||||
<!-- TODO: When do we expect to see results? What's the measurement timeline? -->
|
||||
|
||||
## Approval
|
||||
|
||||
<!-- TODO: OPTIONAL - Remove if not needed. Sign-off section for key stakeholders:
|
||||
| Role | Name | Signature | Date |
|
||||
|------|------|-----------|------|
|
||||
| Business Owner | | | |
|
||||
| Product Owner | | | |
|
||||
| Technical Lead | | | |
|
||||
-->
|
||||
Reference in New Issue
Block a user