[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75PSB4JAF751G5Y8G5EVA6E":3,"skill-same:01M75PSB4JAF751G5Y8G5EVA6E":56},{"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":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M75PSB4JAF751G5Y8G5EVA6E","roadmap-planning",null,"Use when creating, updating, validating, or executing delegable roadmap plans under a repo's roadmap directory, especially for Gode feature phases and document-first planning workflows.","RoderAI\u002Froder","RoderAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F284978122?v=4","01M75PQQ8DXA6WMHGMZXS7CTP5","Roder","01M75PQQ91JEF84WMNZG8GQH8Q",9,"MIT","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Froadmap-planning\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: roadmap-planning\ndescription: Use when creating, updating, validating, or executing delegable roadmap plans under a repo's roadmap directory, especially for Gode feature phases and document-first planning workflows.\nmetadata:\n  short-description: Create and maintain roadmap plans\n---\n\n# Roadmap Planning\n\nUse this skill when the user asks to turn an idea into a roadmap, add a roadmap phase, split work for agents, or work through an existing roadmap document.\n\n## Workflow\n\n1. Inspect the current roadmap index and nearby phase plans before writing.\n   - In Gode, start with `roadmap\u002F00-feature-inventory-and-sequencing.md`.\n   - Read the closest existing phase plans and relevant source files so the new plan is grounded in the repo.\n2. Produce durable artifacts, not chat-only planning.\n   - Add or update `roadmap\u002F{NN}-{feature-slug}.md`.\n   - Update the phase map and any phase-count checklist in the roadmap index.\n3. Use the standard implementation-plan header:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [one sentence]\n**Architecture:** [2-3 sentences]\n**Tech Stack:** [key technologies]\n\n---\n```\n\n4. Make the plan delegable.\n   - Include `## Owned Paths`, `## Dependency Checks`, `## Tasks`, per-task `Run:` commands, and `Acceptance:` criteria.\n   - Split tasks by ownership boundary so separate agents can work without shared write sets.\n   - Name exact files and packages to inspect or modify.\n   - Include local-only verification paths; guard live provider or network checks behind explicit env vars.\n5. Keep the roadmap document as the source of truth.\n   - When executing a roadmap, mark task checkboxes as work completes.\n   - If implementation changes the plan, update the document before reporting completion.\n   - Do not replace the roadmap with an untracked scratch note.\n   - Treat threads as execution lanes that can attach to roadmap tasks; transcripts are evidence, not the roadmap state.\n6. Keep language repo-owned.\n   - Mention external references only when the user asks for direct parity or source comparison.\n   - Avoid making plans read like copied product requirements from another project.\n\n## Validation\n\nRun focused checks after editing roadmap files:\n\n```sh\nfor f in roadmap\u002F*.md; do\n  printf '%s\\t' \"$f\"\n  rg -q '^# ' \"$f\" && printf 'heading '\n  rg -q '^\\\\*\\\\*Goal:\\\\*\\\\*' \"$f\" && printf 'goal '\n  rg -q '^\\\\*\\\\*Architecture:\\\\*\\\\*' \"$f\" && printf 'arch '\n  rg -q '^## Owned Paths' \"$f\" && printf 'owned '\n  rg -q '^## Tasks' \"$f\" && printf 'tasks '\n  rg -q '^Run:' \"$f\" && printf 'run '\n  rg -q '^Acceptance:' \"$f\" && printf 'accept '\n  printf '\\n'\ndone\n```\n\nAlso scan for stale phase counts, placeholder text, unintended reference-project names, and unchecked acceptance gaps.\n","# Roadmap Planning\n\nUse this skill when the user asks to turn an idea into a roadmap, add a roadmap phase, split work for agents, or work through an existing roadmap document.\n\n## Workflow\n\n1. Inspect the current roadmap index and nearby phase plans before writing.\n   - In Gode, start with `roadmap\u002F00-feature-inventory-and-sequencing.md`.\n   - Read the closest existing phase plans and relevant source files so the new plan is grounded in the repo.\n2. Produce durable artifacts, not chat-only planning.\n   - Add or update `roadmap\u002F{NN}-{feature-slug}.md`.\n   - Update the phase map and any phase-count checklist in the roadmap index.\n3. Use the standard implementation-plan header:\n\n```markdown\n# [Feature Name] Implementation Plan\n\n> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.\n\n**Goal:** [one sentence]\n**Architecture:** [2-3 sentences]\n**Tech Stack:** [key technologies]\n\n---\n```\n\n4. Make the plan delegable.\n   - Include `## Owned Paths`, `## Dependency Checks`, `## Tasks`, per-task `Run:` commands, and `Acceptance:` criteria.\n   - Split tasks by ownership boundary so separate agents can work without shared write sets.\n   - Name exact files and packages to inspect or modify.\n   - Include local-only verification paths; guard live provider or network checks behind explicit env vars.\n5. Keep the roadmap document as the source of truth.\n   - When executing a roadmap, mark task checkboxes as work completes.\n   - If implementation changes the plan, update the document before reporting completion.\n   - Do not replace the roadmap with an untracked scratch note.\n   - Treat threads as execution lanes that can attach to roadmap tasks; transcripts are evidence, not the roadmap state.\n6. Keep language repo-owned.\n   - Mention external references only when the user asks for direct parity or source comparison.\n   - Avoid making plans read like copied product requirements from another project.\n\n## Validation\n\nRun focused checks after editing roadmap files:\n\n```sh\nfor f in roadmap\u002F*.md; do\n  printf '%s\\t' \"$f\"\n  rg -q '^# ' \"$f\" && printf 'heading '\n  rg -q '^\\\\*\\\\*Goal:\\\\*\\\\*' \"$f\" && printf 'goal '\n  rg -q '^\\\\*\\\\*Architecture:\\\\*\\\\*' \"$f\" && printf 'arch '\n  rg -q '^## Owned Paths' \"$f\" && printf 'owned '\n  rg -q '^## Tasks' \"$f\" && printf 'tasks '\n  rg -q '^Run:' \"$f\" && printf 'run '\n  rg -q '^Acceptance:' \"$f\" && printf 'accept '\n  printf '\\n'\ndone\n```\n\nAlso scan for stale phase counts, placeholder text, unintended reference-project names, and unchecked acceptance gaps.\n",{"name":5,"metadata":24,"description":7},{"short-description":25},"Create and maintain roadmap plans","master","cc8a773a0aeb90b9a2c6d9496045d0086befa159",".agents\u002Fskills\u002Froadmap-planning",1,"https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder","https:\u002F\u002Froder.sh","https:\u002F\u002Fgithub.com\u002FRoderAI","roder.sh","Roder maintain the last model harness the world will need","2026-11-13 16:46:55",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add RoderAI\u002Froder --skill roadmap-planning",{"tool":42,"command":43},"bunx","bunx skills add RoderAI\u002Froder --skill roadmap-planning",{"tool":45,"command":46},"pnpm","pnpm dlx skills add RoderAI\u002Froder --skill roadmap-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Froadmap-planning\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"agents\u002Fopenai.yaml","REFERENCE","参考文档",292,"https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Froadmap-planning\u002Fagents\u002Fopenai.yaml",[57,64,71,78,85,91],{"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},"01M75PV4G2KGTM7SWT2CH1V4AF","repo-tour","Use when a user asks for an orientation tour of an unfamiliar repository. Produces a structured tour of entry points, key modules, and how to run tests.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fexamples\u002Fpackages\u002Fdemo-roder-package\u002Fskills\u002Frepo-tour\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},"01M75PV378N4WSCDFRD1BCDAPS","review","Review code changes.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Ftests\u002Ffixtures\u002Fmodel\u002Fworkspace-review\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},"01M75PV216EXMRD1ZXTWZ94CZD","vcs-snapshot","Create a scoped version-control snapshot.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Ftests\u002Ffixtures\u002Fmodel\u002Fbuiltin-vcs-snapshot\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},"01M75PTW4RMS1K8FTKGSXBC895","webwright","Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Fwebwright\u002FSKILL.md",[],[],{"skillNo":86,"name":73,"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},"01M75PTRBG4VZVNJY9D7C8J7RK","Create scoped VCS snapshots from the current workspace state.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Fvcs-snapshot\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M75PTNTG14BJ27N6S5QBVGNA","roder-config","Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.","https:\u002F\u002Fgithub.com\u002FRoderAI\u002Froder\u002Fblob\u002Fmaster\u002Fcrates\u002Froder-skills\u002Fbuiltin\u002Froder-config\u002FSKILL.md",[],[]]