Plan Validation

Overview

This skill validates the plan itself before implementation starts.

It exists because the summon/stream/dominion workflow increasingly depends on plan metadata being correct. A good-looking plan that is structurally incomplete can cause subtle downstream failures:

• streams that cannot be claimed correctly
• false dependencies that kill parallelism
• overlapping file ownership
• final validation mode missing
• no clear verification story

When to Use

• Before /stream or /dominion on any multi-stream plan
• When a plan was edited manually after generation
• When a plan was written outside the normal /summon workflow
• When the user says "validate the plan", "check this plan", or "is this plan executable?"