draft / default

What problem does it solve?

It helps the system produce a concrete draft artifact for a generic work type when the action shape is ambiguous, while preventing unsafe or low-quality drafts by forcing unresolved context references to be handled first.

Core Features & Use Cases

• Context-first drafting: Loads action index data, stage files, and context_refs in a canonical order before writing anything.
• Plan-aware scope enforcement: Treats an existing plan trail (e.g., stages/<NNN>-plan.md) as binding when present.
• Guardrailed ambiguity handling: If output shape or prerequisites are unclear, blocks and escalates via awaiting_external or awaiting_operator instead of guessing.
• Artifact placement control: Produces a draft artifact by default inside the action folder to keep scope boundaries clear.

Quick Start

Use the draft / default skill to generate a reviewable artifact for a playbook: other action by ensuring all context references and any plan trail constraints are satisfied.