agents

Use this skill to rebase gh-stack branches and resolve conflicts. Replaces raw git rebase for stack workflows. Triggers: restack, rebase, rebase on main, branches out of date, resolve conflicts.

Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.

Use this skill to push a gh-stack stack and create or update stacked pull requests. Replaces git push and gh pr create for stack workflows. Triggers: push, ship it, send this up, submit, update PRs, create PR, push stack, send PRs.

Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.

Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.

Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.

Create a new branch using the repo-preferred stack tool. Use when the user asks to start work, create a branch, switch to a new task branch, or begin an issue.

Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.

Implement one bounded change from conversation context or a named vault artifact through TDD, verification, code review, and commit.

Turn settled conversation and codebase context into an implementation-ready vault spec that can be implemented directly or optionally split into tickets.

Split settled conversation or an implementation-ready artifact into independently deliverable tracer-bullet tickets when explicit work decomposition is useful.

Control local Mac apps through Computer Use for reading or operating desktop UI when a purpose-built connector, API, or CLI is not available.

Review changes since a fixed point along two independent axes: repository standards and the governing vault spec or ticket. Runs both reviews in parallel sub-agents and reports them side by side. Use for branch, PR, or work-in-progress review.

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Build and sharpen a project's vault-backed domain model. Use when the user wants to pin down domain terminology, record a durable decision, or when another skill needs to maintain project language.

Run a relentless one-question-at-a-time interview while recording resolved vocabulary and durable decisions in the project vault.

Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

Compact the current conversation into a handoff document for another agent to pick up.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Improve Rust test suites with a wide, evidence-grounded pass over placement, coverage, readability, and tooling. Use when the user asks to improve Rust tests, adopt stronger Rust testing practices, add property tests, reorganize unit/integration tests, or modernize a Rust project toward TDD guidance.

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.

Investigate a question against high-trust primary sources and capture cited findings in a vault research artifact. Use when the user wants a topic researched, documentation or API facts gathered, or reading legwork delegated.

Use when you need to resolve an in-progress git merge/rebase conflict.

Create or revise a compact durable vault brief/PRD from settled intent, optionally using visual review artifacts for UX/workflow clarity. Use after `$grill` or equivalent context when the desired behavior, scope, non-goals, acceptance model, risks, and verification strategy are ready for user review.

Run an adversarial review of local changes, branch diffs, or PRs without inventing work. Use when the user asks for review, critique, sanity check, or requested-changes prep.

Creates or revises a compact QRDSPI Design Discussion artifact that chooses the solution direction and records tradeoffs. Use when evidence and user context are sufficient to decide desired behavior, boundaries, and architectural approach.

Diagnose hard bugs or performance issues with reproduction, minimization, instrumentation, fixes, and regression tests. Use when the user asks to debug, investigate failures, or find root cause.

Challenge a plan or design with focused questions before side effects. Use when the user asks to be grilled, challenged, interrogated, or forced to clarify assumptions.

Grilling session that challenges a plan one decision at a time against the existing domain model, code reality, and durable decisions. Use when the user wants to stress-test a plan against their project's language and documented decisions while sharpening terminology and capturing resolved context inline.

Deliver one approved task through claim, TDD, verification, Plannotator review, commit, and agent-driven completion after user approval. Use when the user asks to implement a specific task or selected issue.

Find architecture-deepening refactor opportunities grounded in vault docs and code evidence. Use when the user asks to improve codebase architecture, module boundaries, cohesion, or AI navigability.

Turn an approved durable brief into a reviewed issue proposal and task records, optionally using visual review artifacts to validate task slicing. Use after `$brief` approval when implementation should be split into tracer-bullet tasks with structured bodies and clear acceptance criteria.

Publishes a tactical QRDSPI plan artifact and executable task set from settled context. Use when research/design/structure are sufficient to create vertical implementation tasks, blockers, verification, and handoff without reopening solution direction.

Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.

Grills product or engineering intent against existing docs and code, then records resolved choices for later QRDSPI work. Use when a request needs vocabulary, scope, edge cases, defaults, or user preferences clarified before research, design, structure, plan, or implementation.

Creates or revises a factual QRDSPI research artifact about current system reality: behavior, constraints, code paths, vocabulary, risks, and unknowns. Use when objective evidence is needed before design, structure, planning, or implementation.

Creates or revises a compact QRDSPI Structure Outline artifact that sketches implementation shape without task-level detail. Use when a chosen direction needs module seams, ordering, test seams, or review checkpoints clarified.

Apply test-driven development with red-green-refactor cycles for a selected behavior or regression seam. Use when implementing a task that requires TDD discipline or a bug needs a durable regression test.

Triage vault research artifacts and tasks with category and stage metadata. Use when the user asks to classify, prioritize, tag, or prepare vault work for agents or humans.

Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.