[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSBWJMBSAFX6GSYGQM2WGV":3,"skill-same:01M7CSBWJMBSAFX6GSYGQM2WGV":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},"01M7CSBWJMBSAFX6GSYGQM2WGV","pm-as-solo-orchestrator",null,"Use when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todo","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\u002Fpm-as-solo-orchestrator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pm-as-solo-orchestrator\ncategory: pm\ndescription: Use when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todo\n---\n# PM as Solo Orchestrator\n\n## Overview\n\nWhen product-manager is the only enabled orchestration agent, the plan you write for a request is not a multi-agent handoff — it's one subtask that writes the board, followed by columns doing the rest of the work automatically.\n\n**Core principle:** One subtask creates the tasks; the board, not the plan, drives every stage after that.\n\n## Rules\n\n- All subtasks are assigned to product-manager — never to system-architect, security-agent, backend-developer, frontend-developer, mobile-developer, data-scientist, game-developer, or qa-agent. Developer work goes through `create_board_task`, not an orchestration subtask.\n- Multiple parallel PM subtasks are fine only when every one is read-only (e.g. web research + `list_board_tasks` concurrently). At most one subtask per parallel group may write to the board; a second board writer in the same group rejects the whole plan. Use `depends_on` to sequence when a later subtask needs an earlier one's result.\n- Delivery stages (analiz, implementation, QA verification, approval) are board columns the task travels through afterwards — never plan a subtask per stage; that opens one board record per stage for a single piece of work and is rejected before the plan runs.\n- Analiz tasks skip approval — they go straight to `todo` (investigation is always safe to start).\n- Planner sets `ready=false` only when a product decision blocks creating any board task (max 3 questions, see stakeholder-intake's ask-vs-assume rule). Otherwise `ready=true`.\n\n## Standard flow — one subtask, in order\n\n1. Create the tasks in `backlog` (see implementation-task-spec, acceptance-criteria-gwt).\n2. Call `ask_user`, choice mode:\n   - `context`: what you asked \u002F what you're assuming (name each assumption so the stakeholder can correct it cheaply) \u002F the task list with assignee and order.\n   - options: \"Start all (recommended)\", \"Start only some\", \"Change something\", plus whatever else applies.\n3. On approval, move every approved task to `todo` with `move_board_task`. Order lives in `blocked_by` — never hold a task back in `backlog` to fake an order; a blocked task parks itself and starts automatically once its blocker lands.\n4. On partial approval, move only the selected tasks; leave the rest in `backlog`.\n5. On rejection or requested changes, `update_board_task` the affected fields, or `delete_board_task` + `create_board_task` for `assignee`\u002F`derived_from` (creation-only fields) — and for `task_type` when `update_board_task`'s schema does not list it.\n6. Report which tasks moved to `todo` (agents will pick them up) and which stay in `backlog`, and why.\n\nThis is ONE subtask calling these tools in order — not three subtasks. Splitting it hands the same board record to several agents that cannot see each other's writes.\n\nIf a blocking product decision remains, call `ask_user` within a subtask — never append questions as markdown in the final summary.\n\n## Common Mistakes\n\n- A subtask per delivery stage instead of one subtask that creates the tasks.\n- Holding implementation tasks in `backlog` \"until analiz is done\" instead of using `blocked_by` — the board already enforces that order.\n- Two parallel subtasks writing to the board in the same group.\n- Approval-question `context` that doesn't separate what you asked from what you assumed.\n\n## Red Flags\n\n- A plan with a subtask named \"QA stage\" or \"human_uat review\" — those are columns, not subtasks.\n- More than one board-writing subtask in a parallel group.\n- A task left in `backlog` with a \"Depends on: …\" sentence instead of `blocked_by`.\n","# PM as Solo Orchestrator\n\n## Overview\n\nWhen product-manager is the only enabled orchestration agent, the plan you write for a request is not a multi-agent handoff — it's one subtask that writes the board, followed by columns doing the rest of the work automatically.\n\n**Core principle:** One subtask creates the tasks; the board, not the plan, drives every stage after that.\n\n## Rules\n\n- All subtasks are assigned to product-manager — never to system-architect, security-agent, backend-developer, frontend-developer, mobile-developer, data-scientist, game-developer, or qa-agent. Developer work goes through `create_board_task`, not an orchestration subtask.\n- Multiple parallel PM subtasks are fine only when every one is read-only (e.g. web research + `list_board_tasks` concurrently). At most one subtask per parallel group may write to the board; a second board writer in the same group rejects the whole plan. Use `depends_on` to sequence when a later subtask needs an earlier one's result.\n- Delivery stages (analiz, implementation, QA verification, approval) are board columns the task travels through afterwards — never plan a subtask per stage; that opens one board record per stage for a single piece of work and is rejected before the plan runs.\n- Analiz tasks skip approval — they go straight to `todo` (investigation is always safe to start).\n- Planner sets `ready=false` only when a product decision blocks creating any board task (max 3 questions, see stakeholder-intake's ask-vs-assume rule). Otherwise `ready=true`.\n\n## Standard flow — one subtask, in order\n\n1. Create the tasks in `backlog` (see implementation-task-spec, acceptance-criteria-gwt).\n2. Call `ask_user`, choice mode:\n   - `context`: what you asked \u002F what you're assuming (name each assumption so the stakeholder can correct it cheaply) \u002F the task list with assignee and order.\n   - options: \"Start all (recommended)\", \"Start only some\", \"Change something\", plus whatever else applies.\n3. On approval, move every approved task to `todo` with `move_board_task`. Order lives in `blocked_by` — never hold a task back in `backlog` to fake an order; a blocked task parks itself and starts automatically once its blocker lands.\n4. On partial approval, move only the selected tasks; leave the rest in `backlog`.\n5. On rejection or requested changes, `update_board_task` the affected fields, or `delete_board_task` + `create_board_task` for `assignee`\u002F`derived_from` (creation-only fields) — and for `task_type` when `update_board_task`'s schema does not list it.\n6. Report which tasks moved to `todo` (agents will pick them up) and which stay in `backlog`, and why.\n\nThis is ONE subtask calling these tools in order — not three subtasks. Splitting it hands the same board record to several agents that cannot see each other's writes.\n\nIf a blocking product decision remains, call `ask_user` within a subtask — never append questions as markdown in the final summary.\n\n## Common Mistakes\n\n- A subtask per delivery stage instead of one subtask that creates the tasks.\n- Holding implementation tasks in `backlog` \"until analiz is done\" instead of using `blocked_by` — the board already enforces that order.\n- Two parallel subtasks writing to the board in the same group.\n- Approval-question `context` that doesn't separate what you asked from what you assumed.\n\n## Red Flags\n\n- A plan with a subtask named \"QA stage\" or \"human_uat review\" — those are columns, not subtasks.\n- More than one board-writing subtask in a parallel group.\n- A task left in `backlog` with a \"Depends on: …\" sentence instead of `blocked_by`.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fpm-as-solo-orchestrator",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 pm-as-solo-orchestrator",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill pm-as-solo-orchestrator",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill pm-as-solo-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fpm-as-solo-orchestrator\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",[],[]]