[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSANHGC13H3EGT0WSSQTRG":3,"skill-same:01M7CSANHGC13H3EGT0WSSQTRG":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},"01M7CSANHGC13H3EGT0WSSQTRG","answer-workspace-questions",null,"Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval","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\u002Fanswer-workspace-questions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: answer-workspace-questions\ncategory: pm\ndescription: Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval\n---\n# Answer Workspace Questions\n\n## Overview\n\nA factual question deserves a factual answer, not a plan. The failure mode is treating \"how many projects do we have?\" as work to orchestrate — creating tasks, asking approval, or claiming there's \"no active context.\" Just call the read tool and answer.\n\n**Core principle:** Read tool first, then answer in one or two sentences with the real data.\n\n## The read tools\n\n| Question | Tool |\n|----------|------|\n| How many projects \u002F what are they | `list_projects` |\n| What repositories exist \u002F which project each belongs to | `list_repositories` |\n| Who is on the team \u002F which role does what | `list_team` |\n| What's on the board \u002F a task's status | `list_board_tasks` |\n| Overall status \u002F \"how are we doing\" | `get_board_summary` (aggregated by column\u002Ftype\u002Fpriority) |\n| What's next \u002F what's ready to start | `list_ready_tasks` |\n\nThese read tools are **always available and never need an active repository** — never answer \"no active project\u002Frepo context.\" Call the tool and use the real data.\n\n## Rules\n\n1. Call the matching read tool FIRST.\n2. Prefer `get_board_summary` for \"status\u002Fhow are we doing\" over listing every task — it returns the total and counts grouped by column, type and priority in one call. Only drill into `list_board_tasks` when the stakeholder asks about a specific task or you need titles\u002Fassignees.\n3. Answer conversationally with actual numbers\u002Fnames — e.g. \"We have 2 projects right now: Alpha and Beta.\"\n4. Translate counts into an outcome update, don't just recite them: what's in progress, what's waiting (backlog\u002Ftodo), what's blocked or in review (need_revision\u002Fhuman_uat), and the biggest bucket (see stakeholder-communication).\n5. Do NOT create tasks, ask for approval, open analiz, or describe your internal plan for a plain question — just answer like a human PM.\n\n## Worked Example\n\nStakeholder: \"How many repos do we have?\" → call `list_repositories` → \"We have 3 repos: backend-api, web, and mobile.\"\nStakeholder: \"Who is on the team?\" → call `list_team` → answer from what it returns, e.g. \"system-architect and security-agent review, backend, frontend, mobile, data and game developers build, qa tests — each one owns its own area.\"\nStakeholder: \"How are we doing?\" → `get_board_summary` → {total 24; in_progress 3, code_review 2, need_revision 4, backlog 10, done 5} → \"24 tasks in total. 3 are in active development, 2 are in architecture review. 4 went back for revision — that's where the biggest risk is. 10 are queued and 5 are done.\" Not a wall of 24 task titles.\n\n## Common Mistakes\n\n- Answering from memory instead of calling the tool.\n- \"No active project context\" — the read tools never need one.\n- Turning a plain question into an orchestration plan.\n- Paging `list_board_tasks` for a status question `get_board_summary` answers in one call.\n- Reporting raw counts with no interpretation or risk callout.\n\n## Red Flags\n\n- You created a task in response to a factual question.\n- You answered a count without calling a read tool.\n- A status update with no mention of the blocked\u002Frevision bucket.\n","# Answer Workspace Questions\n\n## Overview\n\nA factual question deserves a factual answer, not a plan. The failure mode is treating \"how many projects do we have?\" as work to orchestrate — creating tasks, asking approval, or claiming there's \"no active context.\" Just call the read tool and answer.\n\n**Core principle:** Read tool first, then answer in one or two sentences with the real data.\n\n## The read tools\n\n| Question | Tool |\n|----------|------|\n| How many projects \u002F what are they | `list_projects` |\n| What repositories exist \u002F which project each belongs to | `list_repositories` |\n| Who is on the team \u002F which role does what | `list_team` |\n| What's on the board \u002F a task's status | `list_board_tasks` |\n| Overall status \u002F \"how are we doing\" | `get_board_summary` (aggregated by column\u002Ftype\u002Fpriority) |\n| What's next \u002F what's ready to start | `list_ready_tasks` |\n\nThese read tools are **always available and never need an active repository** — never answer \"no active project\u002Frepo context.\" Call the tool and use the real data.\n\n## Rules\n\n1. Call the matching read tool FIRST.\n2. Prefer `get_board_summary` for \"status\u002Fhow are we doing\" over listing every task — it returns the total and counts grouped by column, type and priority in one call. Only drill into `list_board_tasks` when the stakeholder asks about a specific task or you need titles\u002Fassignees.\n3. Answer conversationally with actual numbers\u002Fnames — e.g. \"We have 2 projects right now: Alpha and Beta.\"\n4. Translate counts into an outcome update, don't just recite them: what's in progress, what's waiting (backlog\u002Ftodo), what's blocked or in review (need_revision\u002Fhuman_uat), and the biggest bucket (see stakeholder-communication).\n5. Do NOT create tasks, ask for approval, open analiz, or describe your internal plan for a plain question — just answer like a human PM.\n\n## Worked Example\n\nStakeholder: \"How many repos do we have?\" → call `list_repositories` → \"We have 3 repos: backend-api, web, and mobile.\"\nStakeholder: \"Who is on the team?\" → call `list_team` → answer from what it returns, e.g. \"system-architect and security-agent review, backend, frontend, mobile, data and game developers build, qa tests — each one owns its own area.\"\nStakeholder: \"How are we doing?\" → `get_board_summary` → {total 24; in_progress 3, code_review 2, need_revision 4, backlog 10, done 5} → \"24 tasks in total. 3 are in active development, 2 are in architecture review. 4 went back for revision — that's where the biggest risk is. 10 are queued and 5 are done.\" Not a wall of 24 task titles.\n\n## Common Mistakes\n\n- Answering from memory instead of calling the tool.\n- \"No active project context\" — the read tools never need one.\n- Turning a plain question into an orchestration plan.\n- Paging `list_board_tasks` for a status question `get_board_summary` answers in one call.\n- Reporting raw counts with no interpretation or risk callout.\n\n## Red Flags\n\n- You created a task in response to a factual question.\n- You answered a count without calling a read tool.\n- A status update with no mention of the blocked\u002Frevision bucket.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fanswer-workspace-questions",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 answer-workspace-questions",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill answer-workspace-questions",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill answer-workspace-questions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fanswer-workspace-questions\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",[],[]]