scoped-implementation

Preload for the frontend-engineer and verification-engineer agents; drive the UI in a real browser via playwright to confirm a change actually works.

Use for live SQL Server schema discovery, table and column inspection, foreign-key paths, routine dependencies, and database impact analysis.

Preload for the implementer and complex-implementer agents; use when returning completed implementation work to the lead and reviewer.

Use proactively when a project card has clear acceptance criteria and is ready for implementation by the appropriate specialist subagent.

Preload for the codebase-consultant agent; use the code graph to find the files relevant to a question, then read only those files.

Preload for the code-reviewer agent; use to review a diff independently against its card, graph context, and project standards.

Preload for code-editing and research agents; before writing or debugging code against an unfamiliar library, framework, SDK, CLI, or cloud API, fetch current…

Use for repository discovery, symbol lookup, dependency analysis, caller analysis, bounded architecture context, and code-change impact analysis.

Preload for the codebase-consultant agent; audit the repository's documentation against the actual code and structure, and report what is stale.

Preload for the code-reviewer agent; use to prioritize review findings by severity, confidence, and affected graph surface.

Preload for the verification-engineer agent; run the actual application and observe its behavior to confirm a change works, beyond what the test suite covers.

Preload for the research-planner agent; use to investigate unfamiliar architecture, libraries, alternatives, or unresolved requirements before coding.