| name | sdd-4a-validate |
| description | Validate plan readiness before implementation with parallel quality gates. Use when: a plan has been created by the Architect phase and you want to verify completeness, doctrine compliance, and dependency ordering before starting implementation. |
SDD Phase 4a: Validate Plan
[!CAUTION]
Do NOT modify any source files during this phase. This is a READ-ONLY validation command.
Validate that a plan is ready for implementation by running parallel quality gates.
Inputs
- slug (Optional): Slug from prior phases. Inferred from context if omitted.
- plan (Optional): Path to the plan file from Phase 4 (Architect).
Step 0: Doctrine Resolution
Before starting, resolve project conventions:
- Check for project doctrine files:
docs/project-rules/ (constitution.md, rules.md, idioms.md, architecture.md)copilot-instructions.md, AGENTS.md, CONTRIBUTING.md, README.md
- If no doctrine found, scan the codebase for dependency manifests, build systems, and directory patterns.
- Extract: build command, test command, coverage threshold, naming conventions, CI platform.
- Unknown values become explicit
[TODO] markers — never assume silently.
Step 1: Load Plan Context
- Read the plan file from
{plan} or .copilot-tracking/plans/{date}/{slug}/{slug}-plan.md.
- Read the specification for cross-reference.
- Read the research dossier if it exists.
- Read any workshop documents or ADRs created during this cycle.
Step 2: Launch Parallel Validators
Run these validators concurrently:
