gh-levnikolaevich-claude-code-skills-full-development-workflow-skills/skills/ln-114-project-docs-creator/references/templates/requirements_template.md

Requirements Specification: {{PROJECT_NAME}}

Document Version: 1.0 Date: {{DATE}} Status: {{STATUS}} Standard Compliance: ISO/IEC/IEEE 29148:2018

---

1. Introduction

1.1 Purpose

This document specifies the functional requirements for {{PROJECT_NAME}}.

1.2 Scope

{{PROJECT_SCOPE}}

1.3 Intended Audience

• Development Team
• QA Team
• DevOps Team
• Technical Writers
• System Architects

1.4 References

• Project Charter: {{PROJECT_CHARTER_LINK}}
• Architecture Document: {{ARCHITECTURE_DOC_LINK}}
• Definition of Done: {{DOD_LINK}}

---

2. Overall Description

2.1 Product Perspective

{{PRODUCT_PERSPECTIVE}}

2.2 User Classes and Characteristics

{{USER_CLASSES}}

2.3 Operating Environment

{{OPERATING_ENVIRONMENT}}

---

3. Functional Requirements

3.1 User Management

{{FR_USER_MANAGEMENT}}

3.2 [Feature Group 2]

{{FR_FEATURE_GROUP_2}}

3.3 [Feature Group 3]

{{FR_FEATURE_GROUP_3}}

---

4. Acceptance Criteria (High-Level)

{{HIGH_LEVEL_ACCEPTANCE_CRITERIA}}

---

5. Constraints

5.1 Technical Constraints

{{TECHNICAL_CONSTRAINTS}}

5.2 Regulatory Constraints

{{REGULATORY_CONSTRAINTS}}

---

6. Assumptions and Dependencies

6.1 Assumptions

{{ASSUMPTIONS}}

6.2 Dependencies

{{DEPENDENCIES}}

---

7. Requirements Traceability

Requirement ID	Epic	User Story	Test Case	Status
FR-UM-001	Epic-001	US-001	TC-001	{{STATUS}}

---

8. Glossary

Term	Definition
{{TERM_1}}	{{DEFINITION_1}}

---

9. Appendices

Appendix A: MoSCoW Prioritization Summary

• MUST have: {{MUST_COUNT}} requirements
• SHOULD have: {{SHOULD_COUNT}} requirements
• COULD have: {{COULD_COUNT}} requirements
• WON'T have (this release): {{WONT_COUNT}} requirements

Appendix B: References

1. ISO/IEC/IEEE 29148:2018 - Systems and software engineering
2. OWASP ASVS (Application Security Verification Standard)
3. WCAG 2.1 (Web Content Accessibility Guidelines)

---

Maintenance

Last Updated: {{DATE}}

Update Triggers:

• New functional requirements identified during development
• New constraints or dependencies discovered
• Stakeholder feedback on requirements clarity
• Post-release feedback requiring requirement modifications
• MoSCoW prioritization changes

Verification:

• All FR-XXX-NNN requirements have acceptance criteria
• All FR-XXX-NNN requirements have MoSCoW priority (MUST/SHOULD/COULD/WON'T)
• Traceability matrix links requirements to epics/stories
• No orphaned requirements (all linked to business value)
• All placeholders replaced with actual content

---

Revision History

Version	Date	Author	Changes
1.0	{{DATE}}	{{AUTHOR}}	Initial version

---

Version: 3.0.0 (BREAKING: NFR sections removed completely per project policy) Template Last Updated: 2025-11-16