moai-docs-generation
>
moai-workflow-ddd
>
moai-workflow-jit-docs
>
moai-workflow-project
>
moai-workflow-spec
>
moai-workflow-templates
>
moai-workflow-testing
>
sdd-implement
Task implementation skill for spec-driven workflows. Reads specifications, identifies next actionable tasks, and creates detailed execution plans. Use when ready to implement a task from an existing spec - bridges the gap between planning and coding.
ds-review
REQUIRED Phase 4 of /ds workflow. Reviews methodology, data quality, and statistical validity.
ds-plan
REQUIRED Phase 2 of /ds workflow. Profiles data and creates analysis task breakdown.
dev-verify
REQUIRED Phase 7 of /dev workflow (final). Requires fresh runtime evidence before claiming completion.
ds
Orchestrates 5-phase data analysis workflow with output-first verification.
context-optimization
Guide for managing and optimizing context in Claude Code. Use when experiencing slow responses, context warnings, or planning large tasks. Covers /compact, /clear, context budgeting, subagent delegation, and efficient session workflows.
no-deferred-work
Use during all development - no TODOs, no FIXMEs, no "we'll add this later"; do it now or get explicit deferral permission
branch-discipline
Use before any code changes - hard gate ensuring work never happens on main branch, with proper feature branch creation from correct base
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
git-hex-pr-workflow
>
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
workbench-architecture
Architecture and ADR workflows for Workbench CLI. Use when documenting system design, decisions, tradeoffs, or rationale that must be tracked over time.
workbench-docs
Documentation workflows for Workbench CLI. Use when creating or updating specs, ADRs, runbooks, guides, or general docs, and when syncing backlinks or change notes.
speckit-plan-zh
执行实施规划工作流程，使用计划模板生成设计工件。触发词包括："speckit计划"。
figma-design-workflow
Generate Figma mockups from wrangler specifications with hierarchical file structure and approval tracking
creative-chronicle-log
Document creative decisions and protocol evolution in structured chronicle format.
proactive-collaborative-contribution
Contribute proactively to collaborative workflows.
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
cc-task
Implement based on an approved plan. Use after cc-plan is finalized.
Skill development
This skill should be used when the user asks to "create a skill", "write a new skill", "improve a skill description", "organize skill content", "update skill references", "update skill workflows", "review a skill", "test a skill", "add a reference", "add a workflow", "add a template", or needs guidance on skill structure, progressive disclosure, or skill development best practices.
multi-agent
Build multi-agent systems - orchestration, coordination, workflows, and distributed architectures
technical-specification
Build validated specifications from discussion documents through collaborative refinement. Third phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) User asks to create/build a specification from discussions, (2) User wants to validate and refine discussion content before planning, (3) Converting discussion documents into standalone specifications, (4) User says 'specify this' or 'create a spec' after discussions, (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that technical-planning uses to build implementation plans.
create-hooks
Expert guidance for creating, configuring, and using Claude Code hooks. Use when working with hooks, setting up event listeners, validating commands, automating workflows, adding notifications, or understanding hook types (PreToolUse, PostToolUse, Stop, SessionStart, UserPromptSubmit, etc).
plan-executor
Execute implementation plans step-by-step. Use when user says "execute the plan", "implement the plan we created", "start building based on the plan", "go ahead and implement it", "proceed with the implementation", or references a plan file and wants to begin coding.
