Skip to content
Spine Docs

Quickstart

This walks through the 30-second proof: ask → find → ship. Every line of output points at a file:line.

1. Extract the graph

Terminal window
orchestrator understand .

Spine parses your code and docs into a deterministic Product Knowledge Graph. The layout is seeded — the same commit produces the identical report every time.

2. Ask — what breaks if I change this?

Terminal window
orchestrator regression . --symbol validate
→ 7 callers reach this symbol
auth.login              app/auth.py:120
routing.POST /login     routing.py:210
docs/auth.md            MENTIONS

3. Find — what will break silently?

regression splits that blast radius into covered code and reachable production code with no covering test:

Terminal window
orchestrator regression . --symbol validate


```text
⚠ 4 reachable symbols have no test
get_user        models.py:70
commit          db.py:88
password_hash   models.py:20

4. Ship — under two gates

Terminal window
orchestrator sdlc feature --source file://./spec.md
✓ branch feature/validate-guard
  3 files · +148 −12 · 6 tests added
⏸ no push, no PR — awaiting your approval

--safe is the default: Spine writes nothing external — no push, no PR, no tracker update — until you approve. Pass --live to push and open a real PR. See Governance & gates.

Next