marketplace

Use for an actual ready, non-draft GitLab merge request review, re-review, or approval decision when current discussions, diff, CI, scope, findings, and approval state must be checked. Do not trigger for casual MR discussion, draft/WIP work, GitHub PRs, or local code review.

Use at conversation start, after context recovery, and for non-trivial engineering work to select exactly one primary workflow path plus one task-wide assurance and verification budget. Loading this router does not create artifacts, launch agents, or activate every workflow module.

Use only when creating, resuming, inspecting, updating, completing, or writing artifacts for an authorized .workflow plan or audit run through the bundled Workflow MCP tools. It is an operations contract, not a reason to create workflow artifacts.

Use when an authorized, sufficiently clear change needs a durable decision-complete plan under .workflow because execution is multi-step, risky, resumable, or explicitly requested. Do not create a plan for fast local work or read-only discussion.

Use at conversation start, after compaction or context recovery, and before Agent Memory reads or writes to decide whether durable global or project knowledge can materially change the task. Keep startup reads focused, and do not mutate memory during read-only or no-edits work unless the user explicitly asks to remember something.

Use after intent routing only when unresolved requirements, product intent, architecture, constraints, or tradeoffs can materially change scope, risk, acceptance criteria, or user-visible behavior. Inspect discoverable facts first and avoid exhaustive questioning.

Use to execute an approved active .workflow plan with milestone state updates, scoped task ownership, compaction recovery, selective worktree delegation, and one integration path. Do not use for direct fast-path work without a durable plan.

Use for standard or assurance completion, explicit independent review, risky handoff, or finalization of an active plan. Run one profile-appropriate verification/review path and stop at the completion latch. Fast work completes directly without this skill unless review is explicitly requested.

Use as a brief local routing step before non-trivial planning, execution, review, refactoring, debugging, or design when a shallow reading could change scope, risk, or user-visible behavior. Keep it silent when intent is clear; it does not imply an artifact or subagent.

Use for an explicit project, subsystem, diff, plan, quality, risk, security, architecture, maintainability, or readiness audit. Default to a quick local chat-only audit unless durable artifacts, several independent risk domains, or deep/exhaustive coverage are explicitly needed. The audit is read-only and does not imply fixes.

Use as a supporting skill for substantial production UI intended to ship when hierarchy, interaction, responsive behavior, accessibility, or visible states need an explicit build/review contract. Do not trigger for tiny copy/style changes, invisible frontend plumbing, or bounded mockups and throwaway prototypes.