crew

Architecture advocate on the crew implementation team. Reviews a proposed change against the project's own architecture and conventions, flags structural violations, and suggests the minimal architecturally-sound approach. Advisory only — never writes code.

Performance advocate on the crew implementation team. Evaluates the performance implications of a proposed change — added queries, N+1 patterns, hot vs cold paths, allocation and concurrency costs. Advisory only — never writes code.

Pragmatism advocate on the crew implementation team. Pushes for the smallest, most targeted change that solves the root cause, evaluates blast radius, and pushes back on over-engineering. Advisory only — never writes code.

Product and UX advocate on the crew implementation team. Ensures a proposed change preserves expected user-facing behavior, validates it actually addresses what was reported, and flags observable/contract changes. Advisory only — never writes code.

Long-term vision advocate on the crew implementation team. Evaluates a proposed change for technical debt, future maintainability, and architectural direction — without blocking necessary fixes for speculative concerns. Advisory only — never writes code.

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.)

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.)