workflow-kit-specify

To write a specification without implementation details, you create a self-contained atomic spec.md that captures WHAT/WHY, scope boundaries, and verification. This enforces no-HOW writing, ensuring requirements stay separate from implementation decisions for the next agent step.

An atomic workflow specification is a single self-contained spec.md defining one verifiable desired result for agent handoff. You need it when preparing the next workflow step, preventing implementation guessing by explicitly capturing requirements, scope boundaries, and open questions.

To manage scope boundaries and open questions in a markdown specification, you force unknowns into explicit clarification requests or safe assumptions. This ensures planning doesn't stall later by requiring a single verifiable desired result before proceeding.

If your change request lacks a single verifiable desired result, the workflow specification process stops and requests clarification. This prevents ambiguous requirements from leaking into the spec.md, ensuring the next agent step receives a checkable atomic specification.

You must use the required SPEC-TEMPLATE.md for atomic specification creation and scope control, with an optional SCOPE-TEMPLATE.md. These templates enforce the no-HOW writing structure and ensure the spec.md is prepared for the downstream workflow-kit-plan step.