overseer-plan

Convert markdown planning documents into Overseer task hierarchies via MCP codemode.

Updated Jun 12, 2025
One-click install
npx skills add https://github.com/stevoland/dotfiles --skill overseer-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overseer-plan
Source: https://github.com/stevoland/dotfiles/tree/main/opencode/skill/overseer-plan
Command: npx skills add https://github.com/stevoland/dotfiles --skill overseer-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert markdown planning documents into Overseer tasks via MCP codemode, enabling trackable task hierarchies.

Core Features & Use Cases

  • Convert plan markdown into a milestone and structured tasks/subtasks using Overseer MCP codemode.
  • Automatically extract the plan structure to produce a clear task hierarchy for implementation.
  • Use when mapping plans, specs, or design docs to generate actionable execution work.

Quick Start

Use the overseer-plan command to convert a markdown planning document into Overseer tasks. Example: /overseer-plan plan.md

Frequently Asked Questions about overseer-plan

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

FAQPage Schema
How do I convert markdown planning documents into trackable tasks?

You can convert markdown planning documents into trackable tasks by applying the overseer-plan command via MCP codemode. It automatically extracts the plan structure to produce a clear task hierarchy for implementation.

What is the best way to generate task hierarchies from design docs?

Generating task hierarchies from design docs is best handled by converting the markdown structure into milestones and structured subtasks. This enforces task atomicity and VCS bookmarking via the Overseer MCP API.

Can I use MCP codemode to map specs into milestones and subtasks?

Yes, you can use MCP codemode to map specs into milestones and subtasks. The process extracts the document structure to generate actionable execution work and trackable task hierarchies.

How do I enforce task atomicity when breaking down a project plan?

To enforce task atomicity when breaking down a project plan, convert the markdown file using the Overseer MCP API. This ensures the extracted task hierarchy remains structured and trackable.

Does converting plans with Overseer support VCS bookmarking?

Yes, converting plans with Overseer supports VCS bookmarking. The task hierarchy generation process via MCP codemode automatically enforces VCS bookmarking through the Overseer MCP API.