crew-ops

name

crew-ops

description

This skill should be used when coordinating multiple fakoli-crew agents on a single project — assembling crews, planning waves, assigning file ownership, or routing work across guido, critic, warden, scout, smith, welder, herald, keeper, and sentinel. Provides wave patterns, file-ownership rules, status-file protocol, and language-style references shared across the crew. Trigger phrases: "assemble a crew", "who owns this file", "plan the waves", "run the crew on X", "coordinate agents to Y", "which agent should handle", "multi-agent orchestration". Each agent writes its status to the path the orchestrator provides; the default scratch root is `.fakoli/runs/<run-id>/`.

Crew Operations

To orchestrate multi-agent work, assign one owner per file, route work through the wave pattern below, and have each agent write status to the path the orchestrator provides in the dispatch prompt. The default scratch root is .fakoli/runs/<run-id>/; the orchestrator supplies the absolute path so agents remain path-agnostic.

Available Agents

See skills/crew-ops/references/agent-roster.md for the full 9-agent roster with roles, colors, and file paths.

Pre-Built Crews

• Code quality: guido + critic + sentinel
• Plugin development: smith + guido + sentinel + herald
• Research & build: scout + guido + welder (critic as gate)
• Full overhaul: all 9 in waves

Companion Command

/crew — list all 9 agents and suggest crew compositions for a given task.

Related Skill

debugging — systematic 4-phase root cause analysis (see skills/debugging/SKILL.md).

Wave Pattern

See skills/crew-ops/references/wave-patterns.md for the full multi-wave protocol, including timing, hand-off rules, and gate criteria.

1. Research: scout gathers information
2. Build (parallel): guido + smith + herald create new artifacts
   • ── CRITIC GATE ── critic reviews all modified files (non-negotiable)
3. Integrate: welder wires it together
   • ── CRITIC GATE ── critic reviews the integration
4. Final Verification: sentinel produces evidence-based scorecard
5. Infrastructure + Judge: keeper syncs infra, orchestrator reviews findings

Critic is a standing gate, not a wave agent. It fires after every wave that writes code.

Compressed 3-Wave Pattern (for smaller tasks)

For tasks with 1-5 file changes, collapse to 3 waves:

1. Build (parallel): appropriate agents create/modify
2. ── CRITIC GATE ── critic reviews
3. Verify: sentinel validates

Use the full 5-wave pattern when >5 files change or multiple concerns overlap.

File Ownership

Each agent owns specific files. No two agents modify the same file. If overlap is needed, one agent is primary and the other coordinates via status files. See skills/crew-ops/references/file-ownership.md for the full per-agent ownership matrix.

Communication

Agents write status to the path the orchestrator provides in the dispatch prompt (default scratch root: .fakoli/runs/<run-id>/):

• Status: IN_PROGRESS | COMPLETE | NEEDS_REVIEW
• Decisions: key choices other agents need to know
• Files Modified: list of changed files

See skills/crew-ops/references/communication.md for the full status-file protocol and inter-agent hand-off format.

Language Style References

Shared across guido and welder when working in TypeScript, Python, or Rust:

• skills/crew-ops/references/guido-style.md — TypeScript design conventions
• skills/crew-ops/references/python-style.md — Python design conventions (PEP 8/20/544)
• skills/crew-ops/references/rust-style.md — Rust design conventions (API Guidelines)
• skills/crew-ops/references/welder-patterns.md — integration patterns (re-exports, facades, adapters, shims) across all three languages