Document Work
Repo docs that tracked work needs — then link from issue/PR.
What it is
Section titled “What it is”Repo docs that tracked work needs — then link from issue/PR. This practice is a skill-mapped TTP: when, why, and which command—not a full copy of the skill. Open the skill to execute.
Why it works
Section titled “Why it works”Linking issues/PRs to durable docs prevents tribal knowledge. GitHub’s model of closing keywords and linked work keeps the change set auditable; Diátaxis keeps the doc type honest (how-to vs reference).
When to use it
Section titled “When to use it”When the situation matches the one-liner above and Orientation (or your project path) says this is the fire to touch now.
- Invoke the skill; follow its safety rules
- Keep one write owner; collect evidence before claiming done
- Hand off to the next practice instead of boiling the ocean
- Skip orientation when you’re lost
- Spawn overlapping agents to “go faster”
- Treat the practice as done without evidence
Related concepts
Section titled “Related concepts”04-evidence-over-vibes, 06-work-ownership
Further reading
Section titled “Further reading”See also the handbook Sources & grounding bibliography.
Agent skill
Section titled “Agent skill”issues document · pulls document · document-it