weaver-plan

Author phases as goal plus acceptance criteria plus guardrails rather than step scripts, then land the plan via ch_create_mission_with_plan so Brain writes it to DynamoDB and mqtt-bridge republishes it to Weaver. Alternatively write a local plans/*.yaml file and call start_mission for fast orchestrator-only iteration.

mission-forge is the generic idea-to-ContextHub-mission pipeline including AgentCore Mode 2 generation. weaver-plan is for Weaver Hub specifically, encoding goal-focused Manager-mode authoring, the design-checkpoint-implement pattern, and Weaver schema traps like the ignored execution_target field.

A common cause is a file_exists or file_contains check in a dod_gate without a repo set on a multi-repo mission; the path resolves against the mission worktree root where only repo directories live, so the check can never pass. Always set repo on file checks when the mission owns more than one repo.

Not through a typed field yet. Model is chosen per execution mode in Weaver settings, so a per-todo model tier must ride in the todo metadata bag, which the MQTT PlanTodo wire shape carries. Assign tiers by altitude: Opus/Fable for design and review, Sonnet for execution, Haiku for mechanical sweeps.

Use goal_gated for outcome-shaped work where done must be proven by a machine-verifiable Definition-of-Done gate, such as a command with expected exit code. Use task_list for concrete known-shape work like docs phases or mechanical refactors where each todo completes on its own commit evidence.