القائمة
Ask which skill or flow fits the current situation — a router over the skills in this collection. Use when the user isn't sure where to start or which skill applies.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reviews a change since a fixed point on two independent axes: documented repository standards and the originating ticket or spec. Use before committing or merging a ticket, when reviewing a branch or PR, or when asked to review since a base ref.
Provide a shared vocabulary and practical rules for designing deep modules, choosing seams, improving interfaces, and making code easier to test and navigate. Use when designing or restructuring a module, evaluating abstraction depth, or when another skill needs consistent architecture language.
Diagnose hard bugs and performance regressions with a disciplined evidence loop. Use when the user says "diagnose" or "debug this", or reports something broken, throwing, failing, flaky, or slow.
A relentless interview — small batches of related questions — that stress-tests a plan or design before anything gets built, leaving a paper trail of resolved terms (CONTEXT.md) and decisions (ADRs) as it goes. Use when the user wants to pressure-test an idea, sharpen a plan, or says "grill me".
The handoff skill captures the current session in a concise file so a fresh agent can continue without replaying the conversation. Use it when pausing work, switching sessions, or pairing with `/prototype` or `/kodmap`.
Builds one well-defined ticket from its acceptance criteria through tests, review, commit, and ticket closure. Use when the user invokes `/implement` for a GitHub Issue or local markdown ticket that is ready to build.
| name | ask-kod |
| description | Ask which skill or flow fits the current situation — a router over the skills in this collection. Use when the user isn't sure where to start or which skill applies. |
| disable-model-invocation | true |
You don't have to remember every skill — ask, and get routed to the right one. A flow is a path through the skills. Most work travels one main flow; a few on-ramps merge onto it, and the rest are standalone tools or vocabulary running underneath.
You have an idea and want it built.
/grill — sharpen the idea by relentless interview. In a codebase it
leaves a paper trail (CONTEXT.md glossary + ADRs); with no codebase it
still works, just stateless./handoff out, open a fresh session, /prototype the answer,
/handoff back./spec (turn the thread into a build-ready spec), then
/tickets (split into tracer-bullet tickets with blocking edges). Then
run /implement per ticket, one ticket per fresh context, working
the frontier — tickets whose blockers are closed./implement right here./ship — the landing gate when the work is done: full gate suite,
branches merged in order, pushed, git state verified. Nothing is "done"
until /ship says so./implement drives /tdd internally — one red-green slice at a time — and
closes each ticket with /code-review before committing. Reach for /tdd
alone to build one behavior test-first, and /code-review alone to review
any branch or PR against a fixed point.
Context hygiene: keep grill → spec → tickets in one unbroken context
window so they build on the same thinking. Each /implement starts fresh
from the ticket. When a session degrades before the tickets exist, /handoff
and continue in a new thread — don't push on foggy.
/debug. For the bug that resists a first
glance: it builds a tight feedback loop before theorizing, then fixes with
a regression test. When the post-mortem shows there was no good seam to
lock the bug down, that finding feeds /unslop./kodmap. It charts a shared map of decision tickets on the issue
tracker and resolves them one at a time until the way is clear, then
merges onto the main flow at /spec (or straight to /implement if the
effort shrank)./merge-conflicts. Recovers both sides' intent
before resolving./unslop — run in a spare moment to audit for AI slop and
architectural drift. It surveys and ranks cleanup candidates; picking one
generates an idea you take into the main flow at /grill./codebase-design — the vocabulary bench underneath: deep modules,
seams, interfaces, design-it-twice. /tdd and /unslop both speak it.
Reach for it directly when the words are the problem, not the process./research — clarify-first parallel research (codebase, docs, web)
before planning. Its findings feed /grill — research sharpens thinking,
it doesn't replace it./handoff — compact the session into a file and continue in a fresh
one. Forks the context. Your CLI's /compact continues in place with a
summary — use it between phases; use /handoff when you want a genuinely
fresh session with the context preserved.When the user describes a situation, name the one skill (or short chain) that fits, say why in a sentence, and start it if they agree. Don't recite this whole map back at them.