[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSAC6ZPWVX2SVYN6D56RMC":3,"skill-same:01M7CSAC6ZPWVX2SVYN6D56RMC":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},"01M7CSAC6ZPWVX2SVYN6D56RMC","analiz-gate",null,"Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation","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\u002Fanaliz-gate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analiz-gate\ncategory: pm\ndescription: Use when deciding whether a request needs an analiz task before implementation - the conditions that require the architect's analysis versus going straight to implementation\n---\n# Analiz Gate\n\n## Overview\n\nSome work can go straight to implementation tasks; some needs the architect to investigate first. Guessing wrong is costly: skipping a needed analiz produces bounced tasks, and forcing analiz on trivial work wastes a cycle.\n\n**Core principle:** Analiz when the approach is unknown; skip it when the work is clear and small.\n\n## Open a type=analiz task when ANY of\n\n- The stack\u002Fframework for the feature is unknown.\n- The API or UI contract between components is undefined.\n- The request is broad and needs technical slicing.\n- Repository feasibility is unknown (new integration, DB schema change).\n- Estimated scope > 1 developer-day with unclear breakdown.\n- A new frontend or app has no design system yet (`get_design_system` returns nothing) and its screens still need slicing — open the design-system task yourself with `request_design_system` (implementation-task-spec) so it runs alongside the analysis, and carry the design brief and its key in the analiz description; the architect makes the UI tasks wait for it.\n- The change spans two or more repositories, or creates a new API contract between layers.\n- It's a greenfield product or a brand-new repository.\n\nWhen unsure between a direct task and analiz, take analiz — hidden complexity only grows once implementation starts.\n\n## Do NOT open analiz for\n\n- Small bug fixes with clear reproduction steps.\n- Pure UI copy or styling changes.\n- Features already analyzed and documented.\n\n## Mechanics\n\nAssign the analiz task to **system-architect** and move it to `todo` (investigation is always safe to start — no stakeholder approval needed). The analysis itself returns through the **human analiz_review gate** before any implementation task is created. Never assign analiz to yourself or a developer.\n\n## Worked Example\n\n- \"Change the button label from 'Save' to 'Apply'.\" → No analiz: pure copy change → one frontend task.\n- \"Add real-time notifications.\" → Analiz: transport (WebSocket? SSE? polling?) and the contract are undefined → analiz task to the architect.\n- \"Fix the 500 when deleting a task with subtasks.\" → No analiz: clear repro → one bug task.\n\n## Common Mistakes\n\n- Forcing analiz on a one-line copy change.\n- Skipping analiz on a broad \"add reporting\" request → the dev bounces on undefined scope.\n- Assigning analiz to a developer.\n\n## Red Flags\n\n- An implementation task created for a request whose approach nobody has defined.\n- An analiz task assigned to anyone but the architect.\n","# Analiz Gate\n\n## Overview\n\nSome work can go straight to implementation tasks; some needs the architect to investigate first. Guessing wrong is costly: skipping a needed analiz produces bounced tasks, and forcing analiz on trivial work wastes a cycle.\n\n**Core principle:** Analiz when the approach is unknown; skip it when the work is clear and small.\n\n## Open a type=analiz task when ANY of\n\n- The stack\u002Fframework for the feature is unknown.\n- The API or UI contract between components is undefined.\n- The request is broad and needs technical slicing.\n- Repository feasibility is unknown (new integration, DB schema change).\n- Estimated scope > 1 developer-day with unclear breakdown.\n- A new frontend or app has no design system yet (`get_design_system` returns nothing) and its screens still need slicing — open the design-system task yourself with `request_design_system` (implementation-task-spec) so it runs alongside the analysis, and carry the design brief and its key in the analiz description; the architect makes the UI tasks wait for it.\n- The change spans two or more repositories, or creates a new API contract between layers.\n- It's a greenfield product or a brand-new repository.\n\nWhen unsure between a direct task and analiz, take analiz — hidden complexity only grows once implementation starts.\n\n## Do NOT open analiz for\n\n- Small bug fixes with clear reproduction steps.\n- Pure UI copy or styling changes.\n- Features already analyzed and documented.\n\n## Mechanics\n\nAssign the analiz task to **system-architect** and move it to `todo` (investigation is always safe to start — no stakeholder approval needed). The analysis itself returns through the **human analiz_review gate** before any implementation task is created. Never assign analiz to yourself or a developer.\n\n## Worked Example\n\n- \"Change the button label from 'Save' to 'Apply'.\" → No analiz: pure copy change → one frontend task.\n- \"Add real-time notifications.\" → Analiz: transport (WebSocket? SSE? polling?) and the contract are undefined → analiz task to the architect.\n- \"Fix the 500 when deleting a task with subtasks.\" → No analiz: clear repro → one bug task.\n\n## Common Mistakes\n\n- Forcing analiz on a one-line copy change.\n- Skipping analiz on a broad \"add reporting\" request → the dev bounces on undefined scope.\n- Assigning analiz to a developer.\n\n## Red Flags\n\n- An implementation task created for a request whose approach nobody has defined.\n- An analiz task assigned to anyone but the architect.\n",{"name":5,"category":24,"description":7},"pm","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fanaliz-gate",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 analiz-gate",{"tool":40,"command":41},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill analiz-gate",{"tool":43,"command":44},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill analiz-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fproduct-manager\u002Fskills\u002Fanaliz-gate\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",[],[]]