@skeletiq/mcp 0.3.0 → 0.5.0

package/README.md

@@ -64,14 +64,14 @@ A token grants only what you tick. The server's tools need:
 |---|---|---|
 | `read` | Projects, designs, briefs, build order, readiness, gaps, jobs | `list_projects`, `get_design`, `get_generation_status` |
 | `generate` | Running generations — **that spends credits** — and payload critique, which is free | `generate_architecture`, `critique_architecture` |
-| `report` | Recording what got built. **Needs `read` as well** | `check_drift` |
+| `report` | Recording what got built, and asking a person to change a decision. **Needs `read` as well** | `check_drift`, `request_decision_change` |
 
 `read` alone is a good starting point: the agent can orient and build, but cannot spend anything.
 
 Two things the table above cannot say in a cell:
 
-- **`report` on its own does nothing.** `check_drift` looks the project and the version up before it
-  can report against them, and those lookups are `read`. A `report`-only token is refused.
+- **`report` on its own does nothing.** `check_drift` and `request_decision_change` look the project and the version up before
+  they can report against them, and those lookups are `read`. A `report`-only token is refused.
 - **`generate` without `read` still generates**, but the answer is thinner: the tool reads back the
   design it just created to describe it, and reports that failure as a thinner answer rather than a
   failed generation — telling an agent the generation failed would invite it to pay for the whole
@@ -85,11 +85,12 @@ change your provider keys, see billing, or delete your account, whatever scopes
 | Tool | What it does |
 |---|---|
 | `list_projects` | Find a project by name. Returns the candidates rather than guessing between them. |
-| `get_design` | Read a design, in one of six modes: `overview`, `component`, `brief`, `readiness`, `build_order`, `gaps`. Where a version records its requirements, `overview` and `component` resolve the design's `R`-ids to the requirements they name, and say what became of each. |
-| `generate_architecture` | Design a system from a prompt. Spends credits and takes minutes. |
+| `get_design` | Read a design, in one of nine modes: `overview`, `component`, `brief`, `todo`, `readiness`, `build_order`, `gaps`, `fitness`, `decisions`. `readiness` opens with a verdict-first headline ("22 of 24 met · Ready · score 87"). `fitness` lists the tests to write in your own repo and report through `check_drift`; `decisions` lists the version's decisions with what was chosen, why, and what was rejected. Where a version records its requirements, `overview` and `component` resolve the design's `R`-ids to the requirements they name, and say what became of each. |
+| `generate_architecture` | Design a system from a prompt. Spends credits and takes minutes. A prompt that states no load comes back with a question instead, and nothing is charged: ask your human, and answer "Not sure yet" when they do not know rather than guessing. |
 | `get_generation_status` | Poll a generation started with `wait: false`. |
 | `critique_architecture` | Check a design against SkeletIQ's rules. Deterministic, free, stores nothing. Tell it the `domain` and the `exposure`. |
 | `check_drift` | Report what you built; hear what is missing, half done, or not in the design. |
+| `request_decision_change` | Ask a person to change a design decision, or poll a request you filed. A person on the project reviews it in To-do; nothing changes until they accept. |
 
 ## How a session goes
 
@@ -114,8 +115,9 @@ unknown ids with suggestions, they are suggestions — put them to a person rath
 mapping.
 
 **`critique_architecture`'s optional inputs are not neutral.** Omitting one does not skip a
-question; it answers it. With no `domain` and `secondary_domains`, no compliance framework applies,
-so no compliance finding is possible and the score comes back higher than the SkeletIQ app shows
+question; it answers it. With no `domain`, no compliance framework applies (`secondary_domains`
+select none — they add that domain's design checks as advice — so name a framework when it must
+apply), so no compliance finding is possible and the score comes back higher than the SkeletIQ app shows
 for the same design — by up to 15 points. With no `exposure`, the design is assessed as
 internet-facing, which is how an air-gapped system gets told to add a CDN and a WAF. The response
 says what was actually used — `frameworks_checked` and `exposure_assessed` — and the text output