@esneiderbravo/speclaw 2.0.1 → 2.0.2

package/dist/modules/lawbook/assets/agents/planner.md

@@ -13,6 +13,9 @@ Turn the explorer brief + user intent into a reviewable change under
 `lawbook/changes/<name>/` at the confirmed ceremony level. Prefer `draft` /
 `quick` skills.
 
+A complete explorer brief is the code map. Do not re-investigate it. Call
+Compass only for a gap the brief names.
+
 ## Questions
 
 If anything material is ambiguous, **stop**. Return numbered questions to the

package/dist/modules/lawbook/assets/skills/cortex/steps/02-dispatch-loop.md

@@ -3,6 +3,9 @@
 For the current Cortex stage (`cortex` action `brief` or `status`):
 
 1. Dispatch (spawn or adopt) the matching role with a clear handoff brief.
+   When the role is the planner, paste the explorer brief into the prompt
+   unchanged: symbols with files, callers and callees, blast radius, standards
+   already read, recommended approach, open questions, and gaps.
 2. On role completion, call the matching Cortex op:
    - exploring → `advance`
    - planning with questions → `advance` + `pauseForQuestions` + `openQuestions`

package/dist/modules/lawbook/assets/skills/draft/steps/02-understand.md

@@ -1,15 +1,18 @@
 # Understand the request and the code
 
-- **Refresh the index first.** Run `compass_index` before reasoning about the
-  code — it is incremental (unchanged files are skipped by hash), so this is
-  cheap and guarantees your decisions rest on the current graph, not a stale one.
+- When the handoff includes a complete explorer brief (symbols with files,
+  callers and callees, blast radius, standards already read, recommended
+  approach, open questions, and gaps), that brief is the code map. Call
+  `compass_find` or `compass_explore` only for a gap the brief names. Re-read
+  a file under `docs/standards/` only when the brief does not cite it.
+- When the handoff has no complete explorer brief, refresh the index with
+  `compass_index`, then use `compass_explore` and `compass_find` (mode:
+  concept) before grep/read to locate the code and its blast radius. Read the
+  governing standards in `docs/standards/`.
 - Clarify what the user wants (feature / fix / refactor) and confirm scope.
-- Use `compass_explore` and `compass_find` (mode: concept) (speclaw's code index) BEFORE
-  grep/read to locate the real code the change touches and its blast radius.
 - **Propose a ceremony level** with `lawbook_level` (mode `propose`) using the
-  paths/symbols you found; **confirm with the human** (mode `set`) before
-  writing artifacts. For an obvious one-liner, offer `speclaw quick` instead.
-- Read the governing standards in `docs/standards/` (architecture, backend,
-  frontend, testing) so the change complies with the project's law.
+  paths and symbols from the brief or from that locate pass; **confirm with the
+  human** (mode `set`) before writing artifacts. For an obvious one-liner,
+  offer `speclaw quick` instead.
 
 Next: read `steps/03-name-capabilities.md` and do only what it says.

package/dist/modules/lawbook/assets/skills/explore/steps/02-summarize.md

@@ -1,7 +1,15 @@
 # Summarize
 
-Produce a concise summary: the problem as understood, the constraints, the
-recommended approach, and the open questions. When the direction is clear,
-offer to `draft` the change.
+Produce a brief the planner can use as the code map. Include only these fields:
+
+- symbols, each with its file
+- callers and callees
+- blast radius
+- standards in `docs/standards/` already read
+- recommended approach
+- open questions
+- gaps: the phrase "nothing unresolved", or each symbol that is still unresolved
+
+When the direction is clear, offer to `draft` the change.
 
 No further steps remain — explore workflow complete.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@esneiderbravo/speclaw",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "publishConfig": {
     "access": "public"
   },