adversarial-reasoning
Red-team thinking for robustness testing and edge case discovery. Use when you need to stress-test solutions, find vulnerabilities, anticipate failures, or challenge assumptions. Ideal for security review, system design validation, decision stress-testing, and pre-mortem analysis. Example: "We've designed an auth system" → Attack it from 10 angles before shipping.
devops-incident-responder
Expert in SRE practices, incident management, root cause analysis, and automated remediation.
spec-add-idea
新しい機能アイデアを軽量Specとして specs/000_backlog に追加し、specs/INDEX.md を更新する。実装は行わず、ドキュメント作成と索引更新のみを行う。Use when the user wants to add a new feature idea to the backlog or create a lightweight specification.
plan-reviewer
Review implementation plans (plan.md) for spec compliance and feasibility.
task-management
Framework for systematic task execution using a state machine (Planning, Execution, Closing). Used for (1) complex feature implementation requiring multiple steps, (2) root-cause analysis and bug fixing, and (3) creation and organization of comprehensive design documents.
github-review-cycle
manage pull request code reviews, approvals, comments, and feedback cycles
vulnerability-management
Vulnerability assessment, tracking, and remediation management. Process scan results, prioritize findings, and track remediation progress. Use for vulnerability management programs and security assessments.
star-techspec
Do techspec step of the PLANNING phase of star-team workflow.
spec-workflow
Spec-driven development workflow for systematic feature development. Use when starting a new feature to ensure proper research, requirements, design, tasks, and execution phases.
merge-archive-plan
Archive completed implementation plans after PR merge. Use when a plan's implementation has been merged to main, or after plan-execute completes on main branch.
spec-driven-dev
仕様駆動開発スキル。アイデアから仕様書作成、自律開発ループ、検証まで一連の流れをサポート。新規プロジェクト開始時に使用。
project-review
This skill should be used for reviewing current project against mature project patterns, tool capabilities, and org standards. Triggers include "review this project", "what am I missing", "align with standards", "check tool usage", "compare to arbor/koto", or proactively at session start in unfamiliar projects. Surfaces gaps in patterns, underutilized tools, and org standard deviations.
workflowresolve-escalation
Records a resolution for a human escalation.
issue-splitter
Split complex issues into smaller, implementable sub-issues. Called automatically when ComplexityGate determines an issue needs splitting.
create-issue
Creates GitHub issues with proper formatting and labels. Use when the user wants to report a bug, request a feature, or create documentation tasks.
technical-discussion
Collaborative technical discussion with proactive requirements gathering
close-work-cycle
HAIOS Close Work Cycle for structured work item closure. Use when closing work items. Guides VALIDATE->ARCHIVE->MEMORY workflow with DoD enforcement.
