aif-roadmap

Generate or update .ai-factory/ROADMAP.md with high-level milestones and dependencies.

56|3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/lee-to/ai-workspace --skill aif-roadmap-lee-to
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-roadmap
Source: https://github.com/lee-to/ai-workspace/tree/main/.claude/skills/aif-roadmap
Command: npx skills add https://github.com/lee-to/ai-workspace --skill aif-roadmap-lee-to

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI and product teams often struggle to align across multiple projects and roadmaps. aif-roadmap provides a structured way to create or update a centralized roadmap that captures major milestones, dependencies, and progress in .ai-factory/ROADMAP.md.

Core Features & Use Cases

  • Generate a high-level roadmap with major milestones based on project context, codebase signals, and stakeholder input.
  • Update ROADMAP.md to reflect changes in scope, priorities, or completed work across related projects.
  • Use for software product planning, research initiatives, or cross-team strategic alignment.

Quick Start

Analyze your current project context and run the skill to produce or refresh .ai-factory/ROADMAP.md with a clear milestone sequence.

Frequently Asked Questions about aif-roadmap

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

FAQPage Schema
How do I maintain a high-level project roadmap for cross-team initiatives?

A centralized roadmap tracks major milestones, dependencies, and progress across multiple codebases. By generating or updating a single ROADMAP.md file based on project context, teams align visions and maintain one source of truth for cross-team initiatives.

What is the best way to track cross-team project milestones and dependencies?

The best way to track cross-team project milestones is using a centralized ROADMAP.md file. It enforces high-level milestone tracking and captures dependencies across related projects, ensuring all stakeholders align on scope, priorities, and completed work.

How do I generate a roadmap from existing project context and codebase signals?

Generate a roadmap by analyzing project context, codebase signals, and stakeholder input. The process produces a clear milestone sequence in a reviewable ROADMAP.md file before saving, ensuring the output aligns with your current architecture and strategic vision.

Does this roadmap planning approach work for managing multiple codebases?

Yes, this roadmap planning approach works for managing multiple codebases. It is designed for software projects and cross-team initiatives, allowing you to reflect changes in scope, priorities, or completed work across related projects within a single file.

Can I review and modify the generated project roadmap before saving changes?

Yes, you can review and modify the generated project roadmap before saving changes. The governance enforces that all roadmap outputs are reviewable prior to writing, ensuring you maintain control over the single source of truth file.

When should I update a centralized roadmap file for software product planning?

You should update a centralized roadmap file for software product planning whenever there are changes in scope, priorities, or completed work across related projects. This keeps the high-level milestones and dependencies accurate for all stakeholders.