update-project-docslisted
Install: claude install-skill waynesutton/builder-skills
# Update project docs
Activate with `/update`, `@update`, `update project docs`, or `sync project docs`.
Three files describe a project to the next person who opens it. Keep them true.
| File | Answers |
| --- | --- |
| `task.md` | What is planned, in flight, and done |
| `changelog.md` | What changed for users, by version and date |
| `files.md` | What each file is for |
Truth comes from the repo, not from the conversation. If the diff does not show it, it did not ship.
## Run the sync
1. Find the root. `git rev-parse --show-toplevel`, or the workspace root without git.
2. Collect evidence. `git log --date=short -n 20`, `git status --short`, `git diff --stat`, and for the current change `git diff HEAD --stat` or the staged diff. See [references/evidence-rules.md](references/evidence-rules.md) for what counts.
3. Read all three files as they are. Note the last logged date and the last completed task.
4. Update each file. Rules below.
5. Check idempotency. If nothing new landed since the last entry, change nothing and say so.
6. Scan for secrets and personal data before saving. See the redaction section.
7. Print the commit message. Rules below.
8. Report in a few lines. Show the new changelog entry or say the docs were already current.
## task.md
Sections: `## To Do`, `## In Progress`, `## Completed`.
- Move an item to Completed only if its verification step ran. If the PRD lists a check that has not run, leave it In Progress and say which check is pending.
- Complet