plan / default

To create an action plan for an unspecified workflow, load action context, context_refs, and originating signals to draft required plan sections. This enforces approach discipline by requiring explicit artifact kind, artifact location, and out-of-scope boundaries before execution begins.

Approach discipline in operational safety planning forces explicit declaration of artifact kind, artifact location, and out-of-scope boundaries. This grounding mechanism ensures downstream planning and verification remain anchored to tangible outputs rather than ambiguous objectives.

When external information is missing during action planning, the workflow outputs a 'blocked' or 'awaiting_external' decision value. This clearly marks the plan as requiring specific external inputs before proceeding further down the operational pipeline.

Yes, you use context loading to ingest action index files, stage files, and context references before drafting plans for unshaped work. This context-aware mechanism supplies the necessary originating signals and sensitive policy notes to generate a complete operational plan.

The limitation of using a default playbook for action planning is that it only applies to 'playbook: other' scenarios. If a specific predefined workflow shape exists, this drafting approach is bypassed in favor of the dedicated operational playbook.