release

Files (1)

• SKILL.md

SKILL.md (first lines)

# The release loop

1. **Milestone first** from `rails template milestone`. Step 0 is "the operator did
   <task> on <target>". Every step has a `step:` id and an `expect:` that could come out the other way.
2. **Issues**: one per step, consolidated where one step is one PR-sized unit. Each has a falsifiable
   "Done when".
3. **Spec only where the intent cannot carry it** (a seam, a new concept, a model in the loop, a
   trust boundary): `rails template spec`, one authoring pass, one adversarial pass (`design-review`), build.
4. **Contract first.** The walls the release adds (contracts, settings, auth rows, concepts, limits)
   land in its FIRST PR, with tests that fail on a planted defect.
5. **The demo runs from PR 1**, failing honestly, so wrongness is visible on day one.
6. **Build each line of work through the `rails` loop.** WIP is one app: a second release milestone
   waits for the first's `used`.
7. **Close** with `rails close <milestone>`: it needs the operator's `used #<n>` and no open issue
   (the raw API close is refused). Still on you until the oracle lands: every step id passing in a
   walk receipt on the named target, and `approve` for every rule table touched.
8. **Retro**: run the `retro` skill.

From vancourse/apex, MIT.

More from vancourse/apex