elsa-work-unit-planner

## User Input ```text $ARGUMENTS ``` ## Outline 1. Read `AGENTS.md` for source-of-truth layers and `docs/contributing/program-goals-and-drift-guard.md` for the drift guard. 2. Read `docs/skills/catalog.md#work-unit-planner` and `docs/skills/catalog.md#promote-finding-to-work-unit`. 3. Inspect `docs/program-goals/` and identify whether the work belongs in a named bucket or should remain `none/free-flow`. 4. Read the source report/spec/constitution section behind the finding. 5. Classify the unit as architecture development, feature development, codebase verification, docs/maps/skills work, or code. 6. Define goal, success criteria, in scope, out of scope, source-of-truth layer, program-goal route, program-goal state when used, affected gates/maps/docs, tests, and review points. 7. End with a `<proposed_plan>` block listing exact files to create or update, including likely follow-through obligations such as tests, extension-point catalogs, generated-map refreshes, or docs updates. Do not run Speckit or edit code unless the user explicitly approves implementation. After a unit is approved, required follow-through obligations are part of completing that unit unless they introduce a new architecture decision.