conn-castle

Explicit-only. Run a named autonomous mode, repeatedly selecting, implementing, and shipping coherent work while preserving anything blocked.

Use globally installed `playwright-cli` for browser automation, UI inspection, screenshots, Playwright test debugging, or test generation. Trigger when a task needs browser interaction or test repair. Do not use for generic tests, web search, non-browser docs, or API-only work.

Explicit-only. Align a feature specification, produce a reviewed plan, complete the local work, and ship the pull request.

Explicit-only. Review a plan/task/context artifact set and report material findings.

Explicit-only. Ship one pull request, observe hosted CI and review feedback, follow PR policy, reply to every eligible comment, and request merge authorization before merging and cleaning up.

Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict.

Use Agent Dispatch MCP tools only when the user names an external dispatch target or another skill explicitly requires dispatch. Do not use it for generic subagent, second-agent, or fresh-context requests; use the built-in subagent instead.

Explicit-only. Evaluate feedback on an open pull request, implement accepted fixes, prepare replies, and return dispositions without committing, pushing, or posting.

Use `al dispatch` for focused headless second-agent work — another model, tool set, skill, or review perspective. Trigger when the user asks to run al dispatch, use a subagent or second agent, get a fresh-context review, or invoke a target agent with a skill. Do not use for ordinary shell commands, local test runs, web search, browser automation, or multi-agent orchestration.

Audit and iteratively fix uncommitted working-tree changes until a confirming review finds no remaining actionable issues. Use to stabilize in-progress diffs and report each review/fix round with severity.

Audit the existing test suite for redundancy, quality gaps, and organization: duplicate or self-confirming tests, coverage gaps metrics miss, and safe cleanup fixes. Use `prune-new-tests` instead when the target is tests added in the current uncommitted diff.

Raise coverage: find the real coverage command, select under-covered files, add behavior-focused tests, iterate to target or blocker. Use `audit-tests` for full-suite cleanup; use `prune-new-tests` to prune speculative tests in the current uncommitted diff.

Use `npx ctx7` to fetch current documentation, API references, and code examples for libraries, frameworks, and APIs when the answer is version-dependent or post-cutoff, or local sources (README, docs/, CLI help) can't answer it. Trigger for API syntax, configuration, setup, migration, or "how do I use <technology>" questions. Do not use for generic web research, local file reading, browser automation, or package installation.

Execute an existing plan/task/context artifact set: make aligned code changes and verify code, tests, docs, and memory before closeout. Use `plan-work` when no plan exists.

Write a scoped implementation plan, task list, and context file for a requested change, roadmap slice, execution strategy, task breakdown, or pre-implementation design artifact.

Use playwright-cli for real-browser UI automation, screenshots, Playwright test debugging, and interactive test generation. Trigger when a task needs browser interaction, UI inspection, end-to-end verification, or Playwright test repair. Do not use for generic test running, web search, non-browser docs, or API-only work.