@open-tomato/rafa 0.22.0 → 0.24.0

package/README.md

@@ -57,6 +57,7 @@ your accounts.
   | `rafa skill search` | 🪙 one `haiku` session reading the twelve best-ranked files, one per kind with `--all`; with `--no-model`, nothing |
   | `rafa agent search` | 🪙 the same as `rafa skill search`, over agent definitions |
   | `rafa next` | 🪙 when the step it runs is one of the above; it asks before each step |
+  | `rafa epic close` | 🪙 one verification planning session and one session per check; nothing while a member is open |
 
   The same 🪙 marks appear in `rafa --help` at all levels and in `rafa describe` output.
 
@@ -348,13 +349,23 @@ from GitHub Issues:
   machine-specific failures a run meets stay off your public tracker.
   Specs in an epic may not carry two `epic:` labels; `rafa issue ready`
   refuses the second one.
+- **Boards and switching.** Most projects stay on one board. A project
+  with several teams can hold one board per team, each with its own
+  owner and owned folders listed in `Owner:` and `Owns:` lines, and tied
+  to the repository's `CODEOWNERS` file. `rafa switch <n>` moves to that
+  board's epic and position, `rafa board list` shows all boards, and
+  `rafa status` prints where you stand. A switch made by hand re-homes; pass
+  `--no-rehome` to keep your home and go back to it later. The position
+  file `.rafa/position.json` holds your current place, where you were, and
+  where you came from — the same two-slot pattern as `cd -` and
+  `git checkout -`, plus a home anchor.
 - **Other trackers.** GitHub Issues is what works today. Linear support
   is being ported from the project rafa grew out of, as an optional
   add-on in a later version. For anything else, open or upvote a request
   in [the issues](https://github.com/open-tomato/rafa/issues).
 
 The full guide, with the spec template explained, a prompt for drafting
-a spec, epics and every gate in order, is
+a spec, epics, boards and every gate in order, is
 [docs/specs-and-roadmap.md](docs/specs-and-roadmap.md).
 
 ## From a checkout
@@ -480,6 +491,9 @@ and a line here is ticked by the change that finishes the feature.
 - ✅ Know which skills earn their place and which are ignored
 - ✅ rafa learns from its own runs: what one task works out is handed
   to the tasks that need it later
+- ✅ Every change to an epic is a command that leaves a trail: `rafa epic new`,
+  `defer`, `promote`, `move`, `close` with a verification gate, `cancel`, and
+  the end-of-epic lines in `rafa next`
 - ⬜ Skills and lessons shared across projects and machines
 - ⬜ Config as code: a typed `rafa.config.ts` holding your settings, your
   passes and your flows, with today's behaviour as the default