Files
gstack/captain/templates/AGENTS.md
T
Garry Tanandcapy-ai[bot] 4d48d39e51 v1.91.253.0 feat(captain): /captain skill (also /crew), crew templates and docs/captain.md for running a crew from one controller (#3473)
* feat(captain): /captain skill (also /crew), crew templates and docs/captain.md for running a crew from one controller

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* chore(captain): regenerate SKILL.md at main's version

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* feat(captain): AGENTS.md and NOTES.md templates, roles, ship lane sequence, owner device and lessons loop in docs/captain.md; owner-brief closes with the do-it reply

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(captain): review pass 1: 'do it' parses as rec, READY template matches the tool's lines, slot-2 and freeze wording, mergeChangelogs named, parameter lists and doc numbers aligned

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix(captain): align the slot-call BASE merge, freeze repair and severe-race wording across skill, CREW.md and docs; router routes on phrases; receipt head width as printed

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* feat(captain): CREW.md template becomes pointers plus parameters; every crew rule gets a canonical home in gstack (lane discipline, outside contributions, stale READYs, standing spend, the lane side of flaky reruns in docs/captain.md; the rule-to-home map)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-10-26 18:04:22 +00:00

1.9 KiB

<CREW_NAME> standing rules

The controller's own file. Scope instructions: every thread in the crew reads it. Each rule that came from the owner keeps the date and the exact words, so lanes can cite it as a standing approval instead of asking again. Append; never rewrite an owner's words.

Mandate (, )

"<the owner's words for what this crew is for>"

  • Every -* thread in is in the crew. New threads the owner starts are added too.
  • Watch issues and PRs. Start lanes for severe user-reported bugs no live thread has claimed (the severity bar is below).
  • Severity first: S1 is a broken install or upgrade, data loss, a security result that is wrong, or BASE red. S2 is a broken workflow with no workaround. Everything else is batched.

Merging (, : "")

  • One controller merges, through a train (/captain, the merge-train section). Lanes send READY and never merge. Standing approval to merge when green: "".
  • A merge outside a train costs a backstop gate; none without the owner's words.

Spend (, : "")

  • Pre-approved: train gates, bisects, the backstop, screens, focused paid cases. Cap per rerun: . Over the cap is a fresh ask.

Asks to the owner (, : "")

  • Plain language, each option with what it is, why it matters, what each answer does and the cost. The recommended one-word reply is the default. Every ask ends with "do it": every recommendation at full scope, follow-ons included, no further ask.

Parallelism (, : "")

  • Keep about lanes working on disjoint files whenever there is backlog. Serial steps stay serial only where the tooling requires it: one train's slots, version stamps, edits to a shared file.

Decisions log