Requirements Authoring

Author a Product Requirements Document (PRD) or Software Requirements Specification (SRS) that any startup can adopt from day one, per ISO/IEEE 830 and ISO/IEC/IEEE 29148:2018, using the bare SRS template vendored from jam01/SRS-Template (CC0). Use this skill when the user mentions "PRD", "SRS", "product requirements", "software requirements specification", "especificación de requisitos", "requisitos de producto", "requisitos de software", "29148", "IEEE 830", "write the requirements", "requirement spec", "write the spec for this feature", "convertir la idea en requisitos", or any situation where a fractional CTO needs to formalize a client's product idea into verifiable, testable requirements BEFORE any code or OpenSpec is written. This is the FRONT DOOR of the requirements-first pipeline: PRD first, OpenSpec derived from the PRD, Linear issues with Bilingual briefs, then the /opsx-* workflow. NOT for authoring operational SOPs (that is /sop-authoring) nor contracts.

chimeranext Updated 4 repo stars

File contents

chimeranext/better-toolkits commit b42b8db998

Frequently asked questions

npx get-skill add chimeranext/requirements-authoring