AI Agent Workflow Collection

Use whenever the user wants to CREATE a new basic design document — whole-system (docs/main-basic-design.md) or subsystem (docs/subsystems/{id}{name}/{name}-design.md, including nested subsystems like docs/subsystems/.../subsystems/{id}{name}/{name}-design.md). Trigger on phrases like "基本設計を作る", "draft a basic design", "新しい設計書", or any request implying production of a fresh design artifact. This skill MUST NOT update an existing basic design document — it only creates new ones — and MUST halt if the corresponding requirements document does not exist.

Use whenever the user wants to CREATE a new detailed design document — whole-system (docs/main-detail-design/index.md) or subsystem (docs/subsystems/{id}{name}/detail-design/index.md, including nested subsystems like docs/subsystems/.../subsystems/{id}{name}/detail-design/index.md). Trigger on phrases like "詳細設計を作る", "詳細設計書を書きたい", "detail design を作って", "draft a detailed design", "create detail design", "モジュールの振る舞いを設計したい". Do NOT trigger for updates to existing detailed design documents — use spec-coexist:revising instead. This skill MUST NOT update existing detail design files — it only creates new ones — and MUST halt if the corresponding basic design document does not exist. This skill is self-contained and MUST NOT delegate to any superpowers: skill.

Use whenever the user wants to CREATE a new requirements document — whole-system (docs/main-requirements.md) or subsystem (docs/subsystems/{id}{name}/{name}-requirements.md, including nested subsystems like docs/subsystems/.../subsystems/{id}{name}/{name}-requirements.md). Trigger on phrases like "要件定義を作る", "draft requirements", "new requirements doc", "要件をまとめたい", or any request that implies producing a fresh requirements artifact. This skill MUST NOT update an existing requirements document — it only creates new ones.

Use whenever the user wants a point-in-time status report of the project — completed requirements, in-progress work, uncovered REQ-IDs, and a dependency graph. Trigger on phrases like "スナップショットを生成して", "プロジェクトの現状を見たい", "ステークホルダー向けのレポート", "generate a delivery snapshot", "project status report", "what's the current state of requirements". Do NOT trigger for traceability matrix generation alone (use buildtraceabilitymatrix.sh directly) or for spec creation/revision. This skill is self-contained and MUST NOT delegate to any superpowers: skill.

Use whenever the user arrives with an unstructured wish, complaint, or idea that is NOT yet a requirements document — to DIVERGE, list hypotheses, and converge on the single problem worth solving before requirements begin. Trigger on phrases like "何を作るか迷ってる", "まだ要件にできない相談", "ざっくり相談したい", "I'm not sure what we should build", "help me figure out the real problem", "brainstorm the problem". This skill MUST hand off to spec-coexist:creating-requirements only via a written handoff memo; it MUST NOT invoke any superpowers: skill (including superpowers:brainstorming).

Use whenever verified, reviewed work is ready to be integrated — committed, changelogged, pushed, or merged — whole-system or subsystem. Trigger on phrases like "マージしたい", "PR を出して", "ブランチを締めたい", "ready to merge", "open a pull request", "wrap up this branch". This skill MUST halt if verification-before-completion evidence is missing or if any Critical/Important review finding is unresolved, and MUST halt before any destructive git operation to get explicit user confirmation. It MUST NOT invoke any superpowers: skill.

Use whenever the user wants to IMPLEMENT code based on existing requirements + basic design documents — whole-system or subsystem. Trigger on phrases like "仕様に従って実装", "implement from the spec", "この設計書のとおり作って", "build it from the basic design". This skill embeds writing-plans and executing-plans equivalents and MUST halt if either the requirements doc or the basic design doc is missing. The agent MUST NOT start implementation until the user approves the plan.

Use whenever 2 or more subsystems under docs/subsystems/ each have completed requirements + basic design and the user wants them implemented concurrently in isolated git worktrees. Trigger on phrases like "サブシステムを並列で実装したい", "複数の基本設計を同時に進めて", "worktree で並列化して", "parallelize these subsystems", "implement these in parallel worktrees". This skill MUST halt if any candidate pair has a dependency, touches shared main- files, or if the repo is dirty; it MUST NOT invoke any superpowers: skill (including superpowers:using-git-worktrees and superpowers:dispatching-parallel-agents).

Use whenever implementation code has just been written or modified and a completion claim or code-review request is imminent. Trigger on phrases like "自己レビュー", "コードの品質を確認", "レビュー前にチェック", "self review", "pre-review check", "sanity check the diff". This skill is the self-review step the implementing agent runs on its own diff BEFORE dispatching code-review-loop. It catches obvious problems (naming, complexity, boundaries, error handling, dead code, secrets, logging) before the expensive subagent round-trip. Do NOT trigger on T0 tasks or when the user explicitly skips review. This skill is self-contained and MUST NOT delegate to any superpowers: skill.

Use whenever the user wants to REVISE spec documents (requirements or basic design) OR UPDATE implementation after a spec change. Trigger on phrases like "要件を変更したい", "設計を直したい", "revise the spec", "update the requirements", "仕様変更を実装に反映", "update the code to match the new spec", "実装を直したい", "the spec changed, fix the code". Handles both spec-mode and implementation-mode internally. Do NOT trigger for creating new specs from scratch (use creating-requirements or creating-basic-design instead). This skill is self-contained and MUST NOT delegate to any superpowers: skill.

Task-tier router for the spec-coexist skill suite. Classifies every user message into T0 (trivial) / T1 (small) / T2 (medium) / T3 (large) and invokes only the skills that tier requires. Trigger on any message that involves code changes, spec work, debugging, or development tasks in this repo. Users may override with tier:T0–tier:T3 prefix. タスクのティア分類を行い、必要最小限のスキルだけを起動するルーター。 This skill is self-contained and MUST NOT delegate to any superpowers: skill.

Use whenever code is about to be written or modified as part of a spec-driven implementation — whole-system or subsystem. Trigger on phrases like "実装する", "コードを書く", "TDD で進めて", "テスト先に書く", "implement this", "write the code", "let's TDD this". This skill is a REQUIRED SUB-SKILL of spec-coexist:implementing-from-spec and spec-coexist:revising and MUST halt if a failing test does not exist before production code is written. Carves out legacy/spike/notebook/config/docs via references/negative-triggers.md.

T0/T1 タスク専用の最短経路スキル。spec 文書を一切要求せず、必要最小限のプロセスだけを通す。 T0 (typo, rename, ≤10行) は直接編集、T1 (単一関数追加, バグ修正) は TDD + verification のみ。 Use for trivial and small tasks: typo fixes, renames, single-function additions, bug fixes. Trigger on "tier:T0", "tier:T1", "ちょっとした修正", "typo直して", "quick fix", "small change", "この関数を追加", "バグ修正". Do NOT trigger on T2/T3 tasks or anything requiring spec documents. This skill is self-contained and MUST NOT delegate to any superpowers: skill.