@esneiderbravo/speclaw 0.1.1 → 0.1.3

package/dist/server.js

@@ -1,7 +1,7 @@
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { registerCompass } from "./modules/compass/register.js";
-import { registerSpec } from "./modules/spec/register.js";
+import { registerSpec } from "./modules/lawbook/register.js";
 import { registerFoundation } from "./modules/foundation/register.js";
 import { registerTools } from "./modules/tools/register.js";
 /** Build the speclaw MCP server with every module's tools registered. */
@@ -9,7 +9,7 @@ export function buildServer() {
     const server = new McpServer({ name: "speclaw", version: "0.1.0" });
     // Each module contributes its own MCP tools. Adding a module = one line here.
     registerFoundation(server); // init_project, scaffold, configure_agent, doctor
-    registerSpec(server); // spec_init, spec_validate, spec_sync, spec_archive, spec_list
+    registerSpec(server); // lawbook_init, lawbook_validate, lawbook_sync, lawbook_archive, lawbook_list
     registerCompass(server); // compass_index, explore, search, recall, impact, trace, watch
     registerTools(server); // list_packs, add_pack
     return server;

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@esneiderbravo/speclaw",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "publishConfig": {
     "access": "public"
   },
-  "description": "Where specs become law. A self-contained MCP suite that turns any repo into a spec-driven, agent-ready project: its own constitution (foundation), its own local code graph (Compass), its own spec workflow (Spec), and opt-in skill packs (Tools). No external CLIs, no LLM to install.",
+  "description": "Where specs become law. A self-contained MCP suite that turns any repo into a spec-driven, agent-ready project: its own constitution (foundation), its own local code graph (Compass), its own spec-driven workflow (Lawbook), and opt-in skill packs (Tools). No external CLIs, no LLM to install.",
   "keywords": [
     "mcp",
     "mcp-server",

package/dist/modules/spec/assets/skills/sync/SKILL.md

@@ -1,21 +0,0 @@
----
-name: sync
-description: Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's spec module (draft → build → sync → archive).
----
-
-# sync — Promote delta specs to canonical
-
-Update the project's canonical specifications (`spec/specs/`) with a change's
-delta specs, without archiving the change. Use this when the specs should
-become the source of truth but the change isn't finished (e.g. multi-PR work).
-
-## Steps
-
-1. Confirm which change to sync (run `spec_list` if unsure).
-2. Run `spec_validate` for the change; do not sync a change whose specs are
-   invalid.
-3. Run the `spec_sync` tool for the change. It copies each
-   `spec/changes/<name>/specs/<capability>/spec.md` over the canonical
-   `spec/specs/<capability>/spec.md` and reports what it promoted.
-4. Report the promoted files to the user. The change stays active — `archive`
-   it when it's fully done.