plan-roadmap

Creates a structured roadmap and discussion summary from feature planning sessions.

Updated Aug 27, 2026

Search Tags:#planning #documentation #collaboration #github #roadmap #feature #product-management

Ready to run

npx skills add https://github.com/mikefullerton/cat-herding --skill plan-roadmap-mikefullerton

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-roadmap
Source: https://github.com/mikefullerton/cat-herding/tree/main/skills/plan-roadmap
Command: npx skills add https://github.com/mikefullerton/cat-herding --skill plan-roadmap-mikefullerton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning a feature can be chaotic without a formal process. This Skill provides a two-phase workflow to move from an initial idea to a concrete Roadmap, ensuring alignment and traceability.

Core Features & Use Cases

Phase 1: Discussion — explore the idea with a guided, interactive conversation to surface goals, constraints, and acceptance criteria.
Phase 2: Planning — transform the discussion into a structured Roadmap with a prioritized sequence of implementation steps, ready for review and PR creation.
Outputs: Roadmap.md in a draft directory, a discussion-summary.md, and lifecycle state markers, all written to a temporary draft area before being moved to the main repo by an activation step.
No code is produced during planning; the Skill only generates planning documents and placeholders for future work.

Quick Start

Start planning by saying /plan-roadmap to begin a two-phase feature planning session.

Frequently Asked Questions about plan-roadmap

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

FAQPage Schema

How do I turn early-stage product ideas into a structured roadmap?▼

To turn early-stage product ideas into a structured roadmap, use a two-phase workflow that formalizes initial discussions into a prioritized sequence of implementation steps. It generates a draft Roadmap.md and a discussion-summary.md without producing implementation code.

What is the best way to plan features for GitHub without writing implementation code?▼

The best way to plan features without writing implementation code is to use a workflow that generates only planning documents, metadata, and placeholders. It produces a PR-ready Roadmap.md and discussion summaries in a temporary draft area before moving them to your main repository.

Can I use this feature planning process to capture goals and acceptance criteria before development?▼

Yes, you can use the feature planning process to capture goals and acceptance criteria before development. Phase 1 uses an interactive conversation to surface constraints and goals, which are then transformed into a structured roadmap with defined steps in Phase 2.

Does roadmap planning generate files directly in the main GitHub repository?▼

Roadmap planning does not generate files directly in the main GitHub repository initially. All outputs, including the Roadmap.md and lifecycle state markers, are written to a temporary draft directory and moved to the main repo by an activation step.

What documents are produced during the feature roadmap planning workflow?▼

The feature roadmap planning workflow produces a Roadmap.md containing prioritized implementation steps, a discussion-summary.md capturing the initial conversation, and lifecycle state markers. These documents are created without generating any implementation code.

When should I avoid using a structured roadmap planning process?▼

You should avoid using a structured roadmap planning process if your project requires immediate implementation code rather than planning documents. This workflow specifically generates metadata, roadmaps, and placeholders, ensuring no implementation code is produced during the planning phase.