spec-coexist

Use whenever implementation work needs code review, or when review feedback has been received. Combines requesting and receiving review into one loop. Trigger on phrases like "コードレビューして", "review this change", "実装できたのでレビュー", "before I merge", "レビューが返ってきた", "here is the review feedback", "reviewer said...". Dispatches a fresh reviewer subagent, then processes feedback with verify-then-fix discipline (verify each item against the codebase before implementing any fix). Do NOT trigger on T0/T1 tasks unless the user explicitly requests review. This skill is self-contained and MUST NOT delegate to any `superpowers:*` skill.

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 `build_traceability_matrix.sh` directly) or for spec creation/revision. This skill is self-contained and MUST NOT delegate to any `superpowers:*` skill.