jr-roadmap

Align product roadmap direction using dependency-aware, timeline-free sequencing.

3|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rusi/junior --skill jr-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jr-roadmap
Source: https://github.com/rusi/junior/tree/main/agents/skills/jr-roadmap
Command: npx skills add https://github.com/rusi/junior --skill jr-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jr Roadmap helps product teams align roadmap direction when priorities shift by focusing on feature layers and sequence without fixed timelines.

Core Features & Use Cases

  • Clarifies direction and priorities at a high level without creating or redefining feature specs.
  • Plans development in a dependency-aware sequence that respects layer boundaries.
  • Synchronizes related high-level product docs to maintain consistency during roadmap updates.

Quick Start

Initiate the clarification loop to align direction, then draft and approve the roadmap contract.

Frequently Asked Questions about jr-roadmap

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

FAQPage Schema
How do I align a product roadmap without committing to fixed timelines?

To align a product roadmap without fixed timelines, use a sequence-first approach that prioritizes feature layers and dependency-aware ordering. This method enforces a clarification loop and contract approval to maintain alignment while keeping roadmap updates timeline-free.

What is a sequence-first roadmap and when do I need it?

A sequence-first roadmap is a planning approach that orders features by dependency layers rather than dates. You need it when priorities shift frequently, requiring cross-document synchronization and high-level direction alignment without redefining detailed feature specs.

How do I sequence roadmap features based on dependencies and layer boundaries?

Sequence roadmap features by applying a dependency-aware analysis that respects layer boundaries. This workflow uses a contract-style governance process, ensuring development planning respects sequence constraints while synchronizing related high-level product docs.

Can I update roadmap priorities without redefining underlying feature specs?

Yes, you can update roadmap priorities without redefining feature specs by clarifying direction at a high level. This process uses a contract approval loop and governance boundaries to shift sequence priorities while maintaining cross-document consistency.

What are the limitations of a timeline-free roadmap governance approach?

A timeline-free roadmap governance approach requires strict adherence to a contract-style workflow and clarification loop. It limits high-level direction shifts to sequence-based planning, meaning it cannot define specific delivery dates or bypass dependency layer boundaries.