vac-optimizer/.agents/skills/ask-matt/SKILL.md

name, description

name	description
ask-matt	Recommend the repository skill or workflow that best fits the user's situation.

Ask Matt

Recommend the shortest useful route for the requested outcome. These are options, not a required pipeline. Reuse known decisions and existing configuration; do not start work, an interview, or publication merely because you recommended a skill.

Choose a route

• A clear spec ready to build: /implement. For explicitly test-first work, /tdd; for a review only, /code-review.
• An idea with consequential open questions: /grill-with-docs for repo work, or /grill-me for a standalone discussion. Skip interviews whose answers are already known.
• A design question that needs a runnable example: /prototype. Return to the original discussion with the verdict; production implementation is a separate choice.
• A large plan needing durable acceptance criteria: /to-spec, then /to-tickets if decomposition helps. Drafting, filing, and implementing remain distinct requested outcomes.
• A genuinely uncertain multi-session effort: /wayfinder for decision tickets. A well-scoped feature does not need a planning map.
• A reported failure: /diagnosing-bugs for evidence and cause, plus repair only when requested.
• Incoming reports to classify: /triage. An explicitly chosen issue can be reviewed regardless of who created it.

Focused alternatives

Use /domain-modeling for project terminology or ADRs, /codebase-design for module shape, and /improve-codebase-architecture for a requested architecture survey. /research gathers primary-source evidence; /teach explains or practices a topic; /writing-great-skills helps maintain skills.

Use /handoff when a fresh session or durable summary is useful. Do not mandate context resets, prevent normal compaction, or assume a universal token threshold.

Read existing docs/agents/ configuration when a workflow needs it. Recommend /setup-matt-pocock-skills only for missing or explicitly changed configuration, not before every engineering task.

Explain the recommended route briefly, including any prerequisite that actually matters. Honor the user's selected skill even when another route would also work.