rjv-work-planlisted
Install: claude install-skill rjvim/ai-skills
# Work plan: branch-scoped working memory
**The branch is the unit of work. One committed plan per branch is its memory.**
The plan holds volatile state: what we are doing and where we stopped. Durable
truth lives in the docs `rjv-spec-driven` owns: spec in `_docs/features/`,
glossary in `CONTEXT.md`, ADRs in `docs/adr/`. The plan links to durable docs
and never copies them.
- `.plans/<name>.md` is the working memory for one branch. It is committed, so
any agent on any machine that checks out the branch resumes from it.
- **Each plan declares `Branch: <name>` in its header.** The filename can be any
readable topic name. Resume finds the plan whose `Branch:` matches
`git branch --show-current`. Git branches are the active-work index: there is
no `RESUME.md` or other index file. Concurrent work runs on concurrent branches
(or worktrees), each with its own committed plan.
- **A plan is never deleted.** It is archived on merge and kept. It moves to `.plans/shipped/` with a
final status and dates. Top-level `.plans/*.md` is work in flight;
`.plans/shipped/` is the delivery record. The lifecycle continues past merge
into maintenance; see [`LIFECYCLE.md`](./LIFECYCLE.md).
The same files serve Claude Code, Codex and any other agent. Reference this
skill from AGENTS.md so every agent follows it.
## Authorship: the human's identity only
**Leave AI authorship and generator credit out of everything you write, unless
the human explicitly asks for it.** That covers com