[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSRH25K3JNNYY92MXYDY41":3,"skill-same:01M7CSRH25K3JNNYY92MXYDY41":49},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSRH25K3JNNYY92MXYDY41","analiz-human-review-gate",null,"Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column","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\u002Fsystem-architect\u002Fskills\u002Fanaliz-human-review-gate\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analiz-human-review-gate\ncategory: architecture\ndescription: Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column\nsource: obra\u002Fsuperpowers (MIT), adapted\n---\n# Analiz Human Review Gate\n\n## Overview\n\nYour analysis output — the ONE analysis report, with the spec and the implementation plan as its sections — is not self-approved. A human reviews it BEFORE any implementation task exists. This is the only human gate in the system: the human does not review individual dev tasks, but they DO review your plan, because a wrong plan multiplies into wrong tasks across every project.\n\nThe human reviews the report passage by passage: they select text in it, comment on it, and send all their comments back at once. Each comment is anchored to the words it is about, so it is precise — and every one of them needs an answer.\n\n**Core principle:** No implementation task is created from an unapproved plan. You stop, the task waits at `analiz_review`, and you create nothing until the human approves.\n\n**This reverses the old flow.** You no longer create tasks and then close the analiz. You present the plan, wait for approval, and only THEN create tasks.\n\n## The Gate\n\n```dot\ndigraph gate {\n    \"Report written\\n& self-reviewed\" [shape=box];\n    \"Summary comment, STOP\\n(system moves -> analiz_review)\" [shape=box];\n    \"Human decision\" [shape=diamond];\n    \"Human moves -> done\\n(approved)\" [shape=box];\n    \"Human sends comments\\n-> need_revision (rejected)\" [shape=box];\n    \"Create per-project impl tasks\\n+ list them\" [shape=box];\n    \"Move analiz -> released\" [shape=doublecircle];\n    \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\" [shape=box];\n\n    \"Report written\\n& self-reviewed\" -> \"Summary comment, STOP\\n(system moves -> analiz_review)\";\n    \"Summary comment, STOP\\n(system moves -> analiz_review)\" -> \"Human decision\";\n    \"Human decision\" -> \"Human moves -> done\\n(approved)\" [label=\"approve\"];\n    \"Human decision\" -> \"Human sends comments\\n-> need_revision (rejected)\" [label=\"request changes\"];\n    \"Human moves -> done\\n(approved)\" -> \"Create per-project impl tasks\\n+ list them\";\n    \"Create per-project impl tasks\\n+ list them\" -> \"Move analiz -> released\";\n    \"Human sends comments\\n-> need_revision (rejected)\" -> \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\";\n    \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\" -> \"Human decision\";\n}\n```\n\n## Step 1 — Present for review (do NOT create tasks yet)\n\nWhen the report is written, self-reviewed, and attached via add_task_document (`format: \"html\"`, analiz-html-report):\n\n1. `add_task_comment` — a review-ready summary for the human:\n   - One-paragraph approach (what will be built and why this approach).\n   - The title of the report you attached (`analiz: …`).\n   - **The project\u002Ftask split you INTEND to create** on approval — list each project and the one-line scope of its task (see project-split-decomposition). This is what the human is approving.\n   - Any product decision you need confirmed.\n2. **STOP.** Your run ends here. When a run ends with the report attached, the system moves the analiz task to **analiz_review** for you — do not move it yourself. Create nothing. Do not touch implementation tasks.\n\n## Step 2 — Handle the human's decision\n\nYou are re-dispatched (as the analiz task's assignee) when the human decides. The task's current column tells you which path:\n\n**Column is `done` → APPROVED.**\n1. Check for answered open questions first (`list_open_questions` if the context block doesn't already show them). An unanswered non-blocking question means its `recommended_answer` stands. If a human's answer contradicts the approved split or plan in a way this decomposition cannot absorb, do NOT decompose — `add_task_comment` naming the conflict and stop (open-questions-protocol).\n2. Now create the per-project implementation tasks (project-split-decomposition + task-decomposition).\n3. Every one of them carries `derived_from: [\"\u003Cthis analiz task's key>\"]`. Your report — spec and plan — is a document on THIS task and exists nowhere else — the reference is what puts it in front of the developer and what makes `list_task_documents` able to return it. A task without it is a task whose specification cannot be found.\n4. Every ordering between them goes in `blocked_by` (who codes first) and `deploy_depends_on` (who ships first), not in the description.\n5. `add_task_comment` listing every created task: title, assignee, project, and its order.\n6. `move_board_task` the analiz task to **released**. You are finished.\n\n**The run is a revision (the task came back through `need_revision`) → REJECTED.**\n1. Read EVERY review comment. They are in your run context under \"Review comments on your analysis document\" — each with its id, the quoted passage and the human's comment. If that list says some were left out, or you are unsure you have them all, `list_document_annotations` with status `submitted` returns every one. Also read the task comments: the review's covering note is there.\n2. Read the report's source: `list_task_documents` on this task with the report's `document_id` and `raw: true`; follow `next_offset` until you have all of it.\n3. Fix each comment at the root of the concern (see root-cause-review reasoning — fix the cause, not the wording). Where a comment questions a fact about the code, re-read the code before you answer it.\n4. Honour every answered open question the same way (`list_open_questions` if you need the full list): fold the answer into the report and withdraw or replace any question it made moot. An unanswered non-blocking question means its `recommended_answer` stands — do not re-ask it (open-questions-protocol).\n5. Revise the SAME report with `update_task_document` on its `document_id` — `edits` (each `old_text` copied exactly from the source) for targeted passages, `content` for a rewrite. Keep its sections and ids, and keep its TITLE unchanged (a new date creates a second document instead of revising this one). Never attach a second document. Leave `split` as the human approved unless a comment or a code re-read gives you a concrete reason to change it.\n6. Re-run the design and plan self-reviews on the revised report.\n7. `resolve_document_annotations` ONCE, with `{id, reply}` for every comment you were sent: the reply is one line saying what changed and where (\"Replaced the queue with a cron job — see #design and #step-2\"), or why you deliberately kept it.\n8. `add_task_comment` with a short summary of what changed. Then STOP: when the run ends with the report revised, the system moves the task back to **analiz_review** — do not move it yourself.\n9. **Create no implementation tasks.** A rejected analysis never spawns work.\n\n## Common Mistakes\n\n- Creating implementation tasks before approval — the whole point of the gate is that tasks come AFTER the human says yes.\n- Moving the analiz task yourself to `analiz_review`, `done` or `need_revision` — the system moves it to `analiz_review`, and `done` \u002F `need_revision` are the human's decisions. You move it only to `released`, after approval.\n- Answering some review comments and not others — every submitted comment gets a fix (or a reasoned \"kept\") and a reply.\n- Resolving a comment without changing the report — the reply is a record of the fix, not a substitute for it.\n- Attaching a revised report next to the old one — revise in place with `update_task_document`.\n- On rejection, tweaking wording instead of addressing the concern — the human will reject again.\n- Forgetting to list the intended project\u002Ftask split in the review comment — the human is approving the split, so show it.\n- Decomposing while a human's answer to an open question still contradicts the approved split — resolve the conflict with the human first (open-questions-protocol).\n\n## Red Flags — STOP\n\n- You are about to call create_board_task and the analiz task is still in `analiz_review` → you are creating tasks before approval.\n- You created implementation tasks without `derived_from` → they point at no analysis, and the report you spent the run writing is unreachable from the work it specifies.\n- You are about to call `move_board_task` to `analiz_review` or `done` → that is the system's move or the human's, not yours.\n- You are about to call `add_task_document` during a revision → revise the existing report with `update_task_document` instead.\n- A revision came back and you are editing task titles instead of the report → you are patching symptoms.\n","# Analiz Human Review Gate\n\n## Overview\n\nYour analysis output — the ONE analysis report, with the spec and the implementation plan as its sections — is not self-approved. A human reviews it BEFORE any implementation task exists. This is the only human gate in the system: the human does not review individual dev tasks, but they DO review your plan, because a wrong plan multiplies into wrong tasks across every project.\n\nThe human reviews the report passage by passage: they select text in it, comment on it, and send all their comments back at once. Each comment is anchored to the words it is about, so it is precise — and every one of them needs an answer.\n\n**Core principle:** No implementation task is created from an unapproved plan. You stop, the task waits at `analiz_review`, and you create nothing until the human approves.\n\n**This reverses the old flow.** You no longer create tasks and then close the analiz. You present the plan, wait for approval, and only THEN create tasks.\n\n## The Gate\n\n```dot\ndigraph gate {\n    \"Report written\\n& self-reviewed\" [shape=box];\n    \"Summary comment, STOP\\n(system moves -> analiz_review)\" [shape=box];\n    \"Human decision\" [shape=diamond];\n    \"Human moves -> done\\n(approved)\" [shape=box];\n    \"Human sends comments\\n-> need_revision (rejected)\" [shape=box];\n    \"Create per-project impl tasks\\n+ list them\" [shape=box];\n    \"Move analiz -> released\" [shape=doublecircle];\n    \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\" [shape=box];\n\n    \"Report written\\n& self-reviewed\" -> \"Summary comment, STOP\\n(system moves -> analiz_review)\";\n    \"Summary comment, STOP\\n(system moves -> analiz_review)\" -> \"Human decision\";\n    \"Human decision\" -> \"Human moves -> done\\n(approved)\" [label=\"approve\"];\n    \"Human decision\" -> \"Human sends comments\\n-> need_revision (rejected)\" [label=\"request changes\"];\n    \"Human moves -> done\\n(approved)\" -> \"Create per-project impl tasks\\n+ list them\";\n    \"Create per-project impl tasks\\n+ list them\" -> \"Move analiz -> released\";\n    \"Human sends comments\\n-> need_revision (rejected)\" -> \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\";\n    \"Fix every comment at root\\nin the SAME report, resolve each\\n(system moves -> analiz_review)\" -> \"Human decision\";\n}\n```\n\n## Step 1 — Present for review (do NOT create tasks yet)\n\nWhen the report is written, self-reviewed, and attached via add_task_document (`format: \"html\"`, analiz-html-report):\n\n1. `add_task_comment` — a review-ready summary for the human:\n   - One-paragraph approach (what will be built and why this approach).\n   - The title of the report you attached (`analiz: …`).\n   - **The project\u002Ftask split you INTEND to create** on approval — list each project and the one-line scope of its task (see project-split-decomposition). This is what the human is approving.\n   - Any product decision you need confirmed.\n2. **STOP.** Your run ends here. When a run ends with the report attached, the system moves the analiz task to **analiz_review** for you — do not move it yourself. Create nothing. Do not touch implementation tasks.\n\n## Step 2 — Handle the human's decision\n\nYou are re-dispatched (as the analiz task's assignee) when the human decides. The task's current column tells you which path:\n\n**Column is `done` → APPROVED.**\n1. Check for answered open questions first (`list_open_questions` if the context block doesn't already show them). An unanswered non-blocking question means its `recommended_answer` stands. If a human's answer contradicts the approved split or plan in a way this decomposition cannot absorb, do NOT decompose — `add_task_comment` naming the conflict and stop (open-questions-protocol).\n2. Now create the per-project implementation tasks (project-split-decomposition + task-decomposition).\n3. Every one of them carries `derived_from: [\"\u003Cthis analiz task's key>\"]`. Your report — spec and plan — is a document on THIS task and exists nowhere else — the reference is what puts it in front of the developer and what makes `list_task_documents` able to return it. A task without it is a task whose specification cannot be found.\n4. Every ordering between them goes in `blocked_by` (who codes first) and `deploy_depends_on` (who ships first), not in the description.\n5. `add_task_comment` listing every created task: title, assignee, project, and its order.\n6. `move_board_task` the analiz task to **released**. You are finished.\n\n**The run is a revision (the task came back through `need_revision`) → REJECTED.**\n1. Read EVERY review comment. They are in your run context under \"Review comments on your analysis document\" — each with its id, the quoted passage and the human's comment. If that list says some were left out, or you are unsure you have them all, `list_document_annotations` with status `submitted` returns every one. Also read the task comments: the review's covering note is there.\n2. Read the report's source: `list_task_documents` on this task with the report's `document_id` and `raw: true`; follow `next_offset` until you have all of it.\n3. Fix each comment at the root of the concern (see root-cause-review reasoning — fix the cause, not the wording). Where a comment questions a fact about the code, re-read the code before you answer it.\n4. Honour every answered open question the same way (`list_open_questions` if you need the full list): fold the answer into the report and withdraw or replace any question it made moot. An unanswered non-blocking question means its `recommended_answer` stands — do not re-ask it (open-questions-protocol).\n5. Revise the SAME report with `update_task_document` on its `document_id` — `edits` (each `old_text` copied exactly from the source) for targeted passages, `content` for a rewrite. Keep its sections and ids, and keep its TITLE unchanged (a new date creates a second document instead of revising this one). Never attach a second document. Leave `split` as the human approved unless a comment or a code re-read gives you a concrete reason to change it.\n6. Re-run the design and plan self-reviews on the revised report.\n7. `resolve_document_annotations` ONCE, with `{id, reply}` for every comment you were sent: the reply is one line saying what changed and where (\"Replaced the queue with a cron job — see #design and #step-2\"), or why you deliberately kept it.\n8. `add_task_comment` with a short summary of what changed. Then STOP: when the run ends with the report revised, the system moves the task back to **analiz_review** — do not move it yourself.\n9. **Create no implementation tasks.** A rejected analysis never spawns work.\n\n## Common Mistakes\n\n- Creating implementation tasks before approval — the whole point of the gate is that tasks come AFTER the human says yes.\n- Moving the analiz task yourself to `analiz_review`, `done` or `need_revision` — the system moves it to `analiz_review`, and `done` \u002F `need_revision` are the human's decisions. You move it only to `released`, after approval.\n- Answering some review comments and not others — every submitted comment gets a fix (or a reasoned \"kept\") and a reply.\n- Resolving a comment without changing the report — the reply is a record of the fix, not a substitute for it.\n- Attaching a revised report next to the old one — revise in place with `update_task_document`.\n- On rejection, tweaking wording instead of addressing the concern — the human will reject again.\n- Forgetting to list the intended project\u002Ftask split in the review comment — the human is approving the split, so show it.\n- Decomposing while a human's answer to an open question still contradicts the approved split — resolve the conflict with the human first (open-questions-protocol).\n\n## Red Flags — STOP\n\n- You are about to call create_board_task and the analiz task is still in `analiz_review` → you are creating tasks before approval.\n- You created implementation tasks without `derived_from` → they point at no analysis, and the report you spent the run writing is unreachable from the work it specifies.\n- You are about to call `move_board_task` to `analiz_review` or `done` → that is the system's move or the human's, not yours.\n- You are about to call `add_task_document` during a revision → revise the existing report with `update_task_document` instead.\n- A revision came back and you are editing task titles instead of the report → you are patching symptoms.\n",{"name":5,"source":24,"category":25,"description":7},"obra\u002Fsuperpowers (MIT), adapted","architecture","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Fsystem-architect\u002Fskills\u002Fanaliz-human-review-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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill analiz-human-review-gate",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill analiz-human-review-gate",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill analiz-human-review-gate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fsystem-architect\u002Fskills\u002Fanaliz-human-review-gate\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"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":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]