spec-refinement

To convert vague roadmap notes into actionable specifications, use iterative ambiguity reduction with structured Socratic questioning. This process clarifies underspecified phases and generates a falsifiable SPEC.md containing clear requirements, scope, and acceptance criteria.

Socratic questioning in requirement engineering is a structured interrogation method used to reduce ambiguity. It systematically challenges vague phase descriptions to expose assumptions, ensuring roadmap planning yields falsifiable, actionable specifications rather than subjective interpretations.

You can generate a SPEC.md with clear acceptance criteria by triggering a refinement round on an underspecified phase. The skill applies structured ambiguity scoring to formalize scope refinement, outputting a concrete document with testable requirements.

Yes, spec refinement supports integration with roadmap and phase planning workflows. It operates directly within colony projects to refine scope and requirement engineering outputs, ensuring generated specifications align with existing planning structures.

The best way to reduce ambiguity in product specifications is applying structured ambiguity scoring alongside Socratic questioning. This formal approach converts underspecified phase descriptions into falsifiable requirements, significantly reducing rework for engineering squads.

You should use a formal SPEC.md generation workflow when roadmap planning produces vague phase descriptions that risk rework. It locks in falsifiable requirements and acceptance criteria whenever scope refinement and structured ambiguity reduction are needed.