Ask User

Route the user's situation to the smallest suitable workflow. Explain the recommendation briefly, then ask whether they want to invoke it. Do not invoke another user-invoked skill without confirmation.

Before stating what a skill does or recommending a step be skipped, read that skill's SKILL.md: the summaries here are for orientation only.

Main Flow

For an idea that needs to ship:

1. Use /grill-with-docs to sharpen an idea in a codebase while updating GLOSSARY.md and ADRs. Use /grill-me when there is no codebase or durable project documentation is not wanted.
2. If a design question needs a runnable answer, use /handoff to branch into a fresh /prototype session, then /handoff the findings back.
3. For work that fits one session, use /implement directly. For multi-session work, use /to-spec, then /to-tickets, and start a fresh /implement session for each unblocked ticket. Use /implement-spec instead when the whole ticket graph should run in parallel worktrees and land on one integration branch.

/implement drives /tdd at agreed seams and closes with /code-review. Use /tdd or /code-review directly when only that focused workflow is needed. Before creating, updating, or marking a PR ready, /engineering-pr-review runs the gate on top of that (botica lint, /code-review, the checks of the diff) and reports what it ran. /test-smell-review applies whenever tests are written or edited; reach for it directly to audit an existing suite for tests that pass without protecting anything.

Keep grilling, specification, and ticketing in one context window when practical, so each step builds on the same thinking. Between independently implementable tickets, clear context; see Phase Boundaries.

On-Ramps