What problem does it solve? Agents that hit a wall often park work silently, and the human operator never finds out — the workstream is forgotten. This Skill makes operator asks first-class state on the Fulcra coordination bus, has an orchestrating agent re-surface aging asks on every heartbeat, and delivers the operator's answer as a single atomic write that unblocks the task. ## Core Features & Use Cases - Raising asks: Any agent blocks a task on the operator with coord-engine task block <team> <slug> --on-user "<ask>", writing a self-contained question with options and a default. - Orchestrator nag loop: On each heartbeat, coord-engine asks <team> --json returns waiting asks oldest-first with age_hours, so the orchestrator surfaces new asks and re-surfaces stale ones past a nag threshold. - Atomic answer leg: coord-engine answer <team> <slug> --with "<answer>" records the answer, flips the task from blocked to active, returns it to its owner's queue, and strips the needs:human tag in one write. - Use Case: An orchestrating agent polls a fulcra-agent-teams space every heartbeat, notices a task blocked for 6 hours waiting on a vault choice, pings the operator in chat, and relays the reply so the owning agent resumes on its next wake. ## Quick Start Ask the agent to check for waiting operator asks in your Fulcra team by running coord-engine asks, then surface the oldest one and relay the operator's reply with coord-engine answer.
