sdd-workflow

Use this agent when resolving specification ambiguities, when users say 'clarify spec', 'identify unclear points', 'check spec ambiguity', or 'generate questions', or before running /generate-spec command when requirement clarification is needed. Systematically analyzes user requirements or existing specifications (.sdd/specification/*_spec.md) across 9 categories (Functional Scope, Data Model, Flow, Non-Functional Requirements, Integration, Edge Cases, Constraints, Terminology, Completion Criteria), identifies unclear points and ambiguities, and generates up to 5 prioritized questions. Calculates clarity scores and integrates user answers into specifications to achieve 80%+ clarity for implementation-ready specs. Works in coordination with vibe-detector skill to prevent Vibe Coding issues.

Use this agent when cross-PRD consistency review is requested across multiple PRD files, when users say 'cross-PRD review', 'review all PRDs', 'PRD 横断レビュー', or 'check consistency between PRDs', or after adding or updating a PRD when portfolio-level consistency needs verification. Reviews multiple .sdd/requirement/*.md PRD files for category boundary consistency (scope-out cross-references), terminology alignment across glossaries, structural and notation style uniformity, CONSTITUTION.md principle reference coverage, and front matter labeling consistency. Reports findings classified as [must]/[recommend]/[nits]. Note: single-PRD quality reviews are handled by prd-reviewer, front matter format validation by front-matter-reviewer, and vertical PRD-spec-design consistency by doc-consistency-checker.

Validates YAML front matter in AI-SDD documents. Checks field formats, dependency direction, status values, type-specific fields, cross-reference integrity, and id uniqueness. Use after document generation or during consistency checks. Pass target document paths as arguments.

Use this agent when PRD (Product Requirements Document) review is requested, after running /generate-prd command when quality checks are needed, or when users say 'review PRD', 'check requirements spec', or 'review requirements'. Reviews .sdd/requirement/*.md PRD files for CONSTITUTION.md compliance, SysML requirements diagram format validity, required section completeness, and requirement ID traceability. Generates fix proposals for detected violations. Requires the PRD file path to review. Note: spec/design reviews are handled by spec-reviewer.

Use this agent when requirement analysis is needed, when users say 'analyze requirements', 'check requirements diagram', 'verify traceability', or 'impact analysis', or before/after running /generate-spec or /generate-prd commands when requirement validation is needed. Analyzes .sdd/requirement/*.md SysML requirements diagrams for coverage gaps, dependency conflicts, implementation traceability, and ID numbering (naming convention, ordering, gaps). Generates actionable reports with traceability status and classified proposals ([must]=critical issues, [recommend]=improvements, [nits]=minor suggestions). Requires the requirement file path or feature name to analyze.

Analyze and extract requirements from use case diagram. Use when extracting UR/FR/NFR from use cases or when called by generate-prd.

Check consistency between implementation code and design documents (design), detecting discrepancies

Generate quality assurance checklists from specifications and plans with structured IDs and categories

Analyze specifications and generate clarification questions to eliminate ambiguity before implementation

Define and manage non-negotiable project principles (Constitution) and verify synchronization with other documents

4 hooks across 4 events