@esneiderbravo/speclaw 0.1.2 → 0.1.4

package/dist/cli/commands/init.js

@@ -26,8 +26,7 @@ function detectProjectName(cwd) {
  * Interactive setup: pick agents and packs, scaffold, index, and print the handoff prompt.
  *
  * @param flags - Parsed flags; runs interactively on a TTY unless `--agents`, `--yes`, or
- *   `-y` is set. Honors `--project-name`, `--ticket-prefix`, `--team-language`, `--packs`,
- *   and `--no-index`.
+ *   `-y` is set. Honors `--project-name`, `--packs`, and `--no-index`.
  */
 export async function runInit(flags) {
     const cwd = process.cwd();
@@ -35,8 +34,6 @@ export async function runInit(flags) {
     const interactive = Boolean(process.stdin.isTTY) && !flags.agents && !flags.yes && !flags.y;
     let agents;
     let packs;
-    let ticketPrefix = flags["ticket-prefix"];
-    let teamLanguage = flags["team-language"];
     banner();
     if (interactive) {
         const answers = await clack.group({
@@ -56,13 +53,9 @@ export async function runInit(flags) {
                 initialValues: ["agents"],
                 required: false,
             }),
-            ticketPrefix: () => clack.text({ message: "Ticket prefix (optional, e.g. FAR)", defaultValue: "" }),
-            teamLanguage: () => clack.text({ message: "Team communication language", defaultValue: "English" }),
         }, { onCancel: () => process.exit(1) });
         agents = answers.agents;
         packs = answers.packs;
-        ticketPrefix = answers.ticketPrefix || undefined;
-        teamLanguage = answers.teamLanguage || undefined;
     }
     else {
         agents = list(flags.agents).length ? list(flags.agents) : ["claude"];
@@ -73,11 +66,7 @@ export async function runInit(flags) {
         ui.err(`Unknown agent(s): ${unknownAgents.join(", ")}. Known: ${AGENTS.map((a) => a.id).join(", ")}`);
         process.exit(1);
     }
-    const profile = {
-        project_name: projectName,
-        ...(ticketPrefix ? { ticket_prefix: ticketPrefix } : {}),
-        ...(teamLanguage ? { team_language: teamLanguage } : {}),
-    };
+    const profile = { project_name: projectName };
     // 1. Content + chosen agents, with a check per piece installed
     ui.step(`Setting up ${c.bold(c.cyan(projectName))}`);
     scaffold(cwd, profile, packs, agents);
@@ -109,6 +98,8 @@ export async function runInit(flags) {
     ui.plain();
     console.log(c.cream("Complete speclaw's foundation: analyze this repo and fill LAWS.md and " +
         "docs/standards/* with its real architecture, quality gates and conventions. " +
+        "Infer the working language and conventions from the repo itself — docstrings, " +
+        "commit messages, branch names, PR and ticket language — don't assume. " +
         "Start with init_project."));
     ui.plain();
     ui.info(`The dev-agents read those standards for your stack — filling them well makes them stack-aware.`);

package/dist/cli/commands/visualize.js

@@ -16,6 +16,7 @@ function openInBrowser(file) {
  * .speclaw/graph.html and open it.
  *
  * @param flags - `_[0]` optionally focuses on a node; `--depth`, `--limit`, `--no-open`.
+ * @throws Exits the process with code 1 if the index is missing or generation fails.
  */
 export async function runVisualize(flags) {
     const cwd = process.cwd();

package/dist/modules/compass/visualize.js

@@ -68,7 +68,15 @@ export function graphData(projectPath, opts = {}) {
         db.close();
     }
 }
-/** Write the interactive graph to <projectPath>/.speclaw/graph.html and return its path. */
+/**
+ * Build the graph and write it as an interactive HTML page to
+ * `<projectPath>/.speclaw/graph.html` (the gitignored index directory).
+ *
+ * @param projectPath - Absolute path to the project root.
+ * @param opts - Focus/depth/limit controlling which nodes are included.
+ * @returns The output path plus the shown/link/total counts for reporting.
+ * @throws If no Compass index exists yet.
+ */
 export function visualize(projectPath, opts = {}) {
     const data = graphData(projectPath, opts);
     const dir = path.join(projectPath, ".speclaw");
@@ -77,7 +85,14 @@ export function visualize(projectPath, opts = {}) {
     fs.writeFileSync(out, renderHtml(data));
     return { path: out, shown: data.nodes.length, links: data.links.length, total: data.total };
 }
-/** Render a self-contained, offline HTML page with an inline force-directed renderer. */
+/**
+ * Render the graph as a self-contained, offline HTML page: the data is embedded
+ * as JSON and drawn by an inline canvas force-directed renderer (no CDN, no
+ * dependencies).
+ *
+ * @param data - The nodes/links/totals to embed.
+ * @returns A complete HTML document as a string.
+ */
 export function renderHtml(data) {
     const payload = JSON.stringify(data);
     return `<!doctype html>
@@ -178,7 +193,7 @@ function draw(){
   }
   ctx.globalAlpha=1;
 }
-function loop(){ tick(); draw(); requestAnimationFrame(loop); } loop();
+function loop(){ tick(); draw(); requestAnimationFrame(loop); }
 
 // interaction
 let dragging=null, panning=false, lastX=0, lastY=0;
@@ -199,5 +214,7 @@ addEventListener('mousemove', e=>{
 addEventListener('mouseup', ()=>{ dragging=null; panning=false; });
 cv.addEventListener('wheel', e=>{ e.preventDefault(); const f=e.deltaY<0?1.1:0.9;
   const mx=e.clientX, my=e.clientY; ox=mx-(mx-ox)*f; oy=my-(my-oy)*f; scale*=f; }, {passive:false});
+
+loop(); // start once every declaration above is initialized (avoids the TDZ on 'dragging')
 </script></body></html>`;
 }

package/dist/modules/foundation/assets/docs/standards/base-standards.template.md

@@ -5,11 +5,16 @@ of layer or language. This is a law of the project — see [`../../LAWS.md`](../
 
 ## Languages
 
+The working language is **inferred from this repo's own conventions** — the
+language already used in docstrings, commit messages, branch names, and PR/ticket
+bodies. Match what the repo does; do not impose a language it doesn't use.
+
 - **Code, identifiers, comments, docstrings, commit messages, PR titles/bodies,
-  and technical docs**: the repo's artifact language (default English).
+  and technical docs**: the repo's artifact language (English unless the repo
+  clearly uses another).
 - **User-facing product copy**: as the product requires.
-- **Agent ↔ human communication** (review comments, thread replies, ticket
-  bodies): the team's working language ({{team_language}}). Technical terms
+- **Agent ↔ human communication** (review comments, thread replies): the same
+  language the team already uses in the repo's tickets and PRs. Technical terms
   stay in English within that prose — don't force-translate them.
 
 ## Commits & branches
@@ -25,8 +30,8 @@ of layer or language. This is a law of the project — see [`../../LAWS.md`](../
   edge cases, "why"). They never narrate history, restate the next line, or
   address the reviewer.
 - **Never** put ticket IDs, ticket text, or changelog narration
-  ("added for {{ticket_prefix}}-123", "fixed as part of…") in code or
-  docstrings. Traceability lives in the branch name, PR, and git history.
+  ("added for TICKET-123", "fixed as part of…") in code or docstrings.
+  Traceability lives in the branch name, PR, and git history.
 
 ## Dependencies
 

package/dist/modules/foundation/assets/docs/standards/conventions.template.md

@@ -6,23 +6,26 @@ Naming, branching, PR, and tracking conventions. A law of the project — see
 ## Branches
 
 - Pattern: `{{branch_pattern}}`
-- Branches without a tracker ticket reference must not be merged (except
-  explicitly scoped chores).
+- Follow the branch/ticket convention this repo already uses (inferred from its
+  existing branch names and history) — don't invent a new one.
 
 ## Pull requests
 
 - Title and body in the repo's artifact language, following the PR template.
-- The body references the tracker ticket ({{ticket_prefix}}-N) so it links.
-- The ticket lives in the PR title/body only — never in the code.
+- If the team uses a tracker, the body references its ticket so it links; the
+  ticket lives in the PR title/body only — never in the code.
 - CI must be green before requesting review.
 
 ## Tracker
 
-- Ticket prefix: `{{ticket_prefix}}`
-- New behavior, endpoints, schema changes, or UI flows get a ticket and a
-  spec change; one-line fixes need not.
-- Ticket ↔ PR traceability is mandatory: closing a ticket attaches its PR
-  (see the `close-ticket` skill).
+speclaw does not prescribe a ticket tool — each team configures its own. Follow
+whatever convention this repo already uses (inferred from its branches, PRs, and
+history); if there is none, leave tracker linkage to the team.
+
+- New behavior, endpoints, schema changes, or UI flows get a spec change;
+  one-line fixes need not.
+- Where a tracker is in use, ticket ↔ PR traceability is expected: closing a
+  ticket attaches its PR.
 
 ## Versioning & releases
 

package/dist/modules/foundation/register.js

@@ -16,8 +16,6 @@ const profileShape = {
     branch_pattern: z.string().optional().describe("e.g. 'feature/<ticket-id>-<slug>'"),
     commit_style: z.string().optional().describe("e.g. 'conventional commits, imperative, English'"),
     custom_laws: z.string().optional().describe("Extra markdown appended to LAWS.md — project-specific binding rules the analysis surfaced"),
-    ticket_prefix: z.string().optional().describe("Ticket prefix in the team's tracker, e.g. 'FAR'"),
-    team_language: z.string().optional().describe("The team's working language for posted communication (reviews, replies, tickets), e.g. 'Spanish'. Repo artifacts stay in the repo's own language. Defaults to English."),
     compass_hints: z.string().optional().describe("Markdown bullets with the repo's real entrypoints and common traces, inserted into docs/compass.md"),
     base_standards_extra: z.string().optional().describe("Markdown with any project-specific cross-cutting rules, appended to docs/standards/base-standards.md"),
     modules_table: z.string().optional().describe("Markdown table of the repo's real modules/bounded contexts + one-line responsibility, for docs/standards/architecture.md"),
@@ -38,9 +36,9 @@ export function registerFoundation(server) {
         return text({
             instructions: [
                 "1. Analyze the repository at projectPath and fill in every profile field below with REAL values from the codebase (read package.json / pyproject.toml / CI configs / README — do not invent).",
-                "2. The foundation is a set of GRANULAR standards under docs/standards/ (base, architecture, backend, frontend, testing, conventions, spec-workflow), bound by LAWS.md and referenced from CLAUDE.md/AGENTS.md. Fill their structured fields from the real repo: modules_table and layering_rules (architecture), backend_layers, frontend_layers, versioning_rules, and any base_standards_extra. Omit a field only when that standard genuinely doesn't apply to this stack.",
-                "3. Suggest packs: add stack packs whose 'detect' hints match dependencies you found; offer the rest. Ask the user which packs to install (the spec workflow is always installed).",
-                "4. If the 'workflow' pack is selected, ask the user for their tracker's ticket prefix and team working language.",
+                "2. The foundation is a set of GRANULAR standards under docs/standards/ (base, architecture, backend, frontend, testing, conventions, lawbook), bound by LAWS.md and referenced from CLAUDE.md/AGENTS.md. Fill their structured fields from the real repo: modules_table and layering_rules (architecture), backend_layers, frontend_layers, versioning_rules, and any base_standards_extra. Omit a field only when that standard genuinely doesn't apply to this stack.",
+                "3. Suggest packs: add stack packs whose 'detect' hints match dependencies you found; offer the rest. Ask the user which packs to install (the lawbook workflow is always installed).",
+                "4. Infer the working language and the branch/commit/tracker conventions from the repo itself — the language already used in docstrings, commit messages, branch names, and PR/ticket bodies. Do NOT ask the user or assume English; match what the repo does, and set branch_pattern/commit_style accordingly. speclaw does not prescribe a ticket tool — leave tracker linkage to the team's own convention.",
                 "5. Draft any custom_laws (extra binding rules for LAWS.md) from conventions you observed that the standard set doesn't cover.",
                 "6. Call the 'scaffold' tool with { projectPath, profile, packs }.",
                 "7. Follow the nextSteps returned by scaffold: complete the HTML-comment sections still left in docs/standards/*, then run the lawbook_init and compass_index tools (both built into speclaw — no external installs).",
@@ -50,7 +48,7 @@ export function registerFoundation(server) {
         });
     });
     server.registerTool("scaffold", {
-        description: "Write the speclaw setup into a project: the foundation (LAWS.md constitution + granular docs/standards/* + CLAUDE.md + AGENTS.md + docs/compass.md), the spec workflow (always), the selected tool packs, multi-IDE symlinks (.claude/.cursor/.codex/.agents), .mcp.json wiring for speclaw, and .gitignore for .speclaw/. Never overwrites existing files. Call init_project first.",
+        description: "Write the speclaw setup into a project: the foundation (LAWS.md constitution + granular docs/standards/* + CLAUDE.md + AGENTS.md + docs/compass.md), the lawbook workflow (always), the selected tool packs, multi-IDE symlinks (.claude/.cursor/.codex/.agents), .mcp.json wiring for speclaw, and .gitignore for .speclaw/. Never overwrites existing files. Call init_project first.",
         inputSchema: {
             projectPath: z.string().describe("Absolute path to the project"),
             profile: z.object(profileShape).describe("Project profile gathered by analyzing the repo"),

package/dist/modules/foundation/scaffold.js

@@ -19,7 +19,6 @@ const FOUNDATION_DEFAULTS = {
     frontend_layers: "",
     versioning_rules: "",
     documentation_extra: "",
-    team_language: "English",
 };
 /**
  * Render the foundation: walk the module's assets/, mirror its structure into

package/dist/modules/lawbook/assets/skills/draft/SKILL.md

@@ -32,7 +32,7 @@ the folder under `lawbook/changes/`.
 Create under `lawbook/changes/<name>/`:
 
 - **proposal.md** — the why, the what, non-goals, and whether migrations are
-  needed. Reference the tracker ticket ({{ticket_prefix}}-N) if there is one.
+  needed. Reference the team's tracker ticket if there is one.
 - **specs/<capability>/spec.md** — the delta spec for each affected capability.
   Use normative language and testable scenarios:
   ```markdown

package/dist/modules/tools/register.js

@@ -12,7 +12,7 @@ export function registerTools(server) {
         inputSchema: {},
     }, async () => text(loadPacks()));
     server.registerTool("add_pack", {
-        description: "Add a single pack to an already-initialized project, then refresh IDE symlinks. Pass template vars (organization, ticket_prefix, team_language, ...) if the pack needs them.",
+        description: "Add a single pack to an already-initialized project, then refresh IDE symlinks. Pass template vars (organization, ...) if the pack needs them.",
         inputSchema: {
             projectPath: z.string().describe("Absolute path to the project"),
             pack: z.string().describe("Pack name (see list_packs)"),

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "@esneiderbravo/speclaw",
-  "version": "0.1.2",
+  "version": "0.1.4",
   "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",