roadmap-planning
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.
- License 许可
- MIT
- 所属仓库
- RoderAI/roder
- 最近更新
- 2026-11-13
- Stars
- ★ 9
- Forks
- 1
01 前言 Front Matter
- name
- roadmap-planning
- metadata
- { "short-description": "Create and maintain roadmap plans" }
- description
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml292 B
03 SKILL.md 正文
Roadmap Planning
Use 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.
Workflow
- Inspect the current roadmap index and nearby phase plans before writing.
- In Gode, start with
roadmap/00-feature-inventory-and-sequencing.md. - Read the closest existing phase plans and relevant source files so the new plan is grounded in the repo.
- In Gode, start with
- Produce durable artifacts, not chat-only planning.
- Add or update
roadmap/{NN}-{feature-slug}.md. - Update the phase map and any phase-count checklist in the roadmap index.
- Add or update
- Use the standard implementation-plan header:
# [Feature Name] Implementation Plan
> **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.
**Goal:** [one sentence]
**Architecture:** [2-3 sentences]
**Tech Stack:** [key technologies]
---
- Make the plan delegable.
- Include
## Owned Paths,## Dependency Checks,## Tasks, per-taskRun:commands, andAcceptance:criteria. - Split tasks by ownership boundary so separate agents can work without shared write sets.
- Name exact files and packages to inspect or modify.
- Include local-only verification paths; guard live provider or network checks behind explicit env vars.
- Include
- Keep the roadmap document as the source of truth.
- When executing a roadmap, mark task checkboxes as work completes.
- If implementation changes the plan, update the document before reporting completion.
- Do not replace the roadmap with an untracked scratch note.
- Treat threads as execution lanes that can attach to roadmap tasks; transcripts are evidence, not the roadmap state.
- Keep language repo-owned.
- Mention external references only when the user asks for direct parity or source comparison.
- Avoid making plans read like copied product requirements from another project.
Validation
Run focused checks after editing roadmap files:
for f in roadmap/*.md; do
printf '%s\t' "$f"
rg -q '^# ' "$f" && printf 'heading '
rg -q '^\\*\\*Goal:\\*\\*' "$f" && printf 'goal '
rg -q '^\\*\\*Architecture:\\*\\*' "$f" && printf 'arch '
rg -q '^## Owned Paths' "$f" && printf 'owned '
rg -q '^## Tasks' "$f" && printf 'tasks '
rg -q '^Run:' "$f" && printf 'run '
rg -q '^Acceptance:' "$f" && printf 'accept '
printf '\n'
done
Also scan for stale phase counts, placeholder text, unintended reference-project names, and unchecked acceptance gaps.
04 同仓库更多 Skills
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.
review
Review code changes.
vcs-snapshot
Create a scoped version-control snapshot.
webwright
Drive a local Playwright browser through a Roder-owned Webwright workspace with plan, final script, screenshots, logs, and verification evidence.
vcs-snapshot
Create scoped VCS snapshots from the current workspace state.
roder-config
Configure and live-reload Roder from pasted config snippets, especially MCP server JSON, without leaking secrets or enabling executable integrations without approval.