The library

annotate · Teams reviewing specifications, documentation, or design rationales where structured feedback (comments, deletions, image callouts) beats inline email.

transform-roadmap · Product teams transitioning from output-focused to outcome-focused planning, especially before executive presentations or quarterly planning.

plan-ceo-review · Founders and product managers blocking time BEFORE spec writing to validate that the requested feature is actually the right product.

po · Managing product backlog and feature documentation.

ba · Solutioning Claude Code Config Manager features through multi-expert analysis and wireframe-driven design.

s · Turning vague feature ideas into testable specifications with clear acceptance criteria.

keb · Determining if a flagged rule is a real bug, deliberate pattern, or framework limitation.

ux · Comprehensive accessibility auditing against 10 usability heuristics + WCAG.

po · PM-style decomposition of vague features into executable, dependency-ordered tasks.

ux · Creating detailed, implementable UX specs for solo/junior frontend developers.

project-recap · Refreshing mental model of project state after weeks away or before planning

ultrathink · Tackling ambiguous problems where you need to question everything and design from first principles

gsd:verify-work · Ensuring quality gate before work moves to done (prevents 'done' from meaning 'not verified')

prd-maker · Feature scoping when you need to transform a vague idea into a junior-developer-ready spec through structured clarification.

import-from-chatgpt · Research workspace bootstrap when you want to convert a ChatGPT exploration into a structured Tao project.

ns-create · Project anchoring when you need an immutable baseline of success criteria that constrains all future decisions.

ui-session · Frontend teams needing rapid visual feedback loop without manual page reloads or Git complexity.

plan-sprint · Teams running time-boxed sprints on modular features where end-to-end vertical slices are critical for demo readiness.

why · Finance/product teams requiring problem validation before spec work; catches missing evidence early.

speckit.specify · Agile teams converting informal feature requests into structured specs without heavyweight process overhead.

clarify · Quick clarification before moving to planning; filters out avoidable ambiguity without heavyweight refinement meetings.

new-page · Rapid MDS prototyping page creation with automatic layout grid and component discovery.

new-feature · Standardized Bock language feature development with test-first discipline.

create · Publishing atomic knowledge notes with enforced taxonomy, proper linking, and validation before commit.

devlyn.design-system · Single-source-of-truth design system when consistency across products is required

improve-ui · Systematically redesigning components against a strict design system to prevent visual drift and generic LLM output.

pf-epic · Managing large multi-repo epics where brainstorm→plan→execution→review is the governance gate

Conductor Implement · Driving large multi-phase development projects where atomic task state, phase gating, and learning capture are critical

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.

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

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.

review-file · Evaluating if diffs actually solve stated problems

plan · Planning feature work with explicit tasks and validation gates

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

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

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

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

speckit.revisit · Handling specification management in rshade/finfocus when you need automated spec validation and requirement capture.

gsd:analyze-dependencies · Dependency analysis and planning in sandk0/fancai to prevent merge conflicts in parallel execution.

score-issues · Automating score-issues workflow in quantified-uncertainty/longterm-wiki with validation gates and structured output.

prp · Automating prp workflow in Pierry/harness-kit with validation gates and structured output.

multi-workflow · Automating multi-workflow workflow in lorenzozanee/NotchBlock with validation gates and structured output.

speckit.clarify · Handling specification management in markhazleton/RequestSpark when you need automated spec validation and requirement capture.

coltrane-resume · Automating coltrane-resume workflow in eir-dev/coltrane with validation gates and structured output.

pattern · Archiving patterns and decisions in DDD-Enterprises/dopemux-mvp for team knowledge.

capture · Documenting design tokens and decisions in lfades/postcards for future reference.