repo-planner

Organize AI-assisted development with a five-document planning loop.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/B2Gdevs/custom_portfolio --skill repo-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-planner
Source: https://github.com/B2Gdevs/custom_portfolio/tree/main/skills/repo-planner
Command: npx skills add https://github.com/B2Gdevs/custom_portfolio --skill repo-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organize and coordinate AI-assisted development in large codebases by enforcing a living, five-document planning loop.

Core Features & Use Cases

  • Supports a global and section planning model using .planning/ and MDX/XML docs to track state, roadmap, tasks, decisions, and requirements.
  • Provides kickoff templates, task registries, and decisions to guide execution and ensure alignment across teams.
  • Applies to monorepos with vendor submodules and cross-project dependencies, helping teams synchronize planning across multiple apps.

Quick Start

Initialize the planning root in your repository and generate the first kickoff to start the planning loop.

Frequently Asked Questions about repo-planner

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

FAQPage Schema
How do I plan and coordinate AI-assisted development across a monorepo?

Plan AI-assisted monorepo development by applying a living five-document planning loop that tracks project state, roadmap, task registries, decisions, and requirements. It coordinates work across vendor submodules and cross-project dependencies using structured MDX or XML artifacts.

What is a living repository planning loop and how does it work?

A living repository planning loop continuously updates five core planning documents—requirements, roadmap, state, task-registry, and decisions—as work progresses. It mandates phase IDs and keeps AI-assisted project state and decisions current from kickoff to closure.

How do I start structured project planning from kickoff to closure?

Start structured project planning by initializing a .planning directory in your repository and generating the first kickoff. This creates task registries and decision logs that guide execution and ensure alignment across teams throughout the project lifecycle.

Does this planning approach support both MDX and XML formats?

Yes, the planning approach supports both MD/MDX and XML formats for repository artifacts. It applies to repositories containing planning-oriented files like ROADMAP, STATE, TASK-REGISTRY, and DECISIONS documents in either format.

Can I use this for monorepos with vendor submodules and cross-project dependencies?

Yes, you can use this for monorepos with vendor submodules and cross-project dependencies. It helps synchronize planning across multiple apps by coordinating structured planning artifacts and maintaining alignment across the entire codebase.

What are the limitations of using a five-document planning loop for repository management?

The five-document planning loop requires maintaining five separate files—requirements, roadmap, state, task-registry, and decisions—and mandates phase IDs. This overhead may not suit small projects that lack a .planning directory or existing planning-oriented artifacts.