j.doc

What problem does it solve? Keeping project documentation accurate is hard when READMEs, API references, and changelogs drift out of sync with actual code and completed work. This Skill regenerates entire documentation files from a resolved objective and gathered evidence, replacing stale content in one authoritative write. ## Core Features & Use Cases - Objective-driven generation: Resolves a target path (README.md, docs/API.md, docs/CLI.md, docs/CONTRIBUTING.md, CHANGELOG.md, docs/STRATEGY.md) to a documented objective with required sections via a YAML rule table, and stops to ask when the target is unknown. - Evidence-based synthesis: Builds a synthesis context from user instructions, scrum-board items, codebase evidence, and git history, while preserving still-valid maintainer intent from the existing file. - Provenance tracking: Runs a resolver script that scans board epics, stories, and tasks for docs annotations to derive a last_update frontmatter date, falling back to unknown when no provenance exists. - Use Case: After a sprint completes, run /doc to regenerate the project README with current features and getting-started steps, or /doc docs/API.md to rebuild the API reference grounded in real endpoints. ## Quick Start Ask the agent to run /doc with no arguments to regenerate the project README, or provide a target path such as /doc docs/API.md to regenerate that specific document.