state-opslisted

# State-Ops — State Inspection Read the canonical SQLite state that fakoli-state maintains: project summary, task inventory, claim activity, dependency graph, conflict warnings, and filesystem reconciliation. This skill makes no mutations. --- ## When to Use - When orienting before starting a work session — run `status` first, always. - Before claiming a task — confirm the PRD is approved and the task is `ready`. - When a claim was interrupted and the state of the queue is unclear. - When multiple agents are active and conflict risk is non-trivial. - When a task shows as `blocked` and the blocker chain needs tracing. - When suspicious that orphan branches or stale packets exist on disk. - When reporting project progress to a human or another skill. State-ops is NOT for authoring or reviewing PRDs — use the `prd` skill. State-ops is NOT for generating plans or scoring tasks — use the `plan` skill. State-ops is NOT for claiming work or submitting evidence — use the `claim` and `execute` skills. This skill only reads. --- ## Prerequisites The project must have run `fakoli-state init` at least once. Check for the sentinel file: ```bash ls .fakoli-state/state.db 2>/dev/null || echo "MISSING: run fakoli-state init first" ``` If `.fakoli-state/state.db` does not exist, refuse to proceed and tell the caller to run: ```bash fakoli-state init --name "<project-name>" ``` Do not attempt to read state, list tasks, or call any other `fakoli-state` command until `state.db` is co