メニュー
Use for Phase 6 (Analyze): completeness audit, cross-analysis, compliance, and ANALYSIS.md gate decision. Trigger on sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, or sdd_check_sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to 'research codebase', 'scan tech stack', 'import documents', 'discovery questions', or needs guidance on Phase 1 research. Also trigger on 'sdd research', 'brownfield scan', 'import transcript', or 'check ecosystem'.
Use for Phase 2 (Specify): write SPECIFICATION.md with EARS, REQ-IDs, and acceptance criteria. Trigger on sdd_write_spec, sdd_turnkey_spec, sdd_validate_ears, or /specky-specify.
Use for Phase 4 (Design): produce DESIGN.md with architecture, API contracts, data model, and Mermaid diagrams. Trigger on sdd_write_design, sdd_generate_all_diagrams, or /specky-design.
Use for contracted implementation planning, executable TDD bindings, IaC, Docker, devcontainer, local environment, or Codespaces tools after an APPROVE analysis gate.
Use when starting or resuming Specky work, selecting lifecycle/workload/mode/capabilities, diagnosing config/state, or choosing an agent/tool.
This skill should be used when the user asks to 'orchestrate pipeline', 'run full pipeline', 'coordinate phases', 'advance phase', or needs guidance on end-to-end pipeline execution. Also trigger on 'specky orchestrate', 'phase transition', 'LGTM gate', 'pipeline status', or 'which agent for this phase'.
| name | specky-quality-reviewer |
| description | Use for Phase 6 (Analyze): completeness audit, cross-analysis, compliance, and ANALYSIS.md gate decision. Trigger on sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, or sdd_check_sync. |
Every call includes explicit spec_dir and feature_number.
sdd_run_analysis: also requires explicit force.sdd_cross_analyze: feature identity only.sdd_check_sync: supply explicit code_paths; do not rely on workspace-wide guessing.sdd_metrics: uses canonical feature state.Report only server values:
APPROVECHANGES_NEEDEDBLOCKDo not rename them to CONDITIONAL or REJECT. Analyze remediation tools remain available only when the persisted gate permits remediation.
Run only when compliance capability is enabled. Frameworks and control-pack version come from capability_config.compliance; callers do not select another framework per request.
sdd_compliance_check requires an evidence map keyed by control ID:
{
"SOC2-CC6.1": ["SPECIFICATION.md#REQ-AUTH-001", "DESIGN.md#Authorization"]
}
Every configured framework is evaluated. Keyword presence is not evidence. Missing control evidence fails that control. The supported packs are HIPAA, SOC 2, GDPR, PCI DSS, and ISO 27001; no generic compliance fallback exists.
Present traceability percentages, gaps, orphan IDs, control evidence, and drift details. Never override the computed gate with a prose opinion or a global threshold not persisted in the feature contract.