ground-checklisted

# Ground Check Before starting any task, verify what the codebase actually supports today. This skill bridges the gap between plans and executable reality. ## Usage ``` ground-check <task> ``` Where `<task>` is any of: - A track subtask: `A2` or `Track A, Ledger Store` - A task description: `"implement hook entrypoint dispatch"` - A design doc path: `docs/plan/TRACK_H_AGENT_BRIDGE/H1_STORE_AND_HOOKS.md` - An issue number: `#15` - A feature idea: `"add transcript cursor-based delta ingest"` ## What This Skill Does 1. **Reads the task** — understands what needs to be built 2. **Scans actual code** — checks what exists today in the codebase 3. **Reports readiness** — concrete findings, not theoretical analysis 4. **Identifies the gap** — when something isn't ready, names the specific missing piece ## Output Categories ### Ready (can start now) Infrastructure exists. You can start coding this today. - Required types/structs are defined - Required crate APIs are implemented (not stubs) - Required file store layout exists - Dependencies compile - Prerequisite work is done ### Almost (one piece away) 80%+ foundation exists, but one specific thing is missing. - Report EXACTLY what's missing (file, function, type, crate) - Estimate effort to fill the gap (trivial / small / medium) - Suggest: fill the gap first, or work around it? ### Not Ready (foundation missing) Prerequisite work hasn't been done yet. - Identify which prerequisite needs to be done first - Trace the depe