arthur-debert/rustloc

implementing

Implement one shipit task as a role-scoped implementer. Use when an agent is spawned to build a standalone issue or epic workstream: make the code/test change in its Tree, verify it, open a draft PR with context, run the PR engine once, then stop before…

원문 언어: 영어

shepherding-prs

Shepherd one shipit draft PR through review-addressing rounds. Use when an agent is assigned to a PR after it is open: read current review threads, address findings in severity order, fix or reply, resolve threads, verify, push the round, and park without…

원문 언어: 영어

coordinating

Coordinate shipit's delegated dev cycle. Use when the top-level agent is orchestrating a standalone issue, epic, workstream set, or PR lifecycle: gather context, brief implementers and shepherds, drive the PR engine, wait, flip ready, and stop at the human…

원문 언어: 영어

grill-me-with-docs

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and…

원문 언어: 영어

lex-primer

Primer for writing correct Lex documents. Use when: (1) Writing or generating .lex content (2) Understanding Lex syntax (it is NOT Markdown) (3) Reviewing whether a .lex file is syntactically correct (4) Converting content to Lex format

원문 언어: 영어

planning

Plan a new feature or epic from loose ideas through to issues. Drives ideation → overview checkpoint → Spec → ADRs → docs PR (Leg A), then epic decomposition → issues (Leg B). Use at the START of a feature/epic, before any code. NOT for single fixes — the…

원문 언어: 영어

shipit-session-status

Show the dev-cycle story of the current session — the flow view of spawn/review/planning milestones from shipit's durable log. Use when the user asks what happened this session, wants a session status, or asks about an epic's progress.

원문 언어: 영어

to-spec

Turn the current conversation context into an authoritative feature Spec and write it to docs/spec/. Use when user wants to create the first planning artifact from ideation or a blessed overview, before the architectural grill (`/grill-me-with-docs`).

원문 언어: 영어

to-tickets

Break a Spec into one or more epic tracker issues plus independently-grabbable Work Stream sub-issues on the project issue tracker, using tracer-bullet vertical slices. Use when user wants to convert a plan/Spec into epics and work streams, create…

원문 언어: 영어