[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M737M35TX9WJSBK7JWSGHZES":3,"skill-same:01M737M35TX9WJSBK7JWSGHZES":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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M737M35TX9WJSBK7JWSGHZES","closed-loop-delivery",null,"Use when a coding task must be completed against explicit acceptance criteria with minimal user re-intervention across implementation, review feedback, deployment, and runtime verification.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fclosed-loop-delivery\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: closed-loop-delivery\ndescription: Use when a coding task must be completed against explicit acceptance criteria with minimal user re-intervention across implementation, review feedback, deployment, and runtime verification.\nrisk: safe\nsource: community\ndate_added: \"2026-03-12\"\n---\n\n# Closed-Loop Delivery\n\n## Overview\n\nTreat each task as incomplete until acceptance criteria are verified in evidence, not until code is merely changed.\n\nCore rule: **deliver against DoD (Definition of Done), not against code diff size.**\n\n## When to Use\n\nUse this skill when:\n- user gives a coding\u002Ffix task and expects end-to-end completion\n- task spans code + tests + PR comments + dev deploy + runtime checks\n- repeated manual prompts like \"now test\", \"now deploy\", \"now re-check PR\" should be avoided\n\nDo not use this skill for:\n- pure Q&A\u002Fexplanations\n- prod deploy requests without explicit human approval\n- tasks blocked by missing secrets\u002Faccount access that cannot be inferred\n\n## Required Inputs\n\nBefore execution, define these once:\n- task goal\n- acceptance criteria (DoD)\n- target environment (`dev` by default)\n- max iteration rounds (default `2`)\n\nIf acceptance criteria are missing, request them once. If user does not provide, propose a concrete default and proceed.\n\n## Issue Gate Dependency\n\nBefore execution, prefer using `create-issue-gate`.\n\n- If issue status is `ready` and execution gate is `allowed`, continue.\n- If issue status is `draft`, do not execute implementation\u002Fdeploy\u002Freview loops.\n- Require user-provided, testable acceptance criteria before starting execution.\n\n## Default Workflow\n\n1. **Define DoD**\n   - Convert request into testable criteria.\n   - Example: checkout task DoD = \"checkout endpoint returns a valid, openable third-party payment URL in dev\".\n\n2. **Implement minimal change**\n   - Keep scope tight to task goal.\n\n3. **Verify locally**\n   - Run focused tests first, then broader checks if needed.\n\n4. **Review loop**\n   - Fetch PR comments\u002Freviews.\n   - Classify valid vs non-actionable.\n   - Fix valid items, re-run verification.\n\n5. **Dev deploy + runtime verification**\n   - Deploy to `dev` when runtime behavior matters.\n   - Verify via real API\u002FLambda\u002Flog evidence against DoD.\n\n6. **Completion decision**\n   - Only report \"done\" when all DoD checks pass.\n   - Otherwise continue loop until pass or stop condition.\n\n## PR Comment Polling Policy\n\nAvoid noisy short polling by default. Use batched windows:\n\n- **Round 1:** wait `3m`, collect delta comments\u002Freviews\n- **Round 2:** wait `6m`, collect delta again\n- **Final round:** wait `10m`, collect all remaining visible comments\u002Freviews\n\nAt each round:\n- process all new comments in one batch\n- avoid immediate re-poll after each single comment\n- after the `10m` round, stop waiting and proceed with all comments visible at that point\n\nIf CI is still running, align polling to check completion boundaries instead of fixed rapid polling.\n\n## Human Gate Rules (Must Ask)\n\nRequire explicit user confirmation for:\n- production\u002Fstaging deploy beyond agreed scope\n- destructive operations (history rewrite, force push, data-destructive ops)\n- actions with billing\u002Fsecurity posture changes\n- secret values not available in repo\u002Fruntime\n- ambiguous DoD that materially changes outcome\n\n## Iteration\u002FStop Conditions\n\nStop and escalate with a concise blocker report when:\n- DoD still fails after max rounds (`2` default)\n- external dependency blocks progress (provider outage, missing creds, account permission)\n- conflicting review instructions cannot both be satisfied\n\nEscalation report must include:\n- what passed\n- what failed\n- evidence (commands\u002Flogs\u002FAPI result)\n- smallest decision needed from user\n\n## Output Contract\n\nWhen claiming completion, always include:\n- acceptance criteria checklist with pass\u002Ffail\n- commands\u002Ftests run\n- runtime evidence (endpoint\u002FLambda\u002Flog key lines)\n- PR status (new actionable comments count)\n\nDo not claim success without evidence.\n","# Closed-Loop Delivery\n\n## Overview\n\nTreat each task as incomplete until acceptance criteria are verified in evidence, not until code is merely changed.\n\nCore rule: **deliver against DoD (Definition of Done), not against code diff size.**\n\n## When to Use\n\nUse this skill when:\n- user gives a coding\u002Ffix task and expects end-to-end completion\n- task spans code + tests + PR comments + dev deploy + runtime checks\n- repeated manual prompts like \"now test\", \"now deploy\", \"now re-check PR\" should be avoided\n\nDo not use this skill for:\n- pure Q&A\u002Fexplanations\n- prod deploy requests without explicit human approval\n- tasks blocked by missing secrets\u002Faccount access that cannot be inferred\n\n## Required Inputs\n\nBefore execution, define these once:\n- task goal\n- acceptance criteria (DoD)\n- target environment (`dev` by default)\n- max iteration rounds (default `2`)\n\nIf acceptance criteria are missing, request them once. If user does not provide, propose a concrete default and proceed.\n\n## Issue Gate Dependency\n\nBefore execution, prefer using `create-issue-gate`.\n\n- If issue status is `ready` and execution gate is `allowed`, continue.\n- If issue status is `draft`, do not execute implementation\u002Fdeploy\u002Freview loops.\n- Require user-provided, testable acceptance criteria before starting execution.\n\n## Default Workflow\n\n1. **Define DoD**\n   - Convert request into testable criteria.\n   - Example: checkout task DoD = \"checkout endpoint returns a valid, openable third-party payment URL in dev\".\n\n2. **Implement minimal change**\n   - Keep scope tight to task goal.\n\n3. **Verify locally**\n   - Run focused tests first, then broader checks if needed.\n\n4. **Review loop**\n   - Fetch PR comments\u002Freviews.\n   - Classify valid vs non-actionable.\n   - Fix valid items, re-run verification.\n\n5. **Dev deploy + runtime verification**\n   - Deploy to `dev` when runtime behavior matters.\n   - Verify via real API\u002FLambda\u002Flog evidence against DoD.\n\n6. **Completion decision**\n   - Only report \"done\" when all DoD checks pass.\n   - Otherwise continue loop until pass or stop condition.\n\n## PR Comment Polling Policy\n\nAvoid noisy short polling by default. Use batched windows:\n\n- **Round 1:** wait `3m`, collect delta comments\u002Freviews\n- **Round 2:** wait `6m`, collect delta again\n- **Final round:** wait `10m`, collect all remaining visible comments\u002Freviews\n\nAt each round:\n- process all new comments in one batch\n- avoid immediate re-poll after each single comment\n- after the `10m` round, stop waiting and proceed with all comments visible at that point\n\nIf CI is still running, align polling to check completion boundaries instead of fixed rapid polling.\n\n## Human Gate Rules (Must Ask)\n\nRequire explicit user confirmation for:\n- production\u002Fstaging deploy beyond agreed scope\n- destructive operations (history rewrite, force push, data-destructive ops)\n- actions with billing\u002Fsecurity posture changes\n- secret values not available in repo\u002Fruntime\n- ambiguous DoD that materially changes outcome\n\n## Iteration\u002FStop Conditions\n\nStop and escalate with a concise blocker report when:\n- DoD still fails after max rounds (`2` default)\n- external dependency blocks progress (provider outage, missing creds, account permission)\n- conflicting review instructions cannot both be satisfied\n\nEscalation report must include:\n- what passed\n- what failed\n- evidence (commands\u002Flogs\u002FAPI result)\n- smallest decision needed from user\n\n## Output Contract\n\nWhen claiming completion, always include:\n- acceptance criteria checklist with pass\u002Ffail\n- commands\u002Ftests run\n- runtime evidence (endpoint\u002FLambda\u002Flog key lines)\n- PR status (new actionable comments count)\n\nDo not claim success without evidence.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","community","2026-03-12","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fclosed-loop-delivery","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill closed-loop-delivery",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill closed-loop-delivery",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill closed-loop-delivery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fclosed-loop-delivery\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]