The library

restore-checkpoint · Emergency rollback of a phase when new work has taken a wrong direction

review-staged · Automated gate for Electron projects when architectural boundaries (main/preload/renderer, IPC contracts, security constraints) must be enforced before commits land.

new-page · Rapid page scaffold for marketing/landing page sites when composition rules (grid, spacing, title style) must be consistent across all pages.

breakdown · Converting high-level requirements into parallel-ready tasks when work must be distributed across AI agents or developers with full context in each task prompt.

pr-description · Pre-PR documentation when commit messages are thin and reviewers need executive summary of what changed, why, and what breaks.

module-18-gas.en · Educational context (Module 18 course) when teaching GAS automation incrementally with clasp deployment and trigger configuration.

action-preview-templates · PR workflows where human reviewers must see exactly what will post/merge before clicking 'approve', and can selectively suppress nits without re-navigating menus.

docs-create · Generating high-quality docs when project has strong template/guideline infrastructure and documentation must follow established patterns.

edn-to-lean · Formalizing proofs from symbolic logic systems into Lean when step-by-step mapping of justifications to tactics is needed.

atom-vllm-benchmark-guide · Performance A/B testing of ATOM vLLM plugin when precise, reproducible metrics across concurrency levels and throughput profiles are required.

witness · Building evidence graphs when individual claims must be corroborated with independent sources and conflicts must be discovered before synthesis.

qgis-compat · Pre-submission QGIS plugin store audit when version compatibility must be verified and all violations must be visible in a single report.

wiki-lint · Maintaining wiki coherence when contradictions and orphan pages must be discovered systematically before they compound.

create-release · Automating releases when version bumping, tag creation, and comprehensive release notes must be coordinated in single operation.

review-prp · Design review before implementation when architectural fit, edge cases, and code reuse must be vetted before work starts.

template-check-use-case · Template design audit when a use case must drive new module/role creation and composition must be validated as gracefully-optimistic.

compliance · Pre-submission compliance gate for Obsidian Community Plugin store when all violations must be caught before publication.

typings · Type-safe systems with strict indexed access guards when runtime errors from undefined array access must be eliminated at compile time.

lunar-prime · Onboarding new agents with project structure and README

review-file · Evaluating if diffs actually solve stated problems

plan · Planning feature work with explicit tasks and validation gates

command-orchestration · Automating spec-driven workflow with correct tool sequencing

jira-orchestrator:harness-review · Evaluating if diffs actually solve stated problems

audit · Detecting inconsistencies in tool counts and config across docs

template · Bootstrapping new projects with proven patterns

plan · Planning feature work with explicit tasks and validation gates

release · Publishing macOS apps with GitHub releases and package managers

commit-and-pr · Automating git workflow and PR creation

self-review · Evaluating if diffs actually solve stated problems

team · Setting up multi-agent team structure

read-specs · Onboarding to a new codebase by reading immutable truths and environment metadata before starting work

actions · Monitoring build failures and checking PR checks without opening the GitHub web UI

review-plan · Getting a staff engineer review of an implementation plan against project conventions before coding

aida-doc · Documenting the intent and design rationale of specs that were just modified or shipped

add-task · Creating a formal backlog item with vertical slice definition when you have a new feature or bug to track

arch-adr · Recording and justifying a major technical decision (framework, database, architecture) for future maintainers

iui · Quickly generating shadcn components that match this project's design system without manual tweaking

copilot-review-design · Getting a second review of a feature design before implementation to catch architectural or scope issues

lint · Periodic health check of a wiki to surface decay (orphans, broken links, stubs) without auto-fixing

n8n-branch · Tracking multiple n8n workflow versions locally and switching between branches during active development

collaborate · Asking an external AI (ChatGPT, Gemini) for help on a tricky issue by giving it full project context in one document

create-tool · Quickly adding a new client-side tool to the toolbox without manually wiring up layout, metadata, and FAQ sections

review · Verifying that coded changes match the documented implementation plan before committing

code-migrate · Planning a major framework upgrade or language migration when you need to minimize risk and document the path

release · Creating a release tag and version bump with a full audit trail and zero-trust approval gates

unison-update · Fixing type errors that appear after updating Unison definitions to use new library versions

release · Releasing a Squiggy project with automated changelog generation and zero-trust approval gates

second-opinion · Quick 30-second sanity check before implementing a medium-complexity plan (1-4 files)

tr-decompose · Breaking down a user intent into concrete taproot UseCase behaviors and documenting the decomposition

db-backup · Safely experimenting with different database providers while preserving the current proven configuration