What problem does it solve? Documentation often drifts out of sync with the code it describes, leaving engineers with stale commands, wrong signatures, and misleading examples. This Skill ensures documentation is written after behavior ships and verified against the actual source of truth. ## Core Features & Use Cases - Ship-time documentation: Write README, usage guides, and API/interface docs that match the real code, with signatures, parameters, return shapes, and errors pulled directly from the source. - Architecture Decision Records: Capture ADRs for decisions with lasting consequences, including context, rejected alternatives, and accepted trade-offs. - Verification against behavior: Run every documented command and check every example against shipped behavior before considering docs complete. - Use Case: After merging a new CLI feature, use this Skill to update the README with a working example, document the new flags exactly as implemented, and record an ADR explaining why the interface was designed that way. ## Quick Start Use the documentation skill to write a README and API reference for the feature that just shipped, verifying every command and example against the actual code.
