skills.rest
ashfulcra
ashfulcraCOMMUNITY
Explore all skills by this author →
GitHub

coordinator-discipline

Applies verification gates to multi-agent coordination rulings, merges, dispatches, and completion claims.

10|1|Updated May 21, 2026
Search Tags:#code review#verification gates#multi-agent coordination#task dispatch#agent fleet#merge discipline#incident correction
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill coordinator-discipline-ashfulcra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coordinator-discipline
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/coordinator-discipline
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill coordinator-discipline-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinators of multi-agent fleets routinely act on unverified claims, merge work whose approvals no longer match the artifact, dispatch tasks without durable records, and declare work done without evidence. This Skill provides a set of pre-action gates that force verification before each of those failure-prone actions. ## Core Features & Use Cases - Five action gates: checklists to run before ruling on anything, merging reviewed work, dispatching work to another agent, claiming something is done, and issuing corrections. - Cross-cutting measurement discipline: rules for truncated listings, liveness signals, contaminated controls, and fix-the-instance-leave-the-neighbour audits. - Use Case: Before merging a reviewed branch, a coordinator verifies the approved commit sha matches the PR head and remote branch tip, then writes a closure record carrying the merge sha so the settlement is backed by evidence rather than a tally cache. ## Quick Start Load the coordinator-discipline skill and walk the matching gate checklist before you rule, merge, dispatch, or claim completion on multi-agent work.

Frequently Asked Questions about coordinator-discipline

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

FAQPage Schema
How do I verify agent work before merging reviewed code?▼

Check that the approved artifact identity matches across every authoritative source at merge time: the approved commit sha, the PR head, and the remote branch tip must be byte-identical. Any change, including trivial conflict resolution, produces a new identity requiring a new approval round.

How should a coordinator dispatch tasks to other agents?▼

Send a durable task record plus a visible event, always include a body pointer for obligation-changing broadcasts, and require the assignee's first deliverable to be a STATE report covering what exists, what remains, blockers, and an estimate.

When should I trust a green CI check or passing test?▼

Only after proving the checker can fail: plant a defect, watch it go red, then remove it. Also run controls against the exact immutable snapshot that will be published, since verifying a state the check cannot see verifies nothing.

What evidence should a completion claim include?▼

A completion claim should be demonstrated, not reported: fetch the artifact, read back the record, or show the test failing when it should fail. Capability claims must state how they were verified or be marked UNVERIFIED.

How do I handle corrections after sending a wrong message to agents?▼

Send the correction to every surface the error reached at equal priority, naming the error and its consequence plainly. Correct before anyone acts if possible, mark actions already caused, and name your own defect in the corrective artifact.

Related Skills

Explore More Software Engineering Skills→
adelproadelpro
2

agent-team-orchestration

Coordinate multi-agent teams with defined roles and task lifecycle handoffs.

Community
Advanced
engineai-nzengineai-nz

checkpoint

Save and resume progress checkpoints for long-running iterative tasks.

Official
Basic
ether-moonether-moon

knowledge-gate

Query team-verified Knowledge Vault constraints through the knowledge-gate CLI before code planning.

Community
Intermediate
mvillmowmvillmow
18

verify-pr-ready

Verify GitHub pull requests for CI checks, approvals, and merge conflicts.

Community
Basic