draft / default

To generate a draft artifact with ambiguous action context, load action index data, stage files, and context_refs in a canonical order before writing. This enforces context and plan constraints to safely produce a reviewable artifact.

When context references are unresolved during artifact generation, the process blocks and escalates via awaiting_external or awaiting_operator statuses instead of guessing, ensuring unsafe or low-quality drafts are prevented.

To enforce plan trail scope during drafting, treat an existing plan trail file like stages/<NNN>-plan.md as binding when present. This keeps the generated artifact within established scope boundaries.

The drafted artifact is placed by default inside the action folder. This artifact placement control ensures scope boundaries remain clear for the generic playbook action being processed.

Use context-first drafting for playbook other actions when converting an action's summary and signals into a concrete artifact. It requires ordered context loading before writing to ensure review-draft suitability.

Yes, the draft workflow supports operator escalation for blocked outputs by emitting safe decision outputs like drafted or blocked. It escalates blocked states via awaiting_external or awaiting_operator when prerequisites are unclear.