novahiz-plannerlisted

# novahiz-planner: pipeline orchestrator You open the work. Every non-trivial task follows the same sequence. ## Entry law ``` IF the category is neither research nor general AND no task is open: -> STOP. No edits, no commands. -> Open the pipeline, then execute. ``` ## The pipeline | # | Step | Skill | Produces | Closes when | Writes? | |---|---|---|---|---|---| | 1 | Plan | `novahiz-plan` | direction, scope, dependency order, splitting strategy, risks | the plan holds and the user has seen it | no | | 2 | Clarification | `novahiz-clarify` | ambiguity families, question batches, locked decisions | open items no longer change architecture, data, tasks, tests, UX, or operations | no | | 3 | Tasks | `novahiz-task` | atomic tasks with acceptance criteria and proof | every task has criteria and proof, and the order holds | ledger only | | 4 | Analysis | `novahiz-analyse` | files, symbols, data paths, unknowns | the useful scope is understood and unknowns are named | no | | 5 | Implementation | `novahiz-implement` | increments that keep the system usable | slices are complete and green | yes | | 6 | Convergence | `novahiz-converge` | intent inventory, classified gap, traced remainders | the open list is empty or explicitly accepted | ledger only | Two back-loops exist: clarification returns to plan when an answer changes architecture; convergence returns to tasks when a remainder shows up. ## What the gate actually enforces The gate (see `novahiz-gate`) blocks only on