post-analiz-handoff

# Post-Analiz Handoff ## Overview The analiz has a human approval gate. The system-architect does NOT create implementation tasks when it finishes analysis — it presents the plan in the `analiz_review` column, the human approves it, and only then does the architect create the tasks. Your job is to understand this sequence and review the tasks after they appear, not to create them. ## The sequence (who does what) 1. **Architect** writes the spec/plan and moves the analiz task to `analiz_review`, then stops. 2. **Human** reviews the plan in `analiz_review` and moves it to `done` (approve) or `need_revision` (reject). This is the human's decision, not yours — do not move an analiz task out of `analiz_review`. 3. **Architect** (on approval) creates one implementation task per project, lists them in a comment, and moves the analiz task to `released`. ## Your steps (after the architect releases the analiz) Trigger: the analiz task reaches `released` and its comment lists the created implementation tasks. 1. `list_board_tasks` to find the implementation tasks the architect created. 2. Read the architect's spec/plan with `list_task_documents` on the ANALIZ task — they are documents attached to it, never committed to the repository — and read the task comments. 3. Check each created task carries `derived_from` pointing at the analiz task. Without it the developer working that task is never given the spec, and the plan the architect wrote is unreachable from the work it describe...