zpyoung/quirk
Skill Claude CodeCodex
Divergent-ideation subroutine for surfacing N non-obvious viable options when facing decision points. Explicitly invoked via /adhd or delegated from brainstorming's gray-area resolution. Uses parallel agent dispatch (Diverge + Deepen) + inline Score/Cluster to generate structured option lists with critiques.
zpyoung/quirk
Skill Claude CodeCodex
Use when a work product needs adversarial review - attacking a diff, spec, plan, or written claim to find what is wrong with it. Triggers on "adversarial review", "critique this", "red team it", "attack this", "find flaws", "tear this apart", "poke holes in", or when another skill composes a review step. Runs a…
zpyoung/quirk
Skill Claude CodeCodex
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
zpyoung/quirk
Skill Claude CodeCodex
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
zpyoung/quirk
Skill Claude CodeCodex
Use to implement a multi-step task sequentially in one session when subagents aren't available — plans in context, then executes.
zpyoung/quirk
Skill Claude CodeCodex
Use when the user wants to deeply research a topic OR brainstorm/explore ideas WITHOUT building anything yet — produces a cited briefing or idea-landscape (an exploration doc), never a spec, plan, or implementation. Triggers on "do deep research on X", "research X", "let's brainstorm ideas around X", "explore X"…
zpyoung/quirk
Skill Claude CodeCodex
Use when the user wants to file, report, or write up a bug, a feature request, or a code-change request — triggers on "file a bug", "report an issue", "write up a bug report", "open an issue", "file a feature request", "raise a ticket". Runs a guided evidence-gathering session, resolves what it can by reading the…
zpyoung/quirk
Skill Claude CodeCodex
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
zpyoung/quirk
Skill Claude CodeCodex
Use when dispatching the pi coding agent for a sub-task — code review, analysis, edits, or multi-agent orchestration. Triggers on "use pi", "run pi", or "pi " (codex, terra, opus, sonnet, gemini, haiku, grok).
zpyoung/quirk
Skill Claude CodeCodex
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
zpyoung/quirk
Skill Claude CodeCodex
Use when releasing the quirk plugin - commits any pending changes, stamps a calendar-based (CalVer) version from today's date, writes the changelog, and pushes to origin autonomously. Triggers on "release quirk", "ship quirk", "bump and push quirk", or "cut a quirk release".
zpyoung/quirk
Skill Claude CodeCodex
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
zpyoung/quirk
Skill Claude CodeCodex
Use when a feature branch exceeds 400 lines of diff, when a reviewer asks to "make this PR smaller", when planning a large feature so it ships in reviewable chunks, or when the user invokes /split-branch.
zpyoung/quirk
Skill Claude CodeCodex
Use when executing implementation plans with independent tasks in the current session.
zpyoung/quirk
Skill Claude CodeCodex
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
zpyoung/quirk
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code.
zpyoung/quirk
Skill Claude CodeCodex
Use when about to write hedging language like "pre-existing", "out of scope", "future work", "skipped for brevity", or "architectural concern" — instead, route the observation to a typed artifact (BUGS.md, DEFERRED.md, TESTBACKLOG.md, proposals.md) or an ADR. Also use when the user invokes /quirk:artifacts: commands…
zpyoung/quirk
Skill Claude CodeCodex
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
zpyoung/quirk
Skill Claude CodeCodex
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions.
zpyoung/quirk
Skill Claude CodeCodex
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
zpyoung/quirk
Skill Claude CodeCodex
The planning rubric the execution skills run in-context at the start of a run — turns the tech spec (tech.md) when present, else the logic spec / requirements, into a task breakdown (contracts, acceptance, parallelism) before code.
zpyoung/quirk
Skill Claude CodeCodex
Use when writing or revising a human-facing technical document — README, guide, ADR, PR description, changelog — or when asked to tighten, shorten, or declutter one ("tighten this", "too long", "hard to scan", "make this scannable"). Separates what the reader's decision depends on from detail they do not want, cutting…
zpyoung/quirk
Skill Claude CodeCodex
Use when creating, editing, or testing a Claude Code skill — writing SKILL.md and its frontmatter/description, choosing skill vs command vs subagent vs CLAUDE.md, fixing a skill that won't trigger, or deciding how strictly to test one. Covers activation (getting a skill to fire) and execution (getting it right once…
zpyoung/quirk
Skill Claude CodeCodex
The rubric the execution skills run in-context — only when the work warrants it — to author the code-anchored tech spec from the approved logic spec, before planning.