Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route implement/fix/build requests to /crew:run, which decides the full workflow. (Function: convene the advisory team, write the change, and produce a review-ready PR or local branch; never merges.).
Create a crew.config.yaml at the repo root, pre-filled from the example template and tuned to the detected stack (test/lint commands, docs index). Use when asked to "set up crew" / "configure crew" / "create crew config", or invoked as /crew:init-config.
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route knowledge-capture requests to /crew:run, which decides the full workflow. (Function: capture durable decisions, rationale, and gotchas into the knowledge base, deduped.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route backlog/catch-up requests to /crew:run, which decides the full workflow. (Function: find and advance stalled issues/PRs or ledger tasks, bounded; never merges.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route address-review/fix-feedback requests to /crew:run, which decides the full workflow. (Function: apply review feedback on a crew PR or local branch, bounded by maxreviewiterations; never merges.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route review requests to /crew:run, which decides the full workflow. (Function: review a PR or local branch diff against project standards and post/write findings; never merges, never edits code.).
A standing crew of senior developer agents and the team's single entry point — its job is best-in-class implementation, coding standards, and project health. Use it for essentially ANY software-development request in this repo, whether or not the user says "crew": implementing a feature, fixing a bug, reviewing or…
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route cleanup/dead-code requests to /crew:run, which decides the full workflow. (Function: propose bounded, evidence-backed cleanups validated against the test suite; never touches protected paths, never merges.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route bug/triage/fix requests to /crew:run, which decides the full workflow. (Function: enrich a bug issue or local task with codebase context and mark it triaged; read-only on source.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route task/feature/triage requests to /crew:run, which decides the full workflow. (Function: enrich a task/feature issue or local task with codebase context and mark it triaged; read-only on source.).
Internal crew primitive, dispatched by /crew:run — do not invoke directly or select it for a user request; route docs requests to /crew:run, which decides the full workflow. (Function: update documentation for an issue/PR or local change, verified against the code.).
Connect this repo to your evals.tessary.ai project and wire the platform's tools into Claude Code, so you can assess call sites, inspect graders, query failing traces, and read the cases and root-cause reports it has opened, natively. Use when the user says "connect to evals", "link this repo to Tessary", "connect to…
Derive a v3 SOP-conformance file for a call site — read the agent's whole instruction surface and distill it into intents, an atomic observation vocabulary, and rules, then lint it with the bundled validator. Run after /evals:instrument so the SOP names a real call site. Use when the user says "derive an SOP", "author…
Stamp tessary.callsite.id onto the spans your LLM calls already emit, so production telemetry binds to the call sites graders are keyed on. Run after /evals:connect — it is what makes the platform's observer able to author graders for this repo. Use when the user says "instrument my call sites", "tag call sites", "why…
Re-verify a repo's v3 SOP files against the current instruction surface after code changes — propose edits, retirements, and additions with evidence, then re-lint. The per-commit maintenance flow for what /evals:derive-sop authored. Use when the user says "reconcile the SOP", "is the SOP still true", "update the SOP…