implement
Execute an implementation plan task-by-task with TDD and continuous quality checks. Use when asked to "implement the plan", "execute the tasks", "start building from the plan", or after /arc:detail has created an implementation plan ready for execution.
brainstorming
Diagnose and fix convergent ideation. Use when brainstorming produces the same ideas every time, when all ideas cluster around one approach, or when you need to escape domain defaults.
plan-with-tdd-and-prd
Use when initiating new features, complex code changes, or technical research tasks that require structured planning and documentation before implementation.
project-session-management
Manages session state and context handoffs for multi-session projects using the Session Handoff Protocol. Creates and maintains SESSION.md to track phase progress, git checkpoints, and next actions across context clears. Integrates with project-planning skill to convert IMPLEMENTATION_PHASES.md into trackable session state. Use when starting new projects after planning, resuming work after context clear, or managing complex multi-phase implementations. Keywords: session management, SESSION.md, session handoff protocol, context handoff, multi-session projects, phase tracking, git checkpoints, session state tracking, resume work, context clear, phase progress tracking, implementation phases, verification stage, debugging stage, next action tracking, work continuity, session recovery, context management, phased implementation tracking
requirement-validator
Analyze task descriptions and requirements for completeness, clarity, and implementability. Use when evaluating if a task has sufficient detail to begin implementation or if clarification is needed.
plan-status
Display the execution status of a plan by parsing frontmatter metadata. Shows progress at-a-glance without requiring manual inspection of each file.
recovery-strategies
Escalation path when stuck on pattern development. Use when encountering TypeScript errors, framework confusion, unexpected behavior, or blocked progress. Five-step recovery: check docs, study examples, strategic investigation (plan mode + subagents), reset and retry, ask user.
resolve-pr-comments
GitHub PRの未解決Review threadsを一括Resolveします。GraphQL APIで未解決のReview threads（コード特定行へのコメント）を取得し、resolveReviewThread mutationで全て自動的にResolveします。Issue comments（会話タブ）は元々Resolve機能がないため対象外です。各スレッドのResolve結果を表示します。
build
Quick build for small-to-medium scope work without formal planning. Still uses TDD and verification. Use when asked to "build this", "add a quick feature", "make this change", or for straightforward implementation tasks that don't need extensive design work.
implementation-planner
Create structured implementation plans from validated requirements. Use when requirements are clear and you need to break down implementation into actionable steps with testing approach.
mvp-builder
Rapid MVP development and feature prioritization for fast product validation. Use when building minimum viable products, prioritizing features, validating ideas quickly, or when users need to ship products fast while avoiding over-engineering.
agent-orchestration-multi-agent-optimize
Optimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
scrum-event-backlog-refinement
Transform PBIs into ready status for AI execution. Use when refining backlog items, splitting stories, or ensuring Definition of Ready.
prototype-designer
Create interactive prototypes, design user flows, implement prototype testing strategies, and manage handoff to development. Validate ideas before building.
skill-development
開發新 Agent Skills 的標準化工作流程。當使用者要求建立新技能、轉化工作流程為技能、或詢問 SKILL.md 格式時自動啟用。包含技能結構設計、YAML frontmatter 規範、觸發關鍵字最佳實踐、資源檔案組織。A meta-skill for creating new Agent Skills with standardized workflow, SKILL.md format specification, trigger keyword design, and resource organization best practices.
user-research
Design and conduct user research to understand needs, behaviors, and experiences. Use when user wants "journey mapping", "user interviews", "survey design", "usability testing", "user research", "customer discovery", "card sorting", "information architecture", "accessibility audit", "design critique", "prototype testing", "requirements gathering", "discovery phase", "validation phase", "research planning", or needs to understand users deeply.
pitch-worksheet
This skill provides a structured pitch development worksheet for screenwriters. Covers logline creation, story structure breakdown, character summaries, and commercial viability assessment for pitch meetings. Use when: developing a story concept into a pitchable form, preparing for pitch meetings, clarifying story structure, or testing commercial viability.
security-requirement-extraction
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
writing-specification-driven-development
Write specification documents for features using specification-driven development practices, including requirements with user stories, architecture design documents with correctness properties, and implementation plans with task breakdowns. Use when planning a new feature, designing system architecture, creating implementation roadmaps, or documenting technical specifications.
change-impact-analyzer
Determine what needs modification and identify potential side effects of changes. Use before implementing changes to understand full scope and prevent breaking existing functionality.
aesthetic-excellence
Use when improving visual quality of existing UI - applies 2025 design principles for hierarchy, spacing systems, color theory, and typography excellence to elevate aesthetic appeal and user experience
