Quick Start

Once the plugin is installed, global rules apply to every Agent session. Use the orchestrator skill and specialist agents for structured work.

Full orchestration is not always the best path

Use the usage decision guide before starting /fein. Direct execution or one specialist is often better for small changes, interactive work, and expensive or slow models.

Try a workflow command

In Agent chat (IDE or CLI):

/fein Fix the flaky auth test and review the fix

That runs the full pipeline: adventurer → architect/planner → builder → reviewer.

Other modes:

Command	Behavior
/sonar <goal>	Research only - stop before implementation
/blitz <goal>	Builder-first fast path

Try a single specialist

“Use the builder agent to add a JSDoc comment to the add function in src/math.ts.”

The main agent should spawn builder via Task with a complete handoff.

Try maker/checker

“The login flow throws on empty email. Trace the bug, fix it, and review the fix.”

Expected sequence:

1. diagnose - root cause
2. builder - minimal fix
3. reviewer - validation (read-only; must not edit)

Two-layer maker/checker enforcement

Reviewer/adventurer/planner agents use readonly: true runtime flag to block write tools (Write, StrReplace, Delete) at the Cursor runtime level, with prompt-level instructions as a backup layer. Still, never ask the same agent that implemented to review its own work.

Next

• Agent reference - specialist responsibilities
• Pipeline & roles - handoff contracts and iteration limits