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)

[ Developer Intent / Request ]
                │
                ▼
┌────────────────────────────────────────────────────────┐
│ 1. Intent Classification & Catalog Lookup               │
│    (Match job against `references/catalog.md`)          │
└──────────────────────────┬─────────────────────────────┘
                           │
    ┌──────────────────────┼──────────────────────┐
    ▼                      ▼                      ▼
[ Discovery & Plan ]   [ Code & Architecture ]   [ AI, ML & Automation ]
- `grill-with-docs`    - `implement`             - `ai-engineering`
- `to-spec`            - `code-review`           - `ai-data-remediation`
- `to-tickets`         - `diagnosing-bugs`       - `ml-best-practices`
- `wayfinder`          - `domain-modeling`       - `j-space`
- `prototype`          - `setup-ts-deep-modules` - `goal`
                           │
                           ▼
┌────────────────────────────────────────────────────────┐
│ 2. Lifecycle Route Execution                           │
│    (State route briefly, invoke primary skill)         │
└────────────────────────────────────────────────────────┘

Step-by-Step Procedure (TWI)

Step 1: Ingest Request and Consult Catalog

• Action: Read references/catalog.md and classify the user's underlying intent, not just raw keywords.
• Key Point: Check whether repository setup is complete (docs/agents/issue-tracker.md).
• Why: Accurate intent classification ensures the agent doesn't jump into code when requirements are undefined.

Step 2: Formulate the Narrowest Route

• Action: Select the single primary specialist skill and state the multi-phase roadmap in 1–2 lines.
• Inline Checklist:
  • Target skill verified in references/catalog.md
  • Zero overlapping meta-skills invoked
  • Distinct lifecycle phases separated cleanly

Step 3: Execute Primary Phase

• Action: Invoke the selected skill instructions and proceed directly to execution.
• Why: Direct transition eliminates conversational overhead.

Anti-Rationalization Guardrails