ask-me

Ask Me

Choose the smallest workflow that fits the situation.

A workflow is a path through the skills. Most coding-agent work starts with understanding, then moves through planning, implementation, and review. Bug work starts with diagnosis before planning.

Main Flow: Change Code

Use this route when the user wants to add, modify, or remove behavior.

1. /plan-it — understand the goal, inspect the relevant code, identify affected modules, choose an approach, and define validation.
2. /implement-plan — make the agreed changes in small steps, run the appropriate checks, and keep fixing until the validation passes or a real blocker is found.
3. /review-change — use an independent review when requested or when the diff's risk warrants it.

For a clear, low-risk implementation request, use a brief inline plan and proceed without an extra approval round. Use the full planning workflow when scope, design, or risk needs a decision. Load inquiry or review skills only when they add evidence the task needs.

Bug Flow: Symptom → Diagnosis → Fix

Use this route when behavior or an error contradicts expectations and the cause is not verified: a report of broken, slow, or surprising behavior, a pasted error or log, a "why does this happen" question, or a fix that did not work.

1. /diagnose-bug — restate the symptom, decide whether it is a defect, intended design, or environment, reproduce it, and confirm the cause before any fix.
2. /plan-it — plan the fix once the cause and validation path are clear.
3. /implement-plan — implement the fix and run the validation loop.
4. /review-change — review from fresh context when requested or warranted by the fix's risk.

Establish the cause before editing. If the user requested a fix and the cause, scope, and validation are clear, continue through a brief plan and implementation without asking again. Stop after diagnosis when diagnosis alone was requested.

Review Flow

Use /review-change when the work is done, there is a diff to inspect, or the user asks for review.

Prefer reviewing against a fixed point such as main, a branch, a commit, or a supplied diff.

Context Hygiene

Keep planning and implementation connected while the plan is still active. When reviewing, prefer a fresh context or subagent so the reviewer is not anchored by the implementer's reasoning.

If work must continue later, provide a short conversational handoff with goal, current state, validation, and remaining risks. Persist a handoff file only with the user's approval.