Retrofit work tracking on an existing repo¶
Situation: Plans and ADRs already live under docs/; the team wants a
shared board (Notion, GitHub Projects, or later Jira) without moving plan truth
out of git. The repo has no hoen.yaml / Tracking yet.
Run: work-tracking — mode retrofit
Procedure, templates, and scripts live only in the skill. Pair with
plan-effort-estimate when scanning
existing *.effort.json.
What a good outcome looks like¶
- Primary backend chosen;
hoen.yamladded after asking (or explicitly skipped) AGENTS.md(and README/CONVENTIONS pointers) describe board sync rules- Active plans/ADRs have a slim
## Trackingtable (Plan ID, Work type, Board item) - Canonical board fields exist when permissions allow; otherwise values stamped for retry
- Effort-backed plans still validate via
validate-effort.mjs --scan