Plan Tree

Plan Tree

Use this skill to manage a tree of Markdown planning documents. The goal is to keep plans navigable, current, and internally consistent while preserving the user's intent and existing document style.

Execution Contract

For every plan-tree task:

1. Identify the plan root and user intent before editing.
2. Read the root index plus only the relevant status, topic, decision, question, idea, or history files.
3. Classify the request as an idea, promotion, status update, question, decision, archive, audit, resume, restructure, or consistency repair.
4. Preserve the existing planning entrypoint, registered plan roots, folder names, document style, and authority order unless the task is specifically to reorganize them.
5. Keep active roadmap and handoff files small; move historical evidence out of active state.
6. Update indexes, retrieval headers, and links when adding, moving, promoting, archiving, or splitting durable files.
7. Run the final checks before replying.
8. Report changed files, unresolved questions, and the next useful maintenance action.

Intent Routing

When the request maps to one of these intents, follow the corresponding behavior. Explicit shortcuts such as $plan-tree idea or $plan-tree resume are intent hints, not a strict command language; natural-language requests with the same meaning should behave the same way.

• idea: add a low-commitment thought to ideas/inbox.md or the local equivalent.
• promote: move an idea into a roadmap item, topic, open question, or decision, and link the original idea to the promoted artifact.
• status: update active implementation or handoff state.
• question: add, narrow, or resolve an open question.
• decision: create or update a stable decision record.
• archive: move superseded evidence, old status detail, or reference-only material out of active files.
• audit: run consistency, retrieval, and drift checks without changing structure unless asked.
• resume: follow the resume workflow and summarize current phase, TODO, blockers, next target, and last verification before editing.

Document Model

Prefer this generic shape when creating a new tree, but adapt to existing names and conventions:

<plan-root>/
  README.md
  roadmap.md
  implementation-status.md
  open-questions.md