Engineering Workflow Guide

Centrally analyze tasks, classify developer intent, and route engineering workflows to the narrowest, highest-leverage specialist skill across the curated skill catalog.

Core Invariants

1. Narrowest Effective Skill: Select the most specific skill that fully covers the task; avoid invoking broad, ceremonial meta-skills when a focused tool exists.
2. One Primary Skill per Phase: Designate exactly one primary specialist skill for the current turn; chain secondary skills only across distinct lifecycle gates (e.g. Planning $\rightarrow$ Implementation $\rightarrow$ Review).
3. No Unpackaged Ghost Skills: Every routed skill must exist verbatim in references/catalog.md and have an established SKILL.md.
4. Fast-Path User Overrides: If the user explicitly requests a valid skill by name, honor it immediately without redundant routing deliberation.
5. Setup Pre-Requisite Check: If repository issue tracking, triage labels, or domain docs are unconfigured, run setup-engineering-workflows prior to planning or triage.

Architecture & Map of Content (MOC)