What problem does it solve? Project requirements and design documents drift out of sync with accepted user intent and delivered implementation, leaving teams without a trustworthy contract. This Skill keeps canonical docs/requirements.md and docs/design.md current by classifying every direct user prompt, reconciling durable intent before implementation, and recording verified delivery evidence afterward. ## Core Features & Use Cases - Statement-level intent classification: Every direct root-user prompt is classified as durable requirement intent or non-lifecycle, so unrelated requests leave specs untouched. - Atomic paired publication: Requirements and design are published together through a compare-and-set transaction bound to Git HEAD and both prior file digests, with rollback on partial failure. - Schema v2 validation and migration: Independent requirement status, design readiness, and delivery axes are validated, and legacy Task Implementer or v1 documents migrate with journaled backups and recovery. - Use Case: A user asks an agent to add a new CLI behavior. The skill records the durable requirement and a ready design before coding, then after tests pass advances delivery to verified and the requirement to satisfied. ## Quick Start Ask the agent to use maintain-project-specs to reconcile the selected project's requirements and design documents with the latest accepted intent and implementation evidence.
