taskr

Automate task tracking and memory with CONTEXT, FINDING, and PROGRESS notes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/chadyi-king/mission-control-workspace --skill taskr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taskr
Source: https://github.com/chadyi-king/mission-control-workspace/tree/main/skills/taskr
Command: npx skills add https://github.com/chadyi-king/mission-control-workspace --skill taskr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Taskr solves the problem of keeping complex work visible, coordinated, and well-documented by providing an observable task and memory system that records progress, decisions, and context across sessions.

Core Features & Use Cases

  • Plan-create-execute-document workflow: break work into tasks, track status, and log notes across sessions.
  • Real-time progress visibility: dashboards reflect ongoing work for stakeholders and team members.
  • Durable memory system: persistent CONTEXT, FINDING, and PROGRESS notes to inform future work and decisions.
  • One-task-at-a-time execution: strict discipline to focus on a single task while expanding the task hierarchy.
  • MCP-based coordination: integrates with the MCP API to manage task state and notes across agents.

Quick Start

Install Taskr locally, configure your MCP credentials, then create a top-level task and start the get_task/update_task loop.

Frequently Asked Questions about taskr

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

FAQPage Schema
How do I track real-time progress across multi-step project workflows?

Real-time progress tracking across multi-step projects uses an observable task system with a plan-create-execute-document cycle, reflecting ongoing work on dashboards for stakeholders. It enforces a strict one-task-at-a-time execution model to maintain focus while expanding task hierarchies.

How does durable memory work for cross-session task management?

Durable memory for cross-session task management works by persisting CONTEXT, FINDING, and PROGRESS notes. These notes record decisions and context alongside task states, ensuring information survives across sessions to inform future work and maintain coordination.

What's the best way to coordinate tasks across agents using MCP?

Coordinating tasks across agents using MCP involves JSON-RPC-like messaging to manage task states and notes. It integrates with the MCP API to drive a get_task and update_task loop, ensuring synchronized execution and transparent progress visibility.

Can I use a plan-create-execute-document cycle for complex cross-role collaboration?

Yes, the plan-create-execute-document cycle supports complex cross-role collaboration by breaking work into observable tasks. It provides real-time visibility and durable notes, ensuring all roles remain coordinated and informed throughout the project lifecycle.

Why enforce a one-task-at-a-time execution model in task tracking?

A one-task-at-a-time execution model is enforced to maintain strict focus on the current work item while allowing the task hierarchy to expand. This prevents context switching and ensures progress notes accurately reflect the active task.

Do I need to configure MCP credentials for real-time task tracking?

Yes, you must configure MCP credentials locally to enable real-time task tracking. This setup connects the workflow to the MCP API, allowing the system to manage task states, coordinate agents, and record durable notes.