fulcra-agent-directives

Direct, schedule, and track structured work assignments across agents with acks and re-notify.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-directives-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-agent-directives
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-agent-directives
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-directives-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple agents over a shared file-based inbox makes it easy to lose track of who owes what: freeform messages have no assignee, no priority, and no way to confirm receipt. This Skill adds structured directed work on top of a fulcra-agent-teams space so every directive is a task with an assignee, status machine, and per-agent acknowledgments. ## Core Features & Use Cases - Directed work verbs: Use tell, broadcast, remind, and later to assign tasks to one agent, all agents, a future time, or the backlog, with priority levels P0-P3. - Deterministic inbox with acks: Each agent gets a priority-sorted inbox fold; acking an item hides it and stops re-notify, while unacked P0/P1 items keep surfacing. - Intent capture and dropped-work detection: Record spoken commitments with intent and surface started-then-silent, blocked, or never-started work with the threads fold. - Use Case: An orchestrating agent wakes up, runs coord-engine inbox <team> -a <id> to check for unacked directives, acks completed items, then broadcasts a new P1 task to the team and schedules a reminder for a follow-up review. ## Quick Start Ask the agent to check its directive inbox for the team and acknowledge any completed assigned work before directing new tasks.

Frequently Asked Questions about fulcra-agent-directives

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

FAQPage Schema
How do I assign a task to another agent in a Fulcra team?

Use `coord-engine tell <team> <assignee> "<title>"` with optional priority `-p P0..P3`, summary, and next-action flags. The directive is written as a task doc with an assignee, so it appears in reconcile views and the assignee's inbox.

How does the per-agent inbox and acknowledgment work?

Run `coord-engine inbox <team> --agent <id>` to see open, unacked directives sorted by priority. Ack an item with `--ack <slug>`; acking writes a per-agent shard file that hides the item and stops re-notify for that agent only.

What is the difference between tell, broadcast, remind, and later?

`tell` assigns one agent, `broadcast` assigns every non-stale agent via assignee `*`, `remind` hides a directive until a given time (ISO or relative like 5d/36h/10m), and `later` files the item in the @backlog, visible only with `inbox --all`.

How do I capture a spoken commitment so it is not dropped?

Use `coord-engine intent <team> "<text>" --for user [--by <when>]` in the same turn the commitment is stated. Restating identical text dedupes, while a new `--by` updates the deadline in place; the `threads` fold surfaces intents that pass their window without follow-up.

What should I check before directing work if the engine might be broken?

Run `coord-engine doctor <team>` first; it must exit 0 with the last line exactly `doctor: healthy`. If it fails, fix engine or auth before directing or acking, since operations against a broken engine are unsafe.

What are the limitations of broadcast completion tracking?

A broadcast directive is complete only when every non-stale roster agent has acked, which requires fulcra-agent-presence to be installed. Without presence, acking still hides items per agent, but there is no roster-based completion signal.