fulcra-agent-tasks

# Fulcra Agent Tasks Enhances the [`fulcra-agent-teams`](https://github.com/fulcradynamics/agent-skills) skill. Bare teams tracks long-running work as freeform `task/<name>.md`. This skill gives those docs a **typed lifecycle** — a real `status`/`priority`/`assignee` and a **validated state machine** — so a task's state is queryable (via `fulcra-agent-reconcile`) and can't take an illegal jump (e.g. `done → active`). Pairs with `fulcra-agent-reconcile`: this skill *writes* task state; reconcile *reads/heals* the views. ## Where to start — the re-entrancy probes Before creating or transitioning a task, probe engine health and what work is already waiting. Enter at the **first probe that fails** (per the repo's skill-quality pattern, `docs/skill-quality-pattern.md`); task writes are parse→modify→write and a same-status update is idempotent, so re-entry never corrupts state: | Probe (run in order) | Command | Passes when | If it fails, enter at | |---|---|---|---| | Engine + auth usable? | `coord-engine doctor <team>` | exits 0 and the last line is exactly `doctor: healthy` | fix engine/auth first (see Usage / fulcra-agent-reconcile) — do NOT write tasks against a broken engine | | Aggregate fresh? | `coord-engine status <team>` | output does NOT contain `(no aggregate for team/` (the CLI's missing-aggregate hint) | run `coord-engine reconcile <team>` to build the aggregate, then re-probe | | Work for me? | `coord-engine needs-me <team> --agent <id>` | prints `0 item(s) need...