ask-odell
Ask which installed skill or flow fits the current situation. A router over the engineering and productivity skills installed alongside it.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ask-odell
- description
- Ask which installed skill or flow fits the current situation. A router over the engineering and productivity skills installed alongside it.
- disable-model-invocation
- true
02 资源文件 2
- 参考文档agents/openai.yaml155 B
- 参考文档PHASE-BOUNDARIES.md4.2 KB
03 SKILL.md 正文
Ask Odell
You don't remember every skill, so ask.
A flow is a path through the skills. Most paths run along one main flow, and two on-ramps merge onto it. Everything else is standalone, or a vocabulary layer that runs underneath.
The main flow: idea → ship
The route most work travels. You have an idea and want it built.
-
/grill-with-docssharpens the idea by interview. Start here whenever you are working in a repo: it's stateful, retaining what it learns inCONTEXT.mdand ADRs. (No repo? Use/grill-meinstead, covered under Standalone. Both run the samegrillingprimitive;grill-with-docsis the one that leaves a paper trail, which makes it the better of the two whenever a repo is there to leave it in.) -
Branch: can you settle every question in conversation? If a question needs a runnable answer (state, business logic, a UI you have to see), detour through a prototype, bridged by
/handoffin both directions (a prototype lives in its own directory, which is exactly what/handoffis for; see Phase boundaries):/handoffout, then open a fresh chat against that file,/prototypeto answer the question with throwaway code,/handoffback what you learned, and reference it from the original idea thread.
-
Branch: is this a multi-session build?
- Yes →
/to-spec(turn the thread into a spec), then/to-ticketsto split it into tracer-bullet tickets, each declaring its blocking edges. On a local tracker that's one file per ticket under.scratch/<feature>/issues/, worked blockers-first by hand; on a real tracker the edges become native blocking links, so any ticket whose blockers are done can be grabbed: kick off/implementper ticket, in a fresh chat for each one. Each ticket is self-contained, so the last one's context is disposable. - No →
/implementright here, in the same chat.
Either way,
/implementbuilds each issue by driving/tddinternally (one red-green slice at a time), then closes out by running/code-review, a two-axis review (Standards + Spec) of the diff, before committing. Reach for/tddon its own when you just want to build a concrete behaviour test-first without a full spec, and/code-reviewon its own whenever you want to review a branch or PR against a fixed point. For bug-hunting or security passes use Cursor's/review-bugbotand/review-securityinstead; they cover different axes. - Yes →
Context hygiene
Keep steps 1–3 in one unbroken chat (don't summarize or start over until after /to-tickets) so the grilling, spec, and tickets all build on the same thinking. Each /implement then starts fresh, working from the ticket.
The limit on this is the smart zone: the window (~150k tokens on state-of-the-art models) within which the model still reasons sharply. If a chat approaches it before /to-tickets, don't push on degraded; summarize at the nearest phase boundary and carry on (see Phase boundaries).
On-ramps
A starting situation that generates work, then merges onto the main flow.
-
Bugs and requests piling up →
/triage. It moves issues through triage roles and produces agent-ready issues, which/implementlater picks up.Triage is only for issues you didn't create: bug reports, incoming feature requests, anything that arrives raw. Tickets that
/to-ticketsproduced are already agent-ready, so don't triage them. -
Something's broken →
/diagnosing-bugs. For the hard ones: the bug that resists a first glance, the intermittent flake, the regression that crept in between two known-good states. It refuses to theorise until it has a tight feedback loop (one command that already goes red on this bug), then fixes with a regression test. Its post-mortem hands off to/improve-codebase-architecturewhen the real finding is that there's no good seam to lock the bug down. -
A huge, foggy effort: a greenfield project or a huge feature build, too big for one session →
/wayfinder, the most cognitively demanding flow here. When the way from here to the destination isn't visible yet, it charts a shared map of decision tickets on the issue tracker and resolves them one at a time, producing decisions, not deliverables, until the fog is pushed back and the way is clear. Where/grill-with-docssharpens an idea you can hold in one session, wayfinder is for the idea you can't, and it's slower and denser, so save it for exactly that, never a well-scoped feature.When the map clears, it hands off, it doesn't build: merge onto the main flow at
/to-spec, which collapses the map's linked decisions into a buildable plan, then/to-ticketsand/implementas usual. Looping the map straight into/implementskips that collapse and throws the linked detail away, so go straight to/implementonly when the effort turned out genuinely small.
Codebase health
Not feature work, just upkeep.
/improve-codebase-architectureruns whenever you have a spare moment to keep the codebase good for agents to operate in. It surfaces deepening opportunities; picking one generates an idea you can take into the main flow at/grill-with-docs. It's the survey that finds the candidates;/codebase-design(below) is the bench you design the chosen one on.
Vocabulary underneath
Two model-invoked references that run beneath the other skills, each the single source of truth for its vocabulary. Reach for them directly when the words, not the process, are the problem; or let the skills above pull them in.
/domain-modeling: sharpen the project's domain language: challenge a fuzzy term, resolve an overloaded word ("account" doing three jobs), record a hard-to-reverse decision as an ADR. It's the active discipline/grill-with-docsdrives to keepCONTEXT.mda clean glossary./codebase-designis the deep-module vocabulary (module, interface, depth, seam, adapter, leverage, locality) for designing a module's shape: a lot of behaviour behind a small interface at a clean seam./tddand/improve-codebase-architectureboth speak it.
Phase boundaries
A phase is a chunk of work inside a chat: the grilling, the implementation, the QA. At the boundary between two of them you have five options, and picking between them is the fuzziest decision in this whole map:
- Continue: stay put. Costs nothing, loses nothing.
- New chat: start from an empty window, when nothing here matters to what's next.
/handoffwrites a portable markdown file. Narrow: only for a new harness, a new directory, a colleague, or forking a side task mid-phase. What it buys is portability.- Subagent: send a tightly-scoped task to its own window (Task tool) and get a report back.
- Summarize compresses this context and carries on with the summary. The default, at the bottom of the tree rather than the first reach.
Read PHASE-BOUNDARIES.md for the ordered tree: the five questions, the reasoning behind each branch, and why the primary-source cost makes Continue the one to rule out first. Make the decision at a boundary; mid-phase, continue or split the rest into subagents.
Standalone
Off the main flow entirely.
/grill-me: the same relentless interview as/grill-with-docs, but stateless: it saves nothing locally and builds noCONTEXT.md. Reach for it when you are not working in a repo (sharpening a plan, a design, a piece of writing, anything with no repo under it). If you are in a repo, use/grill-with-docsinstead: it runs the same interview and leaves a paper trail, so it is strictly the better one./grillingis the interview primitive itself: rounds, the frontier, facts are the agent's job and decisions are yours./grill-meand/grill-with-docsare the two named ways in, and/triage,/wayfinderand/improve-codebase-architectureall run it internally. Reach for it directly only when you want the interview with no wrapper around it./prototypeis a small, throwaway program that answers one design question: does this state model feel right, or what should this UI look like. Throwaway is a constraint on how the code is written, not a promise to destroy it: the answer folds into the real code, and the prototype itself is kept as a primary source on aprototype/<name>branch out of main, pointed at from the implementation issue. It's the detour in step 2 of the main flow, but reach for it any time a design question is hard to settle on paper./research: delegate reading legwork to a background subagent: it investigates a question against primary sources (via the Ref and Exa tools), then leaves a cited Markdown file in the repo. Keep working while it reads. The file it produces is something to take into the main flow at/grill-with-docs, since research feeds the thinking rather than replacing it./to-questionnairecomes in when the thing blocking you isn't in your head or the codebase but in someone else's, and it writes them a questionnaire to fill in. It's the inverse of/grill-me: instead of interviewing you about the subject, it interviews you about the send (who it's going to, what you need back) and aims the questions at the gap. What comes back is material for/grill-with-docsor/to-spec./wizardis for the steps only a human can take: provisioning infrastructure, setting up credentials or CI secrets, clicking through an unfamiliar third-party dashboard, running a one-off migration or cutover. It generates an interactive bash script that opens each URL, captures each value, and writes it into.envand GitHub secrets, so the procedure stops being something you re-explain to an agent every time. Model-invoked, so the agent reaches for it the moment it hits a wall only you can pass. If the agent could just do it itself, it should; this is for where a human is genuinely in the loop./wait-whatis the corrective for a message that didn't land. Use it mid-conversation, inside any other skill, and the agent re-pitches what it just said with the context you were missing, in plain English, using theCONTEXT.mdvocabulary. It works after the fact;/grill-with-docsis the upfront cure, because a shared language agreed early is what stops the jargon arriving at all./teach: learn a concept over multiple sessions, using the current directory as a stateful workspace.
Not installed
Skills from the same family that were deliberately left out, and what covers them instead:
- resolving-merge-conflicts: use Cursor's
/autopilot, which resolves conflicts and asks when intents genuinely clash. - writing-for-agents: use Cursor's built-in
create-skillandcreate-ruleskills.
Precondition
/setup-odell-skills: run before your first engineering flow to configure the issue tracker, triage labels, and domain-doc layout the other skills assume. Custom issue trackers also work. For the per-role model rule, run /setup-ostack in Cursor or /setup-pstack in Codex — those belong to the stacks, not to this skill.
04 同仓库更多 Skills
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
triage
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.