Initial commit

skills/spec-author/templates/technical-requirement.md

@@ -0,0 +1,101 @@
+### Technical Requirement
+
+# <!-- Title with ID. Example: #[TRQ-001] Implement Real-Time Notification System -->
+
+**Priority:** <!-- critical | high | medium | low | nice-to-have -->
+
+## Description
+
+<!-- What technical problem are we solving? Describe the technical challenge and why this approach matters. -->
+
+## Business Requirements Addressed
+
+<!-- List business requirements this technical solution fulfills:
+- [BRD-XXX] Requirement Name - How this implementation addresses it
+- [BRD-YYY] Another Requirement - Connection to technical solution
+-->
+
+## Technical Requirements
+
+<!-- Specific technical specifications that must be implemented:
+
+1. **[TR-001] Requirement Title**
+   - Clear, measurable technical requirement
+   - Include specific details (protocols, formats, standards)
+
+2. **[TR-002] Another Requirement**
+   - Focus on what needs to be built
+   - Be specific about constraints and expectations
+-->
+
+### Implementation Approach
+
+<!-- High-level technical strategy:
+- Overall architecture pattern
+- Key technologies and frameworks
+- Integration points with existing systems
+- Critical design decisions
+-->
+
+### Key Design Decisions
+
+<!-- Document important technical choices:
+
+- **Decision:** What was decided
+  - **Rationale:** Why this approach was chosen
+  - **Tradeoffs:** Alternatives considered and why they were rejected
+-->
+
+## Technical Acceptance Criteria
+
+<!-- REQUIRED: Measurable criteria to verify implementation. Each criterion should be testable.
+
+### [TAC-001] Criterion Title
+**Description:** What must be true for this to be satisfied
+**Verification:** How this will be tested (unit tests, integration tests, manual verification)
+
+### [TAC-002] Another Criterion
+**Description:** Clear, specific requirement
+**Verification:** Testing approach
+-->
+
+## Dependencies
+
+### Technical Dependencies
+
+<!-- Required libraries, services, and systems:
+- **Package/Service Name** (version) - Purpose | Risk: Low/Medium/High
+- **API/Service** - Integration purpose | Risk: Low/Medium/High
+-->
+
+### Specification Dependencies
+
+<!-- Other specs that must be completed first:
+- [SPEC-XXX] Specification Name - Why this is a dependency
+-->
+
+### Constraints
+
+<!-- Technical limitations and requirements:
+- **Performance:** Response time, throughput requirements
+- **Scalability:** Load handling expectations
+- **Security:** Authentication, authorization, data protection
+- **Compatibility:** Browser, platform, version requirements
+-->
+
+## Implementation Notes
+
+<!-- Important technical considerations:
+
+### Key Considerations
+- **[Consideration Name]:** What to watch out for
+  - **Action:** How to address it
+
+### Migration Strategy
+<!-- If applicable, approach for transitioning from existing implementation -->
+
+### Error Handling
+<!-- Expected error scenarios and handling approach -->
+
+### Testing Strategy
+<!-- Unit, integration, and end-to-end testing approach -->