openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured…
Skills
Find an Agent Skill for your task. Read the guide and copy the install command.
Updated 11-14 00:15
Coding & development
40,999 results
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-to-beads
PROACTIVELY convert approved OpenSpec specs into Beads issues when user applies a change or explicitly approves implementation. Creates trackable work with…
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
drizzle-orm-best-practices
Dialect-aware Drizzle ORM conventions for safe query, mutation, and transaction boundaries. Use when writing or reviewing Drizzle schemas, queries,…
gcpr
Use only when the user explicitly invokes "/gcpr" or "$gcpr" as the short alias for "/git-commit-push-realtime" or "$git-commit-push-realtime". Delegates to…
git-commit-realtime
Use when the user wants an implementation committed continuously at meaningful checkpoints while pushing stays a separate, explicit step. Trigger on phrases…
gh-stack
Manage Cherry Studio stacked branches and pull requests with the GitHub gh-stack extension. Use for planning, creating, inspecting, rebasing, syncing, linking,…
respond-to-review
Side-route for when a teammate's review lands on your open PR and you want to decide what to fix, what to push back on, and what to defer. Each thread's claim…
pstack-architect
Use for Pstack interface or module design, caller-first sketches, and implementation against a chosen shape.
pstack-how
Use for Pstack code walkthroughs, subsystem behavior, or module placement and ownership questions.
pstack-no-comments
Use for Pstack comment review, unnecessary narration, or suppressions that conceal code problems.
pstack-principle-attack-the-premise
Apply when two or more fixes that share one premise have failed the same gate. Write the premise down and test it directly before you write another fix that…
pstack-principle-boundary-discipline
Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust…
pstack-principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is…
pstack-principle-foundational-thinking
Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data…
pstack-principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that…
pstack-principle-minimize-reader-load
Apply when reviewing or shaping code that's hard to trace. Count layers between question and answer, and hidden state in the reader's head; collapse one-caller…
pstack-principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files.
pstack-principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states…
pstack-principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
pstack-principle-separate-before-serializing-shared-state
Apply when concurrent actors might write to the same file, branch, key, or state object. Eliminate the sharing first; serialize structurally only when one…
pstack-principle-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a…