/rails-flow:brain-reviewWeekly maintenance sweep of docs/brain — flag stale STATUS/evidence, surface decisions-vs-PRD drift and contradictions, compress patterns, and check hypotheses against evidence. Read-only analysis + proposed edits; never rewrites silently.
/rails-flow:brain-syncPublish this project's brain status to a shared cross-project brain repo, and consume sibling projects' status — so agentic flows in separate repos coordinate WITHOUT cloning each other. Uses gh (single-file reads/writes), git as source of truth.
/rails-flow:brainInstitutionalize a lesson or decision as a docs/brain memo, indexed in MEMORY.md
/rails-flow:briefTurn a vague ask into something buildable — ingest whatever documents or code already exist, interview only the genuine gaps, and write docs/brain/BRIEF.md as an index over the sources rather than a copy of them.
/rails-flow:claim-coordinatorTake the machine-wide coordinator role for THIS session, from inside it, without going to the other session to fight for it. The override a session was elected the wrong role needs: same claim as RAILS_FLOW_ROLE=coordinator, no restart.
/rails-flow:coordinateCross-session coordination computed from the repository — who is idle with finished work, which announced paths collide, which conflicts are generated and which are the author's judgement. Reports and messages; it never merges, never writes, and stays silent on single-session work.
/rails-flow:curateConvert project docs (PRDs, branding, architecture) into project-local skills and keep them synced as documentation evolves
/rails-flow:drivePick the one next action from repository state and say whether you may take it alone — the autonomous driver's tick, with named stopping conditions and a configurable decision-rights policy.
/rails-flow:escalateAsk the human a question on a GitHub issue, park the thread, and pick the answer up on a later tick — the async human-in-the-loop. Pillar 3 of the autonomous flow driver. Nothing blocks: the human answers on their own schedule, the flow notices whenever it next cycles, and the state survives a resta
/rails-flow:explainExplain the built system back to its human owner — plain-language docs/GUIDE.md with mermaid diagrams, section-scoped and idempotent. Also explains a PLAN before the build, so a wrong plan is rejected before it costs a build cycle.
/rails-flow:featureOrchestrated feature development — plan, spec-first implementation, quality gates, PR, tool-gated merge
/rails-flow:fixSystematically fix a bug or a phased review backlog — one issue at a time, each proven by a spec
/rails-flow:graphRegenerate the living architecture graph — docs/architecture/{graph.json,index.html,graph.md} — from routes, app/** and db/schema.rb (and every other project-owned db/*_schema.rb a second database dumps). Also runs the drift check and the release-notes delta.
/rails-flow:handoffWrite the work order for a unit of work — one self-contained file an executor can run from with no conversation history, carrying the goal, the criteria it is graded by, the scope, the stop conditions, and how to verify.
/rails-flow:issuesTriage the repo's open issues and work them through the matching pipeline — verify the issue's claims before editing, check that nothing it waits on is still open, group issues that are one change wearing several numbers, each PR closing what it fixed
/rails-flow:pr-commentsSweep a PR's review feedback — fix every actionable comment on-branch or fold it into a tracked repo issue; the PR must close clean before any next task
/rails-flow:reportReport toolchain friction (a rails-flow/qa-flow/pipeline/design-flow/rails-stack bug, wrong guidance, a generated component that won''t build, or a feature idea) upstream as a structured, deduped, version-pinned issue. Drafts by default; add "MODE: FILE" to actually file.
/rails-flow:retroCount the review findings that recur across PRs and propose a check or a doctrine line for each — a report in docs/brain/retro/, nothing else changed
/rails-flow:reviewFull parallel codebase review — seven specialist passes producing a phased, /fix-consumable report
/rails-flow:secure-designThreat-model a plan that adds a security boundary, before its criteria.
/rails-flow:setup-flowScaffold, update, or repair the rails-flow conventions in this project — CLAUDE.md, GUARDRAILS.md, docs/brain. Idempotent and safe on customized repos; can diagnose and propose fixes for a defective CLAUDE.md (fact contradictions, broken safety rules) as approved diffs, never touching deliberate cus
/rails-flow:sliceBreak a spec, a brief or an issue into dependency-ordered vertical slices — draft each with criteria and blocking edges, check the plan, show it for approval, then file one labelled issue per slice so /rails-flow:issues can work the frontier.
/rails-flow:specTurn an idea or a brief into a technical spec before anything is built — read what exists, grill only the gaps one question at a time, write terms and decisions down as they settle, and save docs/product/specs/<slug>.md for /rails-flow:feature to plan from.
/rails-flow:toolchain-auditAudit an existing project's whole claude-skills setup — update the toolchain, verify the scaffolding, run every check that applies, and report in three states. The broad sibling of /rails-flow:toolchain-check, which only resolves versions.
/rails-flow:toolchain-checkCheck whether this project's installed claude-skills toolchain is behind what is published, and carry a durable marker across the restart an update requires. Pillar 1 of the autonomous flow driver — run it before any unattended work so the driver never builds on a stale toolchain.
/rails-flow:wrapThe coordinator's handoff round, end to end — send it to every implementation session, wait out heavy runs instead of interrupting them, check every reply against git, then write the board rows and the coordinator handoff. Coordinator only.