[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GSS4W9VQ4633R7MKEHREG3":3,"skill-same:01M6GSS4W9VQ4633R7MKEHREG3":78},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6GSS4W9VQ4633R7MKEHREG3","execplan-implement",null,"ExecPlan implementation workflow. Use when implementing ExecPlans and you are the parent agent. Do not use if you are a subagent being delegated to.","japurcell\u002Fskills","japurcell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10947458?v=4","01M6GSJK1YAG95R6VHF47V30KY","Adam Purcell","01M6GSJK6817NVR5FVDMFFNJ6H",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fexecplan-implement\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"implement","execplan","execplan implement","model","route","when","subagent","you","use","controls","implementing","implementation workflow","dispatch","subagent dispatch","do","with model","with","workflow","implementation","2026-11-10 10:12:30",false,"---\nname: execplan-implement\ndescription: ExecPlan implementation workflow. Use when implementing ExecPlans and you are the parent agent. Do not use if you are a subagent being delegated to.\ncompatibility: Requires subagent dispatch with model controls and effort controls when the route requires explicit effort.\n---\n\nYou have been provided an ExecPlan. This plan should have tasks and milestones associated with it, describing how to implement the plan.\n\nThe goal is the entire plan implemented on a single **integration branch**, with every task and milestone resolved.\n\nThe tasks are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tasks which are ready to be grabbed.\n\n**Subagent management rules:**\n\n- Activate the `subagent-model-router` skill.\n- For every subagent dispatch, use `subagent-model-router` to obtain its final dispatchable route, and apply its model and effort policy through dispatch controls. Stop on a named blocker.\n- Use the router’s model unless the user explicitly names an exact model; do not ask them to choose. Authorization is not model selection. Separately check task authorization, control permissions, and live acceptance of the model and required effort (only under `explicit` policy). Report specific blockers without confusing permission with capability or bypassing router policy.\n- **Implementer subagents** should be run in the background where possible for maximum concurrency.\n- Communication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the plan, tasks, research notes, and previous commits. Don't duplicate information already available via pointers.\n- Delegate integration to one persistent **integration coordinator** subagent. Reuse it across merge waves, progress updates, and final checks. The coordinator should also handle deterministic commits and status checks directly when safe.\n\nEnforce limits for exploration, implementation, review, and fixes. An agent is idle only with no outstanding assignment; dependency waits remain active.\n\nAll commits must follow [commit message guidelines](references\u002Fmessage.md).\n\n## Runtime enforcement\n\n1. **Record each background assignment you dispatch**, including reuse. Before dispatch, set a deadline based on expected effort and complexity. Record the routed model and its exact explicit effort or host-default omission. Track task and agent IDs, start time, extension count (initially zero), and enforcement handle as available.\n2. **Arm enforcement before waiting.** Use a host timeout or parent-owned scheduler bounded by the nearest assignment or checkpoint deadline. Independently time out blocking operations. Recheck deadlines whenever control returns, including after user interruptions.\n3. **At expiry**, request status, completed work, blockers, and updated ETA by a bounded checkpoint deadline. Keep overdue work under a deadline. On timely status, confirm completion, stop the worker, or grant its only ETA-based extension. If extended, record the new deadline, increment the count, and re-arm enforcement. Preserve the count across follow-ups. Stop the worker on a missed checkpoint or expired extension.\n4. **Before transferring ownership**, confirm the worker and its write-producing operations have stopped, then route and dispatch a fresh replacement. If shutdown is unconfirmed, report the blocker and continue independent work. Cancel enforcement on completion.\n\n## Steps\n\n1. Activate the `exec-plans` skill, then read the plan, milestones, and tasks to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tasks - relevant codebase files or external documentation. Brief it with the needed context, acceptance criteria, and known negative cases, using context pointers where those facts are already available. Ensure the exploration subagent can save files - it should save its markdown notes in a directory next to the plan, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. If current branch is `main` or `master`, create a new **integration branch**. Start the **integration coordinator** subagent, instructing it to activate the `exec-plans` skill and reconcile its required plan sections before reporting a checkpoint complete.\n\n4. Use **implementer subagents** to implement each task, each in its own worktree on its own branch. Follow the router’s final dispatchable route and runtime enforcement as specified above. Each implementer subagent:\n   - confirms its worktree is based on the integration branch before starting, and resets onto it if not;\n   - calls the Skill tool with `tdd` to build the task;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, have the same **integration coordinator subagent** merge its work to the integration branch.\n\n6. If this changes the **frontier** of available tasks, kick off more **implementer subagents** to work on the new tasks. This allows for maximum concurrency.\n\n7. Once all tickets are complete, follow the [code review fix cycle](#code-review-fix-cycle).\n\n8. Ensure all tasks and milestones are resolved and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees and their related branches.\n\n## Code review fix cycle\n\nCall the Skill tool with `code-review-biaxis` on the integration branch. Track all issues raised by the code review as new tasks in the ExecPlan **frontier**, then fix them in a single **implementer subagent**. Repeat _code review → fix cycle_ until no issues remain for a maximum of three iterations. Report all unresolved issues.\n\nFor each repeat of the cycle, prefer reusing the code review and implementer subagents from the previous iteration when they match the final dispatchable route: the same model with no original effort override for `host_default`, or the exact model\u002Feffort pair for `explicit`. Otherwise, dispatch a fresh agent.\n\n## Gotchas\n\n- Do not create worktrees anywhere within the main project directory because agents will automatically discover files like `AGENTS.md` causing context window bloat. Recommend creating them in `..\u002F\u003Cproject name>.worktrees`.\n","You have been provided an ExecPlan. This plan should have tasks and milestones associated with it, describing how to implement the plan.\n\nThe goal is the entire plan implemented on a single **integration branch**, with every task and milestone resolved.\n\nThe tasks are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tasks which are ready to be grabbed.\n\n**Subagent management rules:**\n\n- Activate the `subagent-model-router` skill.\n- For every subagent dispatch, use `subagent-model-router` to obtain its final dispatchable route, and apply its model and effort policy through dispatch controls. Stop on a named blocker.\n- Use the router’s model unless the user explicitly names an exact model; do not ask them to choose. Authorization is not model selection. Separately check task authorization, control permissions, and live acceptance of the model and required effort (only under `explicit` policy). Report specific blockers without confusing permission with capability or bypassing router policy.\n- **Implementer subagents** should be run in the background where possible for maximum concurrency.\n- Communication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the plan, tasks, research notes, and previous commits. Don't duplicate information already available via pointers.\n- Delegate integration to one persistent **integration coordinator** subagent. Reuse it across merge waves, progress updates, and final checks. The coordinator should also handle deterministic commits and status checks directly when safe.\n\nEnforce limits for exploration, implementation, review, and fixes. An agent is idle only with no outstanding assignment; dependency waits remain active.\n\nAll commits must follow [commit message guidelines](references\u002Fmessage.md).\n\n## Runtime enforcement\n\n1. **Record each background assignment you dispatch**, including reuse. Before dispatch, set a deadline based on expected effort and complexity. Record the routed model and its exact explicit effort or host-default omission. Track task and agent IDs, start time, extension count (initially zero), and enforcement handle as available.\n2. **Arm enforcement before waiting.** Use a host timeout or parent-owned scheduler bounded by the nearest assignment or checkpoint deadline. Independently time out blocking operations. Recheck deadlines whenever control returns, including after user interruptions.\n3. **At expiry**, request status, completed work, blockers, and updated ETA by a bounded checkpoint deadline. Keep overdue work under a deadline. On timely status, confirm completion, stop the worker, or grant its only ETA-based extension. If extended, record the new deadline, increment the count, and re-arm enforcement. Preserve the count across follow-ups. Stop the worker on a missed checkpoint or expired extension.\n4. **Before transferring ownership**, confirm the worker and its write-producing operations have stopped, then route and dispatch a fresh replacement. If shutdown is unconfirmed, report the blocker and continue independent work. Cancel enforcement on completion.\n\n## Steps\n\n1. Activate the `exec-plans` skill, then read the plan, milestones, and tasks to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tasks - relevant codebase files or external documentation. Brief it with the needed context, acceptance criteria, and known negative cases, using context pointers where those facts are already available. Ensure the exploration subagent can save files - it should save its markdown notes in a directory next to the plan, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. If current branch is `main` or `master`, create a new **integration branch**. Start the **integration coordinator** subagent, instructing it to activate the `exec-plans` skill and reconcile its required plan sections before reporting a checkpoint complete.\n\n4. Use **implementer subagents** to implement each task, each in its own worktree on its own branch. Follow the router’s final dispatchable route and runtime enforcement as specified above. Each implementer subagent:\n   - confirms its worktree is based on the integration branch before starting, and resets onto it if not;\n   - calls the Skill tool with `tdd` to build the task;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, have the same **integration coordinator subagent** merge its work to the integration branch.\n\n6. If this changes the **frontier** of available tasks, kick off more **implementer subagents** to work on the new tasks. This allows for maximum concurrency.\n\n7. Once all tickets are complete, follow the [code review fix cycle](#code-review-fix-cycle).\n\n8. Ensure all tasks and milestones are resolved and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees and their related branches.\n\n## Code review fix cycle\n\nCall the Skill tool with `code-review-biaxis` on the integration branch. Track all issues raised by the code review as new tasks in the ExecPlan **frontier**, then fix them in a single **implementer subagent**. Repeat _code review → fix cycle_ until no issues remain for a maximum of three iterations. Report all unresolved issues.\n\nFor each repeat of the cycle, prefer reusing the code review and implementer subagents from the previous iteration when they match the final dispatchable route: the same model with no original effort override for `host_default`, or the exact model\u002Feffort pair for `explicit`. Otherwise, dispatch a fresh agent.\n\n## Gotchas\n\n- Do not create worktrees anywhere within the main project directory because agents will automatically discover files like `AGENTS.md` causing context window bloat. Recommend creating them in `..\u002F\u003Cproject name>.worktrees`.\n",{"name":5,"description":7,"compatibility":43},"Requires subagent dispatch with model controls and effort controls when the route requires explicit effort.","main","8a912f4cf9bf915fb92e5b29671f0ed22555bcb7","skills\u002Fdefault\u002Fexecplan-implement","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills","https:\u002F\u002Fgithub.com\u002Fjapurcell","2026-11-11 08:59:34",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add japurcell\u002Fskills --skill execplan-implement",{"tool":56,"command":57},"bunx","bunx skills add japurcell\u002Fskills --skill execplan-implement",{"tool":59,"command":60},"pnpm","pnpm dlx skills add japurcell\u002Fskills --skill execplan-implement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fexecplan-implement\u002FSKILL.md",true,[64,70,74],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"evals\u002Fevals.json","REFERENCE","参考文档",22468,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fexecplan-implement\u002Fevals\u002Fevals.json",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002FREADME.md",782,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fexecplan-implement\u002Fevals\u002FREADME.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fmessage.md",1341,"https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fexecplan-implement\u002Freferences\u002Fmessage.md",[79,108,130,159,181,201],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":90,"publishedAt":38},"01M6PT0ZTYCN4DHK3SXWS79WSY","spec-create","Create or revise a portable behavioral SPEC for a feature or whole product. Use when specifying a new idea, documenting an existing system for reimplementation, or defining a change while preserving compatibility. Implementation planning is a separate task.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fspec-create\u002FSKILL.md",[85],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[91,92,93,94,95,96,97,27,98,99,100,101,102,37,103,104,105,106,107],"create","spec","spec create","feature","planning","for","system","Existing","task","output","change","product","revise","compatibility","behavioral","idea","path",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":38},"01M6GSVHQ4MY4R4SMS8RY6324Q","prd-ralph","Complete at most one eligible unfinished PRD task, verify it, log progress, and optionally create one scoped commit.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fprd-ralph\u002FSKILL.md",[114],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},[116,117,118,91,119,120,121,122,123,124,99,125,126,127,128,129,107],"prd ralph","ralph","prd","progress","verify","at","complete","commit","it","log","scoped","false","file","id",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":139,"publishedAt":38},"01M6GSYMGHE2FEGEFKD926EJH8","fsdp-style-guide","Mandatory for all UI\u002FUX design, implementation, review, audit, or visual regression tasks. Always use for any work that affects user-facing appearance, behavior, accessibility, branding, layout, navigation, forms, dialogs, alerts, tables, or visual design.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Ffsdp-style-guide\u002FSKILL.md",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000032","设计师",[140,141,142,143,144,145,146,147,27,148,149,150,151,152,153,154,155,156,157,158,96],"fsdp style guide","style guide","FSDP","style","guide","visual regression","regression","design","visual","tasks","review","visual design","alerts","work","branding","layout","audit","ux","behavior",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":38},"01M6GSYHEQARNM7WN0RJA7K7T2","agency-priorities","Provide self-contained USDA strategic goals and Forest Service priorities for agency briefings, proposals, and work-plan alignment. Use when explaining agency direction or evaluating how a project contributes to USDA and Forest Service priorities.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Fagency-priorities\u002FSKILL.md",[],[166,167,168,169,170,153,171,172,173,174,175,176,177,178,27,96,24,179,180],"agency priorities","priorities","agency","self","alignment","plan","goals","proposals","direction","how","project","strategic","service","briefings","self-contained",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":190,"publishedAt":38},"01M6GSY9VVN8RSJ5QYM540ZJ1D","accomplishment-report","Create a concise Forest Service executive accomplishment report when all work in an ExecPlan is completed, or update its existing report. Use at ExecPlan closeout and when asked to report completed work, agency alignment, and estimated AI-assisted versus human-only time and cost savings.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fforest-service\u002Faccomplishment-report\u002FSKILL.md",[187],{"categoryNo":188,"categoryName":189,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000034","行政与办公人员",[191,192,170,193,91,153,194,195,196,197,121,168,198,178,27,199,200,20,98,24],"report","accomplishment report","cost","concise","human","time","update","only","closeout","savings",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":215,"publishedAt":38},"01M6GSY7J8ZMCE319P8Y6JZ432","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fjapurcell\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdefault\u002Fwriting-for-agents\u002FSKILL.md",[207,212],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":213,"categoryName":214,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000036","内容创作者",[216,217,96,27,218,219,24],"writing","writing for agents","documents","editing"]