agents

Plugin agents from marketplace forge-studio in ArtMin96/forge-studio. Commands read from the repo's manifest — 1 month ago.

Skills (5)

• contract

  Use whenever a generator agent or implementation step is about to begin work from a plan file — re-read the sprint contract verbatim and confirm the success criteria before writing any code. Prevents context decay by forcing a fresh Read of the criteria from disk rather than trusting earlier-in-sess

• dispatch

  Use when the user describes a multi-step feature or refactor and you need to decide whether to handle it solo, dispatch a parallel `/fan-out`, or run a `/worktree-team` planner→generator→reviewer pipeline. Outputs a routing recommendation with the reasoning behind it.

• fan-out

  Use whenever the user asks to apply the same operation to many independent files or components — bulk migration, batch refactor across controllers, parallel exploration of unrelated subsystems. Dispatches one subagent per file with a shared prompt template, then collects the results.

• lean-agents

  Use when subagent dispatches feel expensive — token budget tight, per-turn cost ballooning in multi-agent workflows, or when planning a `/fan-out` over many files. Recommends a 4-layer isolation profile (CLAUDE_CODE_SIMPLE, narrowed `allowed-tools`, capped `maxTurns`, picked `model`) that drops suba

• worktree-team

  Use when two or more streams of work must not interleave edits — concurrent feature branches, long-running research alongside implementation, or any time `/fan-out` would race because items share mutable state. Bootstraps N (max 5) parallel agents each in an isolated git worktree with a role-scoped

Subagents (4)

• generator

  Implementation agent that writes code from an approved plan. Use proactively after a planner has produced a plan and code needs to be written, or when executing a Pipeline (Planner → Generator → Reviewer). Full read-write access; follows existing patterns and conventions.

• planner

  Exploration + plan-authoring agent. Analyzes the codebase, proposes an implementation approach, and writes the resulting plan to `.claude/plans/s<N>-<slug>.md` in canonical format. Write/Edit scope is restricted to `.claude/plans/` by convention — source files are off-limits during planning.

• researcher

  Deep research and information-gathering specialist. Use proactively whenever the user asks to research, investigate, understand, explore, trace, or find something in the codebase ("where is X", "how does X work", "what calls X", "map the dependencies of X"), and before planning a non-trivial change

• reviewer

  Read-only critic agent that reviews implementation for bugs, edge cases, and convention violations. Use proactively after any generator-produced change, before merging a branch, or when high-risk code needs a skeptical second pass. Cannot modify code — separation ensures honest evaluation.

Hooks (4)

• SubagentStart

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/contract-reread.sh

• SubagentStop

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/contract-check.sh

• SubagentStop

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/output-schema-check.sh

• PreToolUse

  bash ${CLAUDE_PLUGIN_ROOT}/hooks/directory-ownership.sh

Similar plugins