overseer

Organize multi-session work into tickets with context, blockers, and learnings.

30|1|Updated Feb 19, 2022
One-click install
npx skills add https://github.com/princejoogie/dotfiles --skill overseer-princejoogie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overseer
Source: https://github.com/princejoogie/dotfiles/tree/main/opencode/.config/opencode/skills/overseer
Command: npx skills add https://github.com/princejoogie/dotfiles --skill overseer-princejoogie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Overseer codemode MCP helps teams organize work that spans multiple sessions by converting individual efforts into tickets that carry full context, decisions, and learnings for seamless handoffs.

Core Features & Use Cases

  • Tickets enable comprehensive context, block tracking, and learning bubbling across task hierarchies (milestones, tasks, subtasks).
  • Supports persistent task context propagation, blockers, and verification-driven completion to improve reliability and traceability.
  • Ideal for software development, research, and complex workflows requiring cross-session coordination and durable records.

Quick Start

Create a new Overseer task with full context, start, implement, and complete it with learnings.

Frequently Asked Questions about overseer

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

FAQPage Schema
How do I track context and blockers for multi-session software development tasks?

Multi-session task management persists context, blockers, and learnings across milestones, tasks, and subtasks using tickets that carry full decisions for seamless cross-session handoffs. It enforces a workflow API with context propagation and verifiable completion.

What is the best way to organize cross-session work into milestones and subtasks?

Organizing cross-session work involves breaking it into hierarchical milestones, tasks, and subtasks with context inheritance and learning bubbling. A workflow API manages the lifecycle through get, nextReady, start, complete, reopen, and delete operations.

Does VCS integration support task start and complete lifecycle operations?

VCS integration supports task start and complete operations to improve traceability and reliability. It ties version control actions to the task lifecycle, ensuring that context and learnings are captured during each phase of multi-session work.

How do I handle task blockers and ensure verification before completing work?

Blockers are tracked within task context, and verification-driven completion requires confirming work before marking tasks done. The workflow provides guidance for resolving blockers and enforces verifiable completion to maintain reliable task records.

Can I use context propagation for research workflows that span multiple sessions?

Context propagation suits research workflows requiring cross-session coordination and durable records. Persistent task context ensures decisions and learnings bubble up across hierarchies, enabling seamless handoffs for complex research efforts.

When should I not use a ticket-based task hierarchy for managing work?

Ticket-based task hierarchies are unnecessary for simple, single-session work that does not require context handoffs, blocker tracking, or verifiable completion. It is designed for complex workflows spanning multiple sessions that need durable records.