[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P4PBMFRRJRVDCJRF63GGM4":3,"skill-same:01M6P4PBMFRRJRVDCJRF63GGM4":61},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":60},"01M6P4PBMFRRJRVDCJRF63GGM4","epic-implementer",null,"Implement a GitHub Epic, open the pull request, verify its gates and auto-merge it (use the no-merge flag to skip the merge).","maurodesouza\u002Fai-kanban-app-lab","maurodesouza","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54520907?v=4","01M6P3VA3WVQC4XZ0RQWJCDKW6","Mauro de Souza","01M6P3VA7YK770SNWT12GBEGAF",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.claude\u002Fskills\u002Fepic-implementer\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"implementer","EPIC","epic implementer","github","implement","merge","pull request","pull","verify","open","use","auto","gates","it","request","2026-11-10 10:12:30",false,"---\nname: epic-implementer\ndescription: Implement a GitHub Epic, open the pull request, verify its gates and auto-merge it (use the no-merge flag to skip the merge).\n---\n\n# User Input\n\n```text\n$ARGUMENTS\n```\n\nThe input must contain a GitHub Epic.\n\n# Flags\n\n* `no-merge` (also accepted: `--no-merge`, `no merge`): create the pull request and verify all gates, but do not merge.\n\nWithout the flag, the pull request is merged automatically once every gate passes.\n\n# Objective\n\nAct as an autonomous Epic Implementer.\n\nYour responsibility is to implement the complete Epic from start to finish, open the pull request, verify its gates and merge it (unless `no-merge` is set).\n\nThe Epic is the primary unit of execution.\n\nIndividual Issues are implementation work items, not human approval checkpoints.\n\nDo not stop after completing an individual Issue.\n\n# How This Skill Works\n\nThis skill is an orchestrator. It does not do the work itself.\n\nEach step is delegated to a micro-skill with a single responsibility. Call the micro-skill, use its output as input for the next step, and follow its result.\n\nDo not re-implement inside this skill what a micro-skill is responsible for.\n\nShared skills (`command-bus-architecture`, `fragiola-ui`, `command-handle-implementation`, `utils-implementation`, `test-writer`, `reviewer`) are loaded once. While their instructions are still in context, follow them without loading them again for every Issue.\n\n# Autonomy\n\nWork as if the user is not watching.\n\n* When a problem can be solved within the Epic scope and the architecture (failing import, type error, missing config, lint issue, small adaptation of reference code), decide, fix it and continue. Note the decision in the pull request Notes.\n* Ask the user only for the stop conditions in section 9. Everything else is decided by the agent.\n* `clarify-first` does not apply inside this skill; requirements were clarified when the Epic was planned.\n\n# Architecture\n\nAll code produced for the Epic must follow `command-bus-architecture`:\n\n* Everything is an event through the Command Bus (V2).\n* MobX stores hold all state and all derived values (`computed`, always prefixed with `$`).\n* Handles hold all execution logic.\n* Components only read prepared `$` values, present them and dispatch actions. No calculation or derived logic in components.\n* Every interface is built with Fragiola UI (`fragiola-ui`).\n\n# 1. Read the Epic\n\nCall `epic-read` with the Epic.\n\nIf it returns `BLOCKED`, stop and present the reason to the user (open questions or an Epic it depends on that is not merged).\n\n# 2. Discover the Repository\n\nCall `epic-discover-repository`.\n\n# 3. Repository Rules\n\nCall `epic-repository-rules`.\n\nRepository rules always override workflow defaults.\n\n# 4. Current Documentation\n\nCall `epic-current-documentation` whenever any step is about to use, install, upgrade, configure or integrate an external tool or dependency.\n\n# 5. Plan Execution\n\nCall `epic-plan-execution` with the outputs of steps 1-3.\n\n`epic-plan-execution` uses `epic-handle-dependent-work` to order the Issues.\n\n# 6. Epic Worktree\n\nCall `epic-worktree`.\n\nAll following steps run inside the Epic worktree.\n\n# 7. Prerequisites\n\nIf the plan lists prerequisites:\n\n* Command Bus not installed: call `setup-command-system`.\n* MobX not installed: install it using the version verified by `epic-current-documentation`.\n* Fragiola UI not set up: configure the `@fragiola` registry with `fragiola-ui`.\n\nThen call `epic-commit-progressively`.\n\n# 8. Execute the Epic\n\nFor each Issue, in the order returned by the plan, call `epic-execution`.\n\n`epic-execution` implements, tests (`test-writer`), reviews (`reviewer`) and commits (`epic-commit-progressively`) one Issue.\n\nContinue automatically to the next Issue.\n\nDo NOT wait for human approval between Issues.\n\nDo NOT open a pull request for individual Issues.\n\nDo NOT stop merely because an Issue is complete.\n\nIf the work reveals a new dependency between Issues, call `epic-handle-dependent-work` again and continue with the updated order.\n\n# 9. Stop Conditions\n\nContinue autonomously unless one of the following occurs:\n\n* Requirements are fundamentally ambiguous.\n* The Epic scope must materially change.\n* A significant architectural decision not covered by the Epic or by `command-bus-architecture` is required.\n* A destructive migration is required.\n* Security boundaries must change.\n* A new external dependency or service is required (the Command Bus, MobX and Fragiola UI are pre-approved).\n* Significant infrastructure changes are required.\n* Data loss is possible.\n* Validation repeatedly fails without a clear resolution.\n* The implementation contradicts the Epic objectives.\n\nWhen a stop condition occurs, stop and clearly explain the decision required from the user.\n\nDo not stop for minor implementation decisions that can be safely resolved within the existing scope.\n\n# 10. Final Validation\n\nAfter all Issues are implemented:\n\n1. Verify every Epic acceptance criterion.\n2. Verify every Issue acceptance criterion.\n3. Run the complete relevant test suite.\n4. Run lint.\n5. Run type checking when applicable.\n6. Run build when applicable.\n7. Call `reviewer` for final Epic-level review.\n8. Address all blocking findings.\n9. Confirm the repository is merge-ready.\n\nDo not open the pull request until the Epic passes final validation.\n\n# 11. Open Pull Request\n\nCall `epic-pull-request`.\n\n# 12. Gates and Merge\n\nCall `epic-merge` with the pull request and the `no-merge` flag.\n\n* Default: verify all gates (checks, conflicts, mergeability) and merge when everything passes.\n* `no-merge`: verify all gates the same way, but do not merge.\n\nIf `epic-merge` returns `BLOCKED` or `WAITING_FOR_HUMAN`, stop and explain what is required from the user.\n\n# 13. Cleanup\n\nWhen `epic-merge` returns `MERGED`, call `epic-cleanup` to delete the remote branch, the local branch and the Epic worktree.\n\nWith `no-merge`, skip this step: the branch and worktree stay for the pending pull request.\n\n# 14. Final Output\n\nReturn:\n\n* Epic number\n* Issues implemented\n* Worktree path\n* Branch name\n* Commits created\n* Pull request URL\n* Gates status (checks, conflicts)\n* Merge status: `MERGED`, `READY_TO_MERGE` (no-merge), `WAITING_FOR_HUMAN` or `BLOCKED`\n* Cleanup status: `CLEANED`, `SKIPPED` or `BLOCKED`\n* Final validation status\n\nStop after the cleanup, or after the gates pass when `no-merge` is set. When invoked by `tech-lead`, return this output to it so it can continue with the next Epic.\n","# User Input\n\n```text\n$ARGUMENTS\n```\n\nThe input must contain a GitHub Epic.\n\n# Flags\n\n* `no-merge` (also accepted: `--no-merge`, `no merge`): create the pull request and verify all gates, but do not merge.\n\nWithout the flag, the pull request is merged automatically once every gate passes.\n\n# Objective\n\nAct as an autonomous Epic Implementer.\n\nYour responsibility is to implement the complete Epic from start to finish, open the pull request, verify its gates and merge it (unless `no-merge` is set).\n\nThe Epic is the primary unit of execution.\n\nIndividual Issues are implementation work items, not human approval checkpoints.\n\nDo not stop after completing an individual Issue.\n\n# How This Skill Works\n\nThis skill is an orchestrator. It does not do the work itself.\n\nEach step is delegated to a micro-skill with a single responsibility. Call the micro-skill, use its output as input for the next step, and follow its result.\n\nDo not re-implement inside this skill what a micro-skill is responsible for.\n\nShared skills (`command-bus-architecture`, `fragiola-ui`, `command-handle-implementation`, `utils-implementation`, `test-writer`, `reviewer`) are loaded once. While their instructions are still in context, follow them without loading them again for every Issue.\n\n# Autonomy\n\nWork as if the user is not watching.\n\n* When a problem can be solved within the Epic scope and the architecture (failing import, type error, missing config, lint issue, small adaptation of reference code), decide, fix it and continue. Note the decision in the pull request Notes.\n* Ask the user only for the stop conditions in section 9. Everything else is decided by the agent.\n* `clarify-first` does not apply inside this skill; requirements were clarified when the Epic was planned.\n\n# Architecture\n\nAll code produced for the Epic must follow `command-bus-architecture`:\n\n* Everything is an event through the Command Bus (V2).\n* MobX stores hold all state and all derived values (`computed`, always prefixed with `$`).\n* Handles hold all execution logic.\n* Components only read prepared `$` values, present them and dispatch actions. No calculation or derived logic in components.\n* Every interface is built with Fragiola UI (`fragiola-ui`).\n\n# 1. Read the Epic\n\nCall `epic-read` with the Epic.\n\nIf it returns `BLOCKED`, stop and present the reason to the user (open questions or an Epic it depends on that is not merged).\n\n# 2. Discover the Repository\n\nCall `epic-discover-repository`.\n\n# 3. Repository Rules\n\nCall `epic-repository-rules`.\n\nRepository rules always override workflow defaults.\n\n# 4. Current Documentation\n\nCall `epic-current-documentation` whenever any step is about to use, install, upgrade, configure or integrate an external tool or dependency.\n\n# 5. Plan Execution\n\nCall `epic-plan-execution` with the outputs of steps 1-3.\n\n`epic-plan-execution` uses `epic-handle-dependent-work` to order the Issues.\n\n# 6. Epic Worktree\n\nCall `epic-worktree`.\n\nAll following steps run inside the Epic worktree.\n\n# 7. Prerequisites\n\nIf the plan lists prerequisites:\n\n* Command Bus not installed: call `setup-command-system`.\n* MobX not installed: install it using the version verified by `epic-current-documentation`.\n* Fragiola UI not set up: configure the `@fragiola` registry with `fragiola-ui`.\n\nThen call `epic-commit-progressively`.\n\n# 8. Execute the Epic\n\nFor each Issue, in the order returned by the plan, call `epic-execution`.\n\n`epic-execution` implements, tests (`test-writer`), reviews (`reviewer`) and commits (`epic-commit-progressively`) one Issue.\n\nContinue automatically to the next Issue.\n\nDo NOT wait for human approval between Issues.\n\nDo NOT open a pull request for individual Issues.\n\nDo NOT stop merely because an Issue is complete.\n\nIf the work reveals a new dependency between Issues, call `epic-handle-dependent-work` again and continue with the updated order.\n\n# 9. Stop Conditions\n\nContinue autonomously unless one of the following occurs:\n\n* Requirements are fundamentally ambiguous.\n* The Epic scope must materially change.\n* A significant architectural decision not covered by the Epic or by `command-bus-architecture` is required.\n* A destructive migration is required.\n* Security boundaries must change.\n* A new external dependency or service is required (the Command Bus, MobX and Fragiola UI are pre-approved).\n* Significant infrastructure changes are required.\n* Data loss is possible.\n* Validation repeatedly fails without a clear resolution.\n* The implementation contradicts the Epic objectives.\n\nWhen a stop condition occurs, stop and clearly explain the decision required from the user.\n\nDo not stop for minor implementation decisions that can be safely resolved within the existing scope.\n\n# 10. Final Validation\n\nAfter all Issues are implemented:\n\n1. Verify every Epic acceptance criterion.\n2. Verify every Issue acceptance criterion.\n3. Run the complete relevant test suite.\n4. Run lint.\n5. Run type checking when applicable.\n6. Run build when applicable.\n7. Call `reviewer` for final Epic-level review.\n8. Address all blocking findings.\n9. Confirm the repository is merge-ready.\n\nDo not open the pull request until the Epic passes final validation.\n\n# 11. Open Pull Request\n\nCall `epic-pull-request`.\n\n# 12. Gates and Merge\n\nCall `epic-merge` with the pull request and the `no-merge` flag.\n\n* Default: verify all gates (checks, conflicts, mergeability) and merge when everything passes.\n* `no-merge`: verify all gates the same way, but do not merge.\n\nIf `epic-merge` returns `BLOCKED` or `WAITING_FOR_HUMAN`, stop and explain what is required from the user.\n\n# 13. Cleanup\n\nWhen `epic-merge` returns `MERGED`, call `epic-cleanup` to delete the remote branch, the local branch and the Epic worktree.\n\nWith `no-merge`, skip this step: the branch and worktree stay for the pending pull request.\n\n# 14. Final Output\n\nReturn:\n\n* Epic number\n* Issues implemented\n* Worktree path\n* Branch name\n* Commits created\n* Pull request URL\n* Gates status (checks, conflicts)\n* Merge status: `MERGED`, `READY_TO_MERGE` (no-merge), `WAITING_FOR_HUMAN` or `BLOCKED`\n* Cleanup status: `CLEANED`, `SKIPPED` or `BLOCKED`\n* Final validation status\n\nStop after the cleanup, or after the gates pass when `no-merge` is set. When invoked by `tech-lead`, return this output to it so it can continue with the next Epic.\n",{"name":5,"description":7},"main","6f1867f215cf86d20099b6dfb1164c79abfb87ce","lab-10\u002F.claude\u002Fskills\u002Fepic-implementer",0,"https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab","https:\u002F\u002Fgithub.com\u002Fmaurodesouza","Software Engineer","2026-10-28 02:01:00",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add maurodesouza\u002Fai-kanban-app-lab --skill epic-implementer",{"tool":53,"command":54},"bunx","bunx skills add maurodesouza\u002Fai-kanban-app-lab --skill epic-implementer",{"tool":56,"command":57},"pnpm","pnpm dlx skills add maurodesouza\u002Fai-kanban-app-lab --skill epic-implementer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.claude\u002Fskills\u002Fepic-implementer\u002FSKILL.md",true,[],[62,87,104,126,138,149],{"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":34},"01M6P519M13JTBZDK3ZJP48P2C","utils-implementation","Write and organize utils (pure helpers for formatting, mapping, filtering, math, parsing, ids, storage) as one namespace object per domain with clear, readable names. Use before creating or changing any util.","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Futils-implementation\u002FSKILL.md",[],[69,70,71,72,73,74,75,76,77,78,79,80,81,29,82,83,84,85,86],"utils implementation","implementation","utils","parsing","for","object","storage","ids","clear","math","write","filtering","with","organize","domain","mapping","formatting","as",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":98,"publishedAt":34},"01M6P516BP8GPRJHPGVFWRF5T8","test-writer","Write tests for the current implementation","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Ftest-writer\u002FSKILL.md",[93],{"categoryNo":94,"categoryName":95,"taxonomyType":96,"taxonomyTypeDesc":97},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[99,100,101,102,79,70,103,73],"test","test writer","writer","write tests","tests",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":34},"01M6P50M0Z2AQH32ZTV90D5V32","tech-lead","Analyze a project, turn the user's goal into an implementation-ready GitHub Epic and Issues (following project rules, the Command Bus architecture and Fragiola UI), then start epic-implementer automatically (use the no-implement flag to stop after planning).","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Ftech-lead\u002FSKILL.md",[],[111,112,113,114,23,22,20,115,116,117,118,119,120,121,122,19,29,123,124,125],"tech","tech lead","ready","command bus architecture","architecture","planning","issues","ui","start","analyze","Rules","command","goal","stop","project",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":34},"01M6P50GND99S9QQY6KWPP6NW9","tech-lead-publish","Publish a final Epic and its Issues to GitHub, linked and labeled, keeping dependency and execution information. Sub-skill of tech-lead.","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Ftech-lead-publish\u002FSKILL.md",[],[133,112,111,134,22,117,135,136,20,137],"tech lead publish","publish","execution","dependency","information",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":34},"01M6P50D4P2SQSYZM7TZMHZA0J","setup-command-system","Install the Command System architecture in the project","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Fsetup-command-system\u002FSKILL.md",[],[145,122,146,147,115,148,125],"setup command system","system","setup","install",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":34},"01M6P50A032630X9JDDZYJMNV3","reviewer","Review code changes and provide feedback","https:\u002F\u002Fgithub.com\u002Fmaurodesouza\u002Fai-kanban-app-lab\u002Fblob\u002Fmain\u002Flab-10\u002F.codex\u002Fskills\u002Freviewer\u002FSKILL.md",[],[151,156,157,158,159,160],"code","review code","feedback","changes","review"]