gen-draft

To create a structured requirements draft, you can use a two-phase human-in-the-loop workflow that consolidates missing context into a checklist and then generates a draft.md capturing the WHAT and WHY of your task.

The best way to plan software features is to generate a high-level draft document that explicitly separates facts from implementation decisions, recording constraints, inputs, and observable outputs before coding begins.

To write an experiment plan with constraints and acceptance criteria, use a strict template that enforces execution-order rules and specifies observable outputs, ensuring the WHY of the experiment is documented prior to training.

Yes, you can use a mandatory context-gathering checklist to collect missing information for operational task planning, which then informs the generation of a structured draft document.

A human-in-the-loop question phase is needed to consolidate and validate missing context, ensuring the resulting draft.md accurately captures explicit facts and observable outputs without jumping to premature implementation decisions.

You should avoid generating a high-level draft document when your task is fully specified with no missing context, or when capturing the high-level WHAT and WHY is unnecessary for the immediate implementation phase.