post-analiz-handoff
Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved
SKILL.mdcatalog/agents/product-manager/skills/post-analiz-handoff/SKILL.md
GitHubPost-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)
- Architect writes the spec/plan and moves the analiz task to
analiz_review, then stops. - Human reviews the plan in
analiz_reviewand moves it todone(approve) orneed_revision(reject). This is the human's decision, not yours — do not move an analiz task out ofanaliz_review. - Architect (on approval) creates one implementation task per project, lists them in a comment, and moves the analiz task to
released.
Your steps
Trigger: the stakeholder asks what an analysis found, or about the tasks it produced. The board never dispatches you here on its own — the PM is subscribed only to pm_uat, so this skill only runs when a human brings it up in chat.
list_board_tasksto find the implementation tasks the architect created.- Read the architect's spec/plan with
list_task_documentson the ANALIZ task — they are documents attached to it, never committed to the repository — and read the task comments. - Check each created task carries
derived_frompointing at the analiz task.update_board_taskcannot setderived_from— it has no such field and silently ignores it. If the task has not started (backlog/todo/blocked),delete_board_task+create_board_taskit withderived_fromset, keeping its title, fields and criteria. If work has already started,add_task_comment: "Spec and plan:list_task_documents A-N" — so the developer can still reach them without touching a task mid-flight. - Check the order is declared, not just described. A frontend task that consumes a new endpoint should carry
blocked_byanddeploy_depends_onnaming the backend task; a "Depends on: …" sentence in the description enforces nothing.update_board_taskCAN add toblocked_by/deploy_depends_on(it adds to whatever is already there) — use it for tasks still in backlog/todo/blocked. - If stakeholder decisions were logged as questions during analysis, confirm answers exist.
- Review scope and priority. Edit acceptance criteria with
update_board_taskonly on tasks still inbacklog/todo/blocked— it replaces the whole array and resets every tick. On a task that has started, usecancel_criterionto drop one, or open a new task for added scope (see scope-management); never duplicate or re-create the architect's tasks. - Tell the stakeholder which implementation tasks are queued, in what order, and what happens next. A task sitting in
blockedbecause its blocker is still open is on schedule, not stuck — it is picked up automatically.
Common Mistakes
- Creating implementation tasks yourself — the architect owns decomposition, gated on human approval.
- Moving an analiz task from
analiz_reviewtodone— that is the human's approval action. - Expecting the tasks to exist as soon as the analiz hits
done— they appear after the architect releases the analiz. - Trying to fix a missing
derived_fromwithupdate_board_task— it silently ignores the field; delete and recreate instead. - Editing acceptance criteria on a task already in
in_progressor later — it resets every tick the developer made.
Red Flags
- You are about to
create_board_taskfor work the architect analyzed → stop; the architect creates it after approval. - You moved an analiz task out of
analiz_review→ that is the human's decision. - You called
update_board_task(derived_from=...)expecting it to take effect → it won't; delete + recreate instead.