krivulcik/yolobox
Skill Claude CodeCodex
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
krivulcik/yolobox
Skill Claude CodeCodex
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
krivulcik/yolobox
Skill Claude CodeCodex
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
krivulcik/yolobox
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design.
krivulcik/yolobox
Skill Claude CodeCodex
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
krivulcik/yolobox
Skill Claude CodeCodex
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
krivulcik/yolobox
Skill Claude CodeCodex
Implement a piece of work based on a spec or set of tickets.
krivulcik/yolobox
Skill Claude CodeCodex
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
krivulcik/yolobox
Skill Claude CodeCodex
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
krivulcik/yolobox
Skill Claude CodeCodex
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
krivulcik/yolobox
Skill Claude CodeCodex
Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
krivulcik/yolobox
Skill Claude CodeCodex
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
krivulcik/yolobox
Skill Claude CodeCodex
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.
krivulcik/yolobox
Skill Claude CodeCodex
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.
krivulcik/yolobox
Skill Claude CodeCodex
Stop. That last message did not land — re-pitch it.
krivulcik/yolobox
Skill Claude CodeCodex
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.