board-column-flow
Use when moving tasks or reporting status - the kanban column semantics, which columns are human/architect/QA gates, and where the PM actually acts
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 122
- Forks
- 18
01 前言 Front Matter
- name
- board-column-flow
- category
- pm
- description
- Use when moving tasks or reporting status - the kanban column semantics, which columns are human/architect/QA gates, and where the PM actually acts
03 SKILL.md 正文
Board Column Flow
Overview
The board has more columns than the PM acts in. Knowing which columns belong to the human, the architect, and QA keeps you from moving a task through a gate that isn't yours.
The columns
Two spines — a given task only passes through the columns its type needs:
task / bug: backlog → todo → in_progress → code_review → ready_for_qa
→ in_qa → human_uat → done → released
analiz: backlog → todo → in_progress → analiz_review → done → released
need_revision ← any gate that rejects (code_review, in_qa, human_uat, analiz_review)
→ back to in_progress' owner, then forward again from where it left
blocked ← parked here automatically while any blocked_by task is open
→ released automatically when the last one lands
need_revision is not a stage in the line — it is where every gate sends work back, and the PM is not dispatched there: act on a need_revision task only if the stakeholder raises it in chat. done → released is release-engineer's step, not yours.
Who owns each gate
| Column | Owner | PM action? |
|---|---|---|
| backlog | PM | Yes — create tasks here by default; stakeholder prioritizes |
| todo | assignee agent (auto) | Move approved tasks here to start them |
| in_progress | developer | No |
| analiz_review | human | No — the human approves the architect's plan (→ done) or rejects it (→ need_revision) |
| code_review | system-architect | No — architect advances to ready_for_qa or need_revision |
| ready_for_qa | QA (queue — QA takes it into in_qa) | No |
| in_qa | QA (testing in progress) | No |
| need_revision | developer / architect | Not dispatched here; act only if the stakeholder asks in chat |
| human_uat | stakeholder | No — stakeholder reviews |
| done / released | — | Terminal; released per project convention, by release-engineer |
PM action points (only these)
- backlog: create tasks here; the stakeholder reviews/prioritizes before agents pick them up.
- todo: move approved tasks here to trigger the assignee.
Everything else (analiz_review, code_review, QA columns, human_uat) is another actor's gate — don't move tasks through them.
Common Mistakes
- Moving an analiz task out of
analiz_review— that's the human's approval gate. - Advancing a task in
code_review— that's the architect's. - Acting on a
need_revisiontask uninvited — you are not dispatched there.
Red Flags
- You moved a task through a column not in the PM action-points list.
- You approved or rejected work in a QA column.
Board mechanics
- Claiming a task and moving it between columns takes seconds and announces what you are doing; it produces nothing by itself. Do it inside the step that does the work, never a step of its own and never as the first item of a plan — a step whose only content is a claim or a move is rejected before it runs.
- The task is already in the column named in your context; never plan a move into the column it is already in.
- If the payload says resumed=question_answered: you previously stopped on the question in payload.question and the human replied in payload.answer — continue from where you stopped using that answer; do not ask it again.
04 同仓库更多 Skills
visual-craft
暂无简介
ux-copy
Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check
screen-mockup-html
Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task
performance-awareness
How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.
design-variants
Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision
design-system-authoring
Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns