crew

Plugin crew from marketplace alfreds-plugins in zienag/alfreds-plugins. Commands read from the repo's manifest — 10 days ago.

Skills (1)

• orchestrator

  Orchestrator / tech-lead mode: run the session through the crew subagents, keeping own context for judgment and integration. crew:solid is the default worker; crew:fast when the brief has made every decision, crew:deep when being wrong is expensive; crew:teamlead for a whole slice. Invoke on "orches

Subagents (4)

• deep

  For work where being wrong is expensive: a design decision, a bug with no known cause, a review meant to find what is broken. Everything else is crew:solid.

• fast

  For work where the brief has made every decision and the agent only carries it out: a given route through code, a command, a browser, computer-use or iPhone screen errand by recipe. It stops and reports when what it finds departs from the brief.

• solid

  The default worker. It chooses the route itself; a wrong choice is cheap to catch, and it stops and reports when the task turns out to hold a design decision or a subtle correctness issue.

• teamlead

  A sub-orchestrator: hand it a whole slice, not a single task. It does hands-on work — edits, builds, runs tests — but pushes context-heavy lookups down: broad code search to Explore, routes you can spell out to crew:fast, hard isolated pieces to crew:deep. It decomposes, verifies, and integrates, ho