orient-roadmap

Computes a project's forward roadmap of increments, gates, and runway stages from git and plan evidence.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill orient-roadmap-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orient-roadmap
Source: https://github.com/allemaar/open-skills/tree/main/skills/orient-roadmap
Command: npx skills add https://github.com/allemaar/open-skills --skill orient-roadmap-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When returning to a project, repo, or plan, it is hard to answer "what comes next, and what gates it?" without manually digging through git history, plan documents, and folder state. This Skill produces a fresh, read-only snapshot of the forward horizons — the increment arc (built → current → next), what ships now, the gates, the next increment's clusters, and the runway of gated stages — without mutating any state. ## Core Features & Use Cases - Forward-horizon board: Renders the increment arc, now-shipping items, gates, next clusters (with the paramount one starred), the runway (now → gated-next → future), and deferred lanes in one view. - Bounded read-only subagent gathering: Delegates evidence collection to a depth-1 subagent with a cheap-first evidence ladder (git tier → plan/doc tier → conversation/folder tier), returning only a distilled bundle with re-runnable proofs. - Provenance-tiered, fail-closed output: Every field is tagged attested/inferred/guessed, and barren evidence produces an honest "NO SUBSTRATE" card instead of a fabricated roadmap. - Three render faces: A structured YON record for agent consumers, a plain-language markdown read for humans, and a visual widget with a mandatory information-complete ASCII twin. - Use Case: Ask "show me the roadmap" on a repository and receive the built → current → next arc, the gates blocking the next increment, and the deferred lanes, each line tagged with its evidence tier. ## Quick Start Ask the agent to show you the roadmap and what's next for the current project or repository.

Frequently Asked Questions about orient-roadmap

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

FAQPage Schema
How do I see what comes next in my project roadmap?

Invoke the skill with a phrase like "show me the roadmap" or "what's next" on a project, repo, or plan. It computes the increment arc (built → current → next), the gates, the next increment's clusters, and the runway of gated stages from current evidence.

What is the difference between orient-roadmap and orient-status?

orient-roadmap reports the forward horizons: increments not yet reached, the runway of gated stages, and deferred lanes. orient-status reports position, remaining work, and a banded ETA on the single current increment you stand on.

Does orient-roadmap work on a folder without git or a plan file?

Yes, but it degrades honestly. With no git history and no plan document, it renders a "NO SUBSTRATE" card stating that no horizons can be drawn, rather than fabricating a structural roadmap from guesses.

Does orient-roadmap modify my repository or write state to disk?

No. It is strictly read-only: gathering is delegated to a bounded, read-only subagent, and the north-star intent and last-look anchor are caller-supplied or git-inferred, never written to disk. Every call recomputes from current reality.

When should I use orient-map instead of orient-roadmap?

Use orient-map when you want the retrospective delta — what changed since your last look and the topology around your current position. Use orient-roadmap when you want the prospective view of where the work is going across multiple future increments.