planner

Converts roadmap items into labeled GitHub tracking issues and keeps the roadmap ordered.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill planner-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/.claude/skills/planner
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill planner-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Roadmap items written as loose intents never become actionable work, and tracking their execution status by hand drifts out of sync with reality. This Skill decomposes ratified roadmap items into well-scoped GitHub issues and derives execution status automatically from issue state. ## Core Features & Use Cases - Roadmap decomposition: Converts each ratified item in .open-autonomy/roadmap.yml into one or more closeable GitHub issues, each labeled with origin:roadmap-planner, roadmap:<id>, and priority/phase labels. - Derived status tracking: Computes item progress (parked, in progress, done) from child issue state instead of hand-written status fields, using a soft planned: true gate. - Roadmap maintenance: Reorders, splits, merges, and sharpens items, reopens prematurely closed issues, and closes orphaned tracking issues whose parent item was retired. - Use Case: A strategist adds a new feature intent to the roadmap; the planner breaks it into a substantial issue, links it with the roadmap:<id> label, sets planned: true, and the item's progress is tracked automatically as the issue's PR merges. ## Quick Start Ask the planner to read .open-autonomy/roadmap.yml and decompose any unplanned ratified items into labeled GitHub tracking issues.

Frequently Asked Questions about planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert roadmap items into GitHub issues automatically?▼

The planner reads .open-autonomy/roadmap.yml, lists existing issues with gh issue list, and creates one substantial issue per ratified item using gh issue create. Each issue carries origin:roadmap-planner, roadmap:<id>, and priority/phase labels so progress rolls up to the parent item.

How is roadmap item status tracked without manual updates?▼

Execution status is derived from child issues: an item is parked until decomposed, in progress while its issues are open, and done once they all close. The planner never writes status fields; it only sets a reversible planned: true flag when decomposition is complete.

Should I split a roadmap item into many small issues?▼

No. The planner prefers one large, cohesive issue per item that a developer can carry end to end. Split only when an item bundles genuinely unrelated implementations that different change-sets would touch, and never file perpetual umbrella issues that can never close.

What happens to tracking issues when a roadmap item is retired?▼

When the strategist removes an item from roadmap.yml but its roadmap:<id> issues remain open, the planner closes them with a comment noting the item was retired. A tracking issue with no parent item is treated as dead work.

Can the planner merge roadmap changes or create strategy items?▼

No. Roadmap file edits are proposed as auto-merging PRs blessed by a strategy reviewer, and issue creation is direct. The planner never authors new strategy items, never sets execution status, and never merges anything.