problem-solving
[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.
pr
[Git] Use when you need to create pull request with standard format.
plan
[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
plan-validate
[Planning] Use when you need to validate a plan with critical questions interview.
plan-review
[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.
plan-analysis
[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
pdf-to-markdown
[Document Processing] Use when you need to convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR).
package-upgrade
[Code Quality] Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates.
memory-management
[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.
markdown-to-pdf
[Document Processing] Use when you need to convert markdown files to PDF with syntax highlighting and custom CSS support.
markdown-to-docx
[Document Processing] Use when you need to convert markdown files to Microsoft Word ( DOCX) format with GFM support and math rendering.
lint
[Code Quality] Use when you need to run linters and fix issues for backend or frontend.
learn
[Utilities] Use when you need to teach Claude lessons that persist across sessions.
llm-council
[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.
linter-setup
[Quality] Use when you need to research and configure code quality tooling for any tech stack — linters, formatters, static analysis, pre-commit hooks, and CI gates.
knowledge-synthesis
[Research] Use when you need to synthesize research findings into structured report using template.
knowledge-review
[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.
project-config
[Utilities] Use when you need to scan workspace and update docs/project-config JSON to match current project structure.
production-readiness-review
[Code Quality] Use when reviewing service-layer and API changes for production readiness.
prioritize
[Project Management] Use when you need to prioritize backlog items using RICE, MoSCoW, or Value-Effort frameworks.
review-artifact
[Code Quality] Use when you need to review artifact quality (PBI, user story, test spec, design spec) before handoff. Supports --type={pbi|story|spec-tests|design}.
review-architecture
[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, and entity events.
remotion
[User-Invoked] Use when you need create, update, or preview Remotion videos.
release-doc
[Documentation] Use when you need to generate a detailed, AI-analyzed release document from git history over a time range or custom prompt.
refine
[Project Management] Use when converting ideas to PBIs, validating problem hypotheses, adding acceptance criteria, or refining requirements.
prompt-enhance
[Skill Management] Use when enhancing, compressing, or expanding prompts, docs, or skills with attention anchoring [INTELLIGENT ROUTING]. Flag: --op={compress|expand|enhance} (default enhance); --op=compress strips token bloat, --op=expand reconstructs compressed text.
prove-fix
[Code Quality] Use when you need to prove fix correctness with code proof traces, confidence scoring, and stack-trace-style evidence chains.
quality-gate
[Code Quality] Use when you need to run quality gate checklist.
markdown-novel-viewer
[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.
plan-execute
[Implementation] Use when you need to start coding & testing an existing plan. Flags: --approval=off (auto/trust mode, no approval gate), --tests=off (skip the test step), --parallel (parallel phase execution via subagents).
performance-review
[Debugging] Use when analyzing or optimizing performance bottlenecks: database queries, N+1 fan-out, indexing, API latency, memory, concurrency, algorithmic complexity (O(n²)), frontend rendering, caching, and distributed paths.
pbi-mockup
[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.
pbi-challenge
[Code Quality] Use when you need an AI-assisted Dev BA PIC review of PBI drafts.
market-analysis
[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.
project-init
[Utilities] Use when initializing or re-evaluating portable project context: project-config, project-reference docs, CLAUDE.md, AGENTS.md, universal agent rules, hookless setup. Triggers on: project init, init project, missing project-config, missing project docs, missing CLAUDE.md, missing AGENTS.md.
quality-gate-review
[Project Management] Use when you need to enforce quality gates, verify compliance with standards, track quality metrics, and generate audit trails.
spec-clarify
[Code Quality] Use to validate a spec artifact's decisions with the user across three contexts — a freshly-authored Feature Spec (idea-to-spec), an existing canonical spec before PBI decomposition (spec-to-pbi), or a refined idea + §8 test-specs (idea-to-pbi deep mode). Detects the context, walks every applicable validation category, and runs an exhaustive but budget-bounded blocking clarification gate so every non-obvious or conflicting decision is confirmed before the artifact drives downstream work.
integration-test
[Testing] Use when you need to generate or review integration tests.
integration-test-verify
[Testing] Use when you need to verify integration tests pass after writing and reviewing them.
integration-test-review
[Code Quality] Use when you need to review integration tests for assertion quality, bug protection, repeatability, and test-spec traceability — AND verify the review target (changed production code) has test coverage (integration-first) with spec↔test↔code alignment.
idea
[Project Management] Use when capturing new ideas, feature requests, or concepts for future refinement.
journal
[Utilities] Use when recording an engineering journal entry — capture decisions, blockers, lessons, or progress notes during work.
harness-setup
[Quality] Use when setting up an agent quality harness with feedforward guides and feedback sensors.
greenfield
[Planning] Use when you need to start a new project from scratch with full waterfall inception — idea, research, domain modeling, tech stack, and implementation plan.
graph-trace
[Code Intelligence] Use when investigating what happens when code executes, understanding blast radius, or tracing frontend-to-backend flows.
graph-query
[Code Intelligence] Use when you need to query code relationships and connections using the structural knowledge graph.
graph-export
[Code Intelligence] Use when you need to export the code review knowledge graph. Flag: --format={json|mermaid} (default json); --format=json dumps the full graph to a JSON file, --format=mermaid renders a single file as a Mermaid flowchart diagram.
graph-connect-api
[Code Intelligence] Use when you need to detect frontend-to-backend API connections using the knowledge graph.
graph-build
[Code Intelligence] Use when you need to build, update, or sync the code review knowledge graph. Flag: --scope={full|update|sync} (default auto-detect); --scope=full forces a full rebuild, --scope=update re-parses uncommitted working-tree changes, --scope=sync syncs committed git changes then updates the working tree.
graph-blast-radius
[Code Intelligence] Use when you need to analyze the blast radius of current code changes using the structural knowledge graph.
Page 1205 of 1717 · 85837 results
