Plan demonstrable outcomes

Plan the result people need, not a catalogue of tasks or technology choices. A plan authorizes neither implementation nor external publication.

For work limited to project agreements, inspect only the relevant project evidence and use step 3 with its reference. Stop when that reference's completion criterion is met, then report the instruction result and loading limits. Use the full sequence below for project or milestone planning.

1. Establish the objective

Inspect the existing project, plans, agreements, and current state. Identify the intended experience or outcome, audience, constraints, available people and resources, exclusions, and delivery expectations. Resolve visible facts before asking.

Ask only about decisions that materially affect scope or direction. Record assumptions and unresolved questions without substituting an agent preference for a user choice.

Done when: the objective, boundaries, decision owners, and planning scope are clear.

2. Resolve consequential uncertainty

Identify risks that could change the plan: feasibility, data, integration, architecture, tools, resources, or dependencies. Reuse established choices when adequate. Compare credible alternatives only where evidence could change the decision.

Use a bounded investigation for disputed facts or a representative prototype for observable behavior when authorized. Keep unrun experiments as proposals. Technical feasibility and user acceptance need different evidence.