skills.rest
bfly123
bfly123COMMUNITY
Explore all skills by this author →
GitHub

plan-tree

Maintain structured Markdown planning trees with roadmaps, decisions, and handoff status files.

3.5k|342|Updated Oct 25, 2025
Search Tags:#Markdown#decision records#Documentation#Planning#ROADMAP#HANDOFF#Knowledge Base
One-click install
npx skills add https://github.com/bfly123/claude_code_bridge --skill plan-tree
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-tree
Source: https://github.com/bfly123/claude_code_bridge/tree/main/useful_tools/claude_skills/plan-tree
Command: npx skills add https://github.com/bfly123/claude_code_bridge --skill plan-tree

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-file planning folders drift out of sync: roadmaps claim work is done without evidence, open questions hide resolved decisions, and handoff state gets lost between sessions. This Skill keeps a tree of Markdown planning documents navigable, current, and internally consistent.

Core Features & Use Cases

  • Structured Document Model: Organizes roadmap, implementation-status, topics, decisions, open questions, ideas, and history files with clear roles and governance rules.
  • Intent-Based Workflows: Routes requests like idea capture, promotion, status updates, decision records, archival, audits, and session resume to the right files.
  • Consistency Auditing: Runs final checks for broken links, duplicate decisions, unsupported status claims, and drift between plans and implemented code.
  • Use Case: After a long implementation session, ask the agent to update the plan tree: it reconciles Done/In Progress/Next states, moves completed detail into history, records new decisions, and leaves a short handoff file so the next session can resume instantly.

Quick Start

Use the plan-tree skill to audit this planning folder and reconcile the roadmap, implementation status, decisions, and open questions.

Frequently Asked Questions about plan-tree

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

FAQPage Schema
How do I organize a multi-file planning folder in Markdown?▼

Use a plan tree with a root README, roadmap grouped by Done/In Progress/Next/Deferred, topic files, numbered decision records, and an open-questions file. Add indexes, history, and ideas folders only when navigation problems actually appear.

How to resume implementation work from a handoff document?▼

Read the root README first, then the implementation-status file for current phase, active TODO, blockers, next commit target, and last verification. Read only the topic and decision files linked from the active TODO before editing.

What is the difference between a roadmap and an implementation status file?▼

The roadmap holds high-level phase state grouped as Done, In Progress, Next, and Deferred. The implementation-status file is a short operational handoff with current phase, active TODO, blockers, and verification notes for session resume.

When should I create a decision record instead of a topic note?▼

Create a decision record when an open question has converged into a stable choice. Use a minimal Context/Decision/Consequences format, link it from the related topic and roadmap item, and move the resolved question out of open-questions.

Can this skill work with an existing docs folder structure?▼

Yes, it adapts to existing folder names, document styles, and conventions rather than forcing a fixed template. The generic document model defines roles, not mandatory directories, and restructuring only happens when navigation is already failing.

What are the limitations of a Markdown planning tree?▼

The skill manages planning documents only; it does not perform code review, architecture scoring, implementation, or release gating. It also avoids generating full plans from scratch unless explicitly requested.

Related Skills

Explore More Product & Management Skills→
prestariusprestarius
1

meeting-notes

Transform raw meeting notes into structured minutes with decisions and action items.

Community
Intermediate
hackefellerhackefeller
1

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Official
Intermediate
Asharf30Asharf30

docs-guard

Cross-reference documentation claims against source code implementations.

Community
Advanced
cwijayasundaracwijayasundara
3

tracker-publish

Publish Claude Harness dependency groups to Linear/Jira tracker tasks.

Community
Advanced