What problem does it solve? Teams using SpecBind need a consistent, read-only answer to "where is this work now and what happens next" without manually inspecting spec.yaml, tasks.yaml, or roadmap files, which risks inconsistent or stale interpretations. ## Core Features & Use Cases - Milestone status reporting: Reads the active milestone projection to report stage, Task progress, recorded blockers, actionable items, and release blockers. - Single-Spec status reporting: Reads one named Spec's lifecycle state, Gate freshness, Task totals, next Tasks, and diagnostics. - Read-only boundary: Never approves, records progress, edits artifacts, or repairs state; it reports the recorded blocker condition and leaves remediation to the owning workflow. - Use Case: A developer asks "what should I do next on this milestone?" and receives a compact handoff covering completed work, blocked Tasks with recorded reasons, and the exact condition that must change. ## Quick Start Ask the assistant to report the current status of the active milestone or a named Spec using the sb-status skill.
