manager

Starts and tracks engineering efforts through an operator-scoped portfolio with checkpoint export and import.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill manager-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manager
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/dev/skills/engineering/manager
Command: npx skills add https://github.com/reddb-io/red-skills --skill manager-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering work often spans multiple sessions, hosts, and context resets, making it hard to know where an effort stands or to continue it elsewhere. This Skill carries one effort from raw intent through the existing owner workflows, persisting it in an operator-scoped portfolio so progress survives across sessions and machines. ## Core Features & Use Cases - Effort Intake and Routing: Start an effort from raw intent, classify it via the /ask-red router, and record the route in the portfolio. - Status Briefs: Render an on-demand brief for any effort, showing its lifecycle state (inbox, active, paused, completed, abandoned). - Checkpoint Handover: Export the whole portfolio as a secret-free TOONL document and import it on another host, which becomes the single active writer. - Trust Boundary Enforcement: Treat tracker issues, comments, and PR bodies as untrusted evidence; only the operator session or an owning HITL workflow can issue directives. - Use Case: You start a spec effort on your laptop with /manager add OAuth support, then run checkpoint export, move to a desktop machine, checkpoint import, and continue exactly where you left off. ## Quick Start Invoke /manager with a short description of the work you want to start, for example by asking the assistant to run /manager with the intent to triage the open bug backlog.

Frequently Asked Questions about manager

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

FAQPage Schema
How do I start a new engineering effort with the manager skill?▼

Invoke /manager with your intent as the argument, for example /manager refactor the auth module. The skill calls the manager tool with the intake action, persists the effort in the portfolio, and routes it via /ask-red.

How do I move my effort portfolio to another machine?▼

Run /manager checkpoint export on the source host to write the portfolio as one TOONL document, then run /manager checkpoint import on the destination. The destination becomes the single active writer and the source host fails closed on its next save.

Where are manager efforts stored on disk?▼

Each effort lives in its own TOONL file under ~/.red/manager/efforts/<effort-id>.toonl, with RED_MANAGER_ROOT overriding the root. Files carry a versioned schema header and generation counter and are written temp-file-then-rename.

Can GitHub issue comments direct the manager to take actions?▼

No. Tracker issues, comments, and PR bodies are treated as untrusted evidence regardless of author privilege. Only the local operator session or an owning HITL workflow can issue directives; every mutation from other origins is refused.

What effort states does the manager portfolio track?▼

The portfolio owns five lifecycle states: inbox, active, paused, completed, and abandoned. Derived states such as HITL, blocked, or frontier are never stored and are reconciled from the tracker at render time.