[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVXZDT7FGT4KB4TBAGJ0W8":3,"skill-same:01M7EVXZDT7FGT4KB4TBAGJ0W8":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7EVXZDT7FGT4KB4TBAGJ0W8","implement-spec",null,"Implement the result of \u002Fto-spec and \u002Fto-tickets in code.","Bryan13092005\u002Fmoviles-tarea3-pomodoro","Bryan13092005","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235162230?v=4","01M7EVG43ZBM4S36Y0RY5ZXWNK","01M7EVG44G6Q3BRVCZV6CPNW7K",0,"MIT","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fimplement-spec\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implement-spec\ndescription: \"Implement the result of \u002Fto-spec and \u002Fto-tickets in code.\"\ndisable-model-invocation: true\n---\n\nYou have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\n\nThe goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.\n\nThe tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.\n\n**Implementer subagents** should be run in the background where possible for maximum concurrency.\n\n## Steps\n\n1. Read the spec and tickets to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.\n\n4. Use **implementer subagents** to implement each ticket, each in its own worktree on its own branch. 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 ticket;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.\n\n6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.\n\n7. Once all tickets are complete, call the Skill tool with `code-review` on the integration branch. Fix all issues raised by the code review in a single **implementer subagent**.\n\n8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees.\n","You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.\n\nThe issue tracker should have been provided to you. If not, tell the user to run `\u002Fsetup-matt-pocock-skills`.\n\nThe goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.\n\nThe tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.\n\nCommunication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.\n\n**Implementer subagents** should be run in the background where possible for maximum concurrency.\n\n## Steps\n\n1. Read the spec and tickets to understand the task graph.\n\n2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.\n\n3. Create the integration branch. If the issue tracker closes work through PRs, or the user asks for one, open a draft PR after the first merge in step 5 (a branch with no commits ahead of main can't open one), marked as closing the spec and tickets.\n\n4. Use **implementer subagents** to implement each ticket, each in its own worktree on its own branch. 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 ticket;\n   - merges the integration branch tip into its own branch before reporting done\n\n5. Once an **implementer subagent** completes, merge its work to the integration branch with a **merger subagent**.\n\n6. If this changes the **frontier** of available tickets, kick off more **implementer subagents** to work on the new tickets. This allows for maximum concurrency.\n\n7. Once all tickets are complete, call the Skill tool with `code-review` on the integration branch. Fix all issues raised by the code review in a single **implementer subagent**.\n\n8. If a draft PR exists, mark it ready for review. Otherwise, resolve each ticket the way the issue tracker closes work, and report the integration branch.\n\n9. Clean up all **implementer subagent** worktrees.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","66348dde3149cd8b85398e250b99c3a0be21fb55",".grok\u002Fskills\u002Fimplement-spec","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro","https:\u002F\u002Fgithub.com\u002FBryan13092005","2026-10-21 10:41:51",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Bryan13092005\u002Fmoviles-tarea3-pomodoro --skill implement-spec",{"tool":36,"command":37},"bunx","bunx skills add Bryan13092005\u002Fmoviles-tarea3-pomodoro --skill implement-spec",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Bryan13092005\u002Fmoviles-tarea3-pomodoro --skill implement-spec","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fimplement-spec\u002FSKILL.md",[43],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.grok\u002Fskills\u002Fimplement-spec\u002Fagents\u002Fopenai.yaml",[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":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"01M7EW14K9Q7KJNZBDJKXC19QF","sdd","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fsdd\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M7EW11JNV3H3STKZ6MWE5HA0","rn-conventions","Úsala siempre que crees o modifiques pantallas, formularios o componentes de interfaz del Temporizador Pomodoro.","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Frn-conventions\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M7EW0XYVMEDERRH88XBYJJ4C","reglas-pomodoro","Úsala siempre que escribas, modifiques o revises código o textos que ejecuten, calculen, configuren o muestren el temporizador, estados, tiempos de descanso o ciclos del Pomodoro.","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Freglas-pomodoro\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7EW0TM6RG39B64JY7ZF3MY5","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7EW0QQBCA9VNSVXRHZ7BKVZ","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Fgrill-me\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7EW0MTENH0569RCR5FEE6R5","estilos-colores","Úsala siempre que crees o modifiques colores, estilos o pantallas de la aplicación.","https:\u002F\u002Fgithub.com\u002FBryan13092005\u002Fmoviles-tarea3-pomodoro\u002Fblob\u002Fmain\u002F.opencode\u002Fskills\u002Festilos-colores\u002FSKILL.md",[],[]]