overseer-plan_skill

This skill converts Markdown planning documents into Overseer tasks and milestones, producing a structured, trackable hierarchy from plans to actionable work.
  • TypeScript

470

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill dmmulroy/.dotfiles --skill overseer-plan

  • SKILL.md3.4 KB

Overview

This skill converts Markdown planning documents into tracked Overseer tasks using MCP codemode. It reads a plan or spec, extracts the top-level title as a milestone, analyzes heading structure to produce tasks and subtasks, and persists them into Overseer. The output includes created task IDs and a concise breakdown summary for review and iteration.

How this skill works

The skill parses the Markdown file, uses the first H1 (stripping a "Plan: " prefix if present) as the milestone title, and inspects headings and lists to derive child tasks (depth 1) and subtasks (depth 2). It enforces task quality rules (atomic, validated, clear), applies priority and optional parent linking, and calls the Overseer MCP codemode to create records in SQLite. After creation it returns IDs and supports later operations like get, list, start, and complete.

When to use it

  • After finalizing a plan in plan mode and you need tracked work items
  • Converting specs or design docs into implementation task hierarchies
  • Turning roadmap or milestone documents into assignable tasks
  • Preparing work for sprint planning or handoff to engineers
  • When you want systematic, testable acceptance criteria attached to tasks

Best practices

  • Keep sections focused so the parser yields atomic tasks (one committable change each)
  • Include explicit acceptance criteria or "Done when:" lines for validation
  • Structure documents with clear H1/H2/H3 headings to control milestone/task/subtask depth
  • Set priority 1-5 and use --parent only when nesting under an existing Overseer task
  • Run the Oracle review step to iterate on the proposed breakdown before persisting

Example use cases

  • Convert a design doc into a milestone with implementation tasks and tests
  • Create a sprint backlog from a roadmap markdown file with priorities
  • Break a feature spec into tasks and subtasks for frontend, backend, and infra work
  • Import a migration plan and attach explicit acceptance criteria to each task
  • Turn a cross-repo implementation guide into an Overseer milestone with tracked children

FAQ

/overseer-plan <markdown-file-path> with optional flags like --priority <1-5> and --parent <task-id>.

When will the skill create subtasks instead of tasks?

Subtasks are created for depth-2 items or when 3–7 separable work items, multiple components, or clear sequential dependencies are detected.

Do start and complete work without a VCS?

CRUD operations work without a VCS, but start and complete require a git or jj repository and will fail with NotARepository if none is found.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational