What problem does it solve? Writing a formal Software Requirements Specification is error-prone: requirements end up ambiguous, untraceable, mixed with design decisions, or scattered without unique IDs. This Skill guides you through producing a complete, reviewable SRS that organizes functional requirements by system feature and covers data, interfaces, quality attributes, and constraints. ## Core Features & Use Cases - Structured SRS Template: A fill-in template covering introduction, overall description, system features, data requirements, external interfaces, quality attributes, and constraints, aligned with IEEE 830 / ISO/IEC/IEEE 29148. - Requirement Writing Standards: Enforces unique persistent IDs, "shall" phrasing, atomic testable statements, and EARS patterns (ubiquitous, event-driven, state-driven, unwanted behavior, optional). - Worked Example: Includes a ChemTrack chemical inventory SRS excerpt showing labeled requirements with rationale, source, priority, and business rule references. - Use Case: A client requires a formal, baselined requirements document before approving design. Use this Skill to organize 200+ requirements into a coherent, traceable SRS ready for stakeholder sign-off. ## Quick Start Ask the agent to draft an SRS for your project using the srs-document template, organizing functional requirements by system feature with unique IDs and EARS-style shall statements.
