context-optimization
[Utilities] Use when managing context window usage, compressing long sessions, or optimizing token usage.
checkpoint
[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).
compact
[Utilities] Use when you need to compress context to optimize token usage (user-facing alias for context-optimization Strategy #3 Compress).
commit
[Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot.
workflow-spec-to-pbi
[Workflow] Use when activating the Spec to PBI Backlog workflow to convert canonical tech-free Feature Specs into complete, prioritized, dependency-aware PBIs and stories.
template-skill
[Category] Use when defining the standard skill description pattern.
architecture-design
[Architecture] Use when designing solution architecture across backend, frontend, deployment, monitoring, testing, and code quality.
workflow-visualize
[Workflow] Use when activating the Visual Diagram workflow for create visual excalidraw diagrams from codebase investigation or web research.
workflow-write-integration-test
[Workflow] Use when activating the Write Integration Tests workflow for spec-first integration test authoring. Also covers converting existing test specs into integration test code and verifying integration test stability (repeat-run verification).
business-evaluation
[Content] Use when you need to evaluate business idea viability: Business Model Canvas, financial projections, risk matrix, go-to-market, execution plan.
changelog
[Documentation] Use when you need to generate or update changelog entries.
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}.
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.
llm-council
[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.
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.
prioritize
[Project Management] Use when you need to prioritize backlog items using RICE, MoSCoW, or Value-Effort frameworks.
pbi-challenge
[Code Quality] Use when you need an AI-assisted Dev BA PIC review of PBI drafts.
markdown-novel-viewer
[Content] Use when you need background HTTP server rendering markdown files with calm, book-like reading experience.
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.
pbi-mockup
[Project Management] Use when you need to generate an HTML mockup report from PBI and story artifacts.
production-readiness-review
[Code Quality] Use when reviewing service-layer and API changes for production readiness.
claude-md-init
[Documentation] Use when you need initialize, update, or refactor CLAUDE markdown from project-config JSON and codebase scan results.
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.
project-config
[Utilities] Use when you need to scan workspace and update docs/project-config JSON to match current project structure.
workflow-feature-spec
[Workflow] Use when activating the Business Feature Documentation workflow for 8-section tech-free feature docs.
workflow-feature
[Workflow] Use when activating the Feature Implementation workflow for implement a well-defined feature with investigation, planning, implementation, and review. Also covers TDD/test-first development and spec-driven feature implementation with test specs written before code.
workflow-idea-to-pbi
[Workflow] Use when activating the Idea to PBI workflow for turning an idea — or a raw product vision/problem — into prioritized PBIs and stories (single-PBI deep mode, or multi-opportunity discovery mode).
workflow-greenfield-init
[Workflow] Use when activating the Greenfield Project Init workflow for full waterfall project inception from idea through implementation with integration testing.
workflow-idea-to-spec
[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.
workflow-refactor
[Workflow] Use when activating the Code Refactoring workflow for restructure and improve existing code without changing behavior.
workflow-research
[Workflow] Use when activating the Research & Synthesis workflow — research a topic via web sources, then synthesize per --output={synthesis|business-eval|marketing|course} (knowledge report, business evaluation, marketing strategy, or course material).
workflow-review-changes
[Workflow] Use when activating the Review Current Changes workflow for review, fix, and re-review recursively until all issues resolved.
review-architecture
[Code Quality] Use when reviewing architecture compliance for layers, messaging, service boundaries, CQRS, repos, and entity events.
knowledge-review
[Research] Use when you need to review knowledge artifacts for completeness, citation quality, confidence accuracy, and template compliance.
remotion
[User-Invoked] Use when you need create, update, or preview Remotion videos.
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).
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.
knowledge-synthesis
[Research] Use when you need to synthesize research findings into structured report using template.
market-analysis
[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.
quality-gate
[Code Quality] Use when you need to run quality gate checklist.
quality-gate-review
[Project Management] Use when you need to enforce quality gates, verify compliance with standards, track quality metrics, and generate audit trails.
prove-fix
[Code Quality] Use when you need to prove fix correctness with code proof traces, confidence scoring, and stack-trace-style evidence chains.
workflow-seed-test-data
[Workflow] Use when activating the Seed Test Data workflow for idempotent QC happy-path seeders.
workflow-spec-sync
[Workflow] Use when activating the Test Spec Update (Post-Change) workflow for update test specs and feature docs after code changes, bug fixes, or pr reviews.
spec
[Documentation] Use to author, audit, amend, or test-spec a business Feature Spec. The single spec skill — modes draft|init|update|audit|amend create/maintain the tech-free 8-section Feature Spec; draft authors a provisional spec from an idea/requirement (no code yet, Evidence: TBD); tests generates Section 8 TC-{FEATURE}-{NNN} test specifications; sync reconciles §8 TCs ↔ integration test code. Per-mode procedure lives in references/{author,tests,sync}.md.
dependency
[Project Management] Use when you need to map and visualize feature dependencies between modules, services, and work items.
design-spec
[Project Management] Use when you need to create UI/UX design specifications from requirements, PBIs, or user stories. Use --mode=wireframe to convert hand-drawn/digital wireframes or UI sketches into structured specs.
design
[Design] Create or describe a UI design — quick (fast), immersive (good), or recreated/described from a screenshot or video. Dispatch via --mode={fast|good|describe|screenshot|video} (default fast).
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.
Page 1151 of 1635 · 81738 results
