by-role-manager-README

Coordinates Manager agent task prioritization across Paperclip and GitHub board workflows.

1|Updated Apr 27, 2026

Search Tags:#orchestration #Manager #task prioritization #release candidate #paperclip #github board #delivery proof

One-click install

npx skills add https://github.com/ControleOnline/agents-mcp --skill by-role-manager-readme-controleonline

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: by-role-manager-README
Source: https://github.com/ControleOnline/agents-mcp/tree/main/agents/skills/controleonline/by-role-manager-README
Command: npx skills add https://github.com/ControleOnline/agents-mcp --skill by-role-manager-readme-controleonline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It defines how the Manager agent orchestrates coordination tasks in Paperclip and subtasks for Developer, Security, and DevOps roles, preventing untracked work, repeated issues, and unauthorized GitHub board mutations. ## Core Features & Use Cases - Priority Pipeline: Enforces a strict P1-P7 execution order covering DevOps releases, hotfixes, documentation, Developer rejections, Security review, new development, and hygiene fallback. - Blocked Recovery Distinction: Separates GitHub board Blocked states (human-controlled) from Paperclip blocked status, which the Manager must investigate and recover with readback confirmation. - Delivery Proof Contract: Requires verifiable mutations (commits, label changes, column moves) before closing work, registering NEXT_ACTION when no new delta exists. - Use Case: A Manager agent starts a round, recovers a blocked Paperclip task, dispatches a Developer subtask from the Working column, validates the staging RC with Security acceptance, and moves the issue to Done. ## Quick Start Read this skill before running the Manager agent and follow its priority order to coordinate Paperclip tasks and GitHub board movements.

Frequently Asked Questions about by-role-manager-README

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

FAQPage Schema

When can the Manager move an issue to Done?▼

Done requires a published release candidate and Security acceptance with local test evidence. A task published to master without Security or local evidence stays open and returns to Working for a second validation round.