What problem does it solve? Teams lose traceability when lifecycle artifacts mix ownership, skip receivers, or use vague language, making phase handoffs impossible to verify. This Skill produces formal, standards-aligned artifacts that the next phase can consume without guessing. ## Core Features & Use Cases - Standards-based artifact selection: Maps each SDLC phase to its governing standard (ISO/IEC/IEEE 12207, 15289, 29148, 29119, IEEE 1016, 1012, and more) with recorded tailoring decisions. - Controlled-English writing profile: Enforces an STE-derived style with one requirement per sentence, stable IDs, and BCP 14 keywords for binding requirements. - Handoff gate enforcement: Validates incoming artifacts against explicit acceptance checks and returns a rejection note listing failed checks instead of silently repairing content. - Use Case: A product owner finishing a Software Requirements Specification uses this Skill to structure the SRS per ISO/IEC/IEEE 29148, link each requirement to stable IDs, and attach a handoff block the architect can verify before design work starts. ## Quick Start Use the lifecycle-documentation skill to draft a Software Requirements Specification for the authentication module with a handoff block addressed to the design phase.
