[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSBAZJFXA1W4A13QFXVCZ0":3,"skill-same:01M7CSBAZJFXA1W4A13QFXVCZ0":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7CSBAZJFXA1W4A13QFXVCZ0","board-column-flow",null,"Use when moving tasks or reporting status - the kanban column semantics, which columns are human\u002Farchitect\u002FQA gates, and where the PM actually acts","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fboard-column-flow\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: board-column-flow\ncategory: pm\ndescription: Use when moving tasks or reporting status - the kanban column semantics, which columns are human\u002Farchitect\u002FQA gates, and where the PM actually acts\n---\n# Board Column Flow\n\n## Overview\n\nThe 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.\n\n## The columns\n\nTwo spines — a given task only passes through the columns its type needs:\n\n```\ntask \u002F bug:  backlog → todo → in_progress → code_review → ready_for_qa\n             → in_qa → human_uat → done → released\n\nanaliz:      backlog → todo → in_progress → analiz_review → done → released\n\nneed_revision ← any gate that rejects (code_review, in_qa, human_uat, analiz_review)\n              → back to in_progress' owner, then forward again from where it left\n\nblocked ← parked here automatically while any blocked_by task is open\n        → released automatically when the last one lands\n```\n\n`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.\n\n## Who owns each gate\n\n| Column | Owner | PM action? |\n|--------|-------|-----------|\n| backlog | PM | Yes — create tasks here by default; stakeholder prioritizes |\n| todo | assignee agent (auto) | Move approved tasks here to start them |\n| in_progress | developer | No |\n| **analiz_review** | **human** | **No** — the human approves the architect's plan (→ done) or rejects it (→ need_revision) |\n| code_review | system-architect | No — architect advances to ready_for_qa or need_revision |\n| ready_for_qa | QA (queue — QA takes it into in_qa) | No |\n| in_qa | QA (testing in progress) | No |\n| need_revision | developer \u002F architect | Not dispatched here; act only if the stakeholder asks in chat |\n| human_uat | stakeholder | No — stakeholder reviews |\n| done \u002F released | — | Terminal; released per project convention, by release-engineer |\n\n## PM action points (only these)\n\n- **backlog:** create tasks here; the stakeholder reviews\u002Fprioritizes before agents pick them up.\n- **todo:** move approved tasks here to trigger the assignee.\n\nEverything else (analiz_review, code_review, QA columns, human_uat) is another actor's gate — don't move tasks through them.\n\n## Common Mistakes\n\n- Moving an analiz task out of `analiz_review` — that's the human's approval gate.\n- Advancing a task in `code_review` — that's the architect's.\n- Acting on a `need_revision` task uninvited — you are not dispatched there.\n\n## Red Flags\n\n- You moved a task through a column not in the PM action-points list.\n- You approved or rejected work in a QA column.\n\n## Board mechanics\n\n- 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.\n- The task is already in the column named in your context; never plan a move into the column it is already in.\n- 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.\n","# Board Column Flow\n\n## Overview\n\nThe 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.\n\n## The columns\n\nTwo spines — a given task only passes through the columns its type needs:\n\n```\ntask \u002F bug:  backlog → todo → in_progress → code_review → ready_for_qa\n             → in_qa → human_uat → done → released\n\nanaliz:      backlog → todo → in_progress → analiz_review → done → released\n\nneed_revision ← any gate that rejects (code_review, in_qa, human_uat, analiz_review)\n              → back to in_progress' owner, then forward again from where it left\n\nblocked ← parked here automatically while any blocked_by task is open\n        → released automatically when the last one lands\n```\n\n`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.\n\n## Who owns each gate\n\n| Column | Owner | PM action? |\n|--------|-------|-----------|\n| backlog | PM | Yes — create tasks here by default; stakeholder prioritizes |\n| todo | assignee agent (auto) | Move approved tasks here to start them |\n| in_progress | developer | No |\n| **analiz_review** | **human** | **No** — the human approves the architect's plan (→ done) or rejects it (→ need_revision) |\n| code_review | system-architect | No — architect advances to ready_for_qa or need_revision |\n| ready_for_qa | QA (queue — QA takes it into in_qa) | No |\n| in_qa | QA (testing in progress) | No |\n| need_revision | developer \u002F architect | Not dispatched here; act only if the stakeholder asks in chat |\n| human_uat | stakeholder | No — stakeholder reviews |\n| done \u002F released | — | Terminal; released per project convention, by release-engineer |\n\n## PM action points (only these)\n\n- **backlog:** create tasks here; the stakeholder reviews\u002Fprioritizes before agents pick them up.\n- **todo:** move approved tasks here to trigger the assignee.\n\nEverything else (analiz_review, code_review, QA columns, human_uat) is another actor's gate — don't move tasks through them.\n\n## Common Mistakes\n\n- Moving an analiz task out of `analiz_review` — that's the human's approval gate.\n- Advancing a task in `code_review` — that's the architect's.\n- Acting on a `need_revision` task uninvited — you are not dispatched there.\n\n## Red Flags\n\n- You moved a task through a column not in the PM action-points list.\n- You approved or rejected work in a QA column.\n\n## Board mechanics\n\n- 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.\n- The task is already in the column named in your context; never plan a move into the column it is already in.\n- 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.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fboard-column-flow",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill board-column-flow",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill board-column-flow",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill board-column-flow","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fboard-column-flow\u002FSKILL.md",true,[],[49,55,62,69,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","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","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","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","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","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.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","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","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","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","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]