statecraft.
Catalog/spec-spine

053-plan-answers-the-whole-question

The plan answers the whole question, and names one pick

Lifecycle approvedImplementation completeVerification unknownQualification unknown

`registry plan` prints spec ids and a count. Every consumer needs more than that, so every consumer adds it back: adopters kept about forty lines of Python to join the ready ids against titles and to explain why each blocked spec is blocked, and the corpus's own `/next` skill has to make a second call to turn an id into something a human can read. The data is all there. `Plan` already carries each blocked spec's blockers with the state of each, and the registry it was computed from carries every title. This spec makes the prose form render what the structure already holds, and adds `--next`, the single pick that the one-spec-per-session loop actually asks for. The JSON shape gains title fields and is otherwise unchanged.

Read the full pinned specification ↗

Relationships

Claimed units

  • extends
    {
  "nature": "additive",
  "spec": "035-registry-plan-ready-set",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/query.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "002-registry-query",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/src/cmd_registry.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "035-registry-plan-ready-set",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/query.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "002-registry-query",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/lib.rs"
  }
}
  • extends
    {
  "nature": "additive",
  "spec": "035-registry-plan-ready-set",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/tests/cli.rs"
  }
}

Source headings

  1. 053: The plan answers the whole question, and names one pick
  2. 1. Purpose
  3. 2. Territory
  4. 3. Behavior
  5. 3.1 The prose form renders what the structure holds
  6. 3.2 `--next`
  7. 3.3 The JSON shape gains titles and nothing else
  8. 3.4 It still answers what is claimed, not what is done
  9. 4. Out of scope
  10. 5. Verification

Frozen anchors

No frozen anchors declared.