squad-kit 0.3.0 → 0.6.0

package/dist/console-ui/index.html

@@ -0,0 +1,16 @@
+<!doctype html>
+<html lang="en" class="dark">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <meta name="color-scheme" content="dark" />
+    <link rel="icon" href="/favicon.ico" sizes="any" />
+    <link rel="icon" href="/logo.svg" type="image/svg+xml" />
+    <title>squad console</title>
+    <script type="module" crossorigin src="/assets/index-Lxr-TdWe.js"></script>
+    <link rel="stylesheet" crossorigin href="/assets/index-BDlxrwaG.css">
+  </head>
+  <body>
+    <div id="root"></div>
+  </body>
+</html>

package/dist/console-ui/logo.svg

@@ -0,0 +1,18 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" width="64" height="64" role="img" aria-label="squad-kit">
+  <defs>
+    <linearGradient id="sk-arrow" x1="0" y1="0" x2="1" y2="1">
+      <stop offset="0%" stop-color="#7cffa0"/>
+      <stop offset="100%" stop-color="#4ade80"/>
+    </linearGradient>
+    <radialGradient id="sk-glow" cx="50%" cy="50%" r="50%">
+      <stop offset="0%" stop-color="#7cffa0" stop-opacity="0.18"/>
+      <stop offset="100%" stop-color="#7cffa0" stop-opacity="0"/>
+    </radialGradient>
+  </defs>
+  <rect x="1" y="1" width="62" height="62" rx="12" fill="#0a0a0c" stroke="#32323a" stroke-width="1.5"/>
+  <circle cx="32" cy="32" r="24" fill="url(#sk-glow)"/>
+  <circle cx="14" cy="32" r="2.75" fill="#7cffa0" fill-opacity="0.35"/>
+  <circle cx="22" cy="32" r="2.75" fill="#7cffa0" fill-opacity="0.65"/>
+  <circle cx="30" cy="32" r="2.75" fill="#7cffa0"/>
+  <path d="M38 21 L51 32 L38 43" fill="none" stroke="url(#sk-arrow)" stroke-width="3.25" stroke-linecap="round" stroke-linejoin="round"/>
+</svg>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "squad-kit",
-  "version": "0.3.0",
+  "version": "0.6.0",
   "author": "Momen Yasser <momenysr@gmail.com>",
   "description": "Plan once, execute cheap. A token-efficient, 3-step SDD workflow CLI (stories → plans → implementation).",
   "keywords": [
@@ -27,30 +27,42 @@
     "LICENSE"
   ],
   "scripts": {
-    "build": "tsup",
+    "build": "pnpm run build:ui && pnpm run build:cli && pnpm run verify:console",
+    "build:cli": "tsup",
+    "build:ui": "pnpm -C console-ui install --no-frozen-lockfile && pnpm -C console-ui build",
+    "clean": "rimraf dist console-ui/dist",
     "dev": "tsup --watch",
     "test": "vitest run",
     "test:watch": "vitest",
     "lint": "tsc --noEmit",
+    "verify:console": "tsx scripts/verify-console-build.ts",
     "verify:models": "tsx scripts/verify-models.ts",
-    "prepublishOnly": "pnpm run verify:models && pnpm build && pnpm test"
+    "size:guard": "tsx scripts/size-guard.ts",
+    "prepublishOnly": "pnpm run verify:models && pnpm build && pnpm test && pnpm size:guard"
   },
   "dependencies": {
+    "@hono/node-server": "^1.13.0",
     "@inquirer/prompts": "^7.2.0",
     "boxen": "^8.0.1",
     "commander": "^12.1.0",
+    "diff": "^7.0.0",
     "fs-extra": "^11.2.0",
     "gradient-string": "^3.0.0",
+    "hono": "^4.6.0",
     "ignore": "^6.0.2",
     "js-yaml": "^4.1.0",
     "kleur": "^4.1.5",
-    "ora": "^8.1.1"
+    "open": "^10.1.0",
+    "ora": "^8.1.1",
+    "zod": "^3.23.0"
   },
   "devDependencies": {
+    "@types/diff": "^7.0.0",
     "@types/fs-extra": "^11.0.4",
     "@types/gradient-string": "^1.1.6",
     "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.10.0",
+    "rimraf": "^6.0.1",
     "tsup": "^8.3.5",
     "tsx": "^4.19.3",
     "typescript": "^5.7.2",

package/templates/agents/claude-code/squad-plan.md

@@ -26,4 +26,5 @@ You are generating an agent-executable implementation plan for this project usin
 - **Planning only.** Do not modify application source code in this session.
 - **Concrete over clever.** File paths, line ranges, type names, function signatures, verification commands. No "consider" or "might".
 - **Respect existing conventions.** Read neighbouring plan files before inventing a new pattern.
+- If a plan file already starts with `<!-- squad-kit:`, **never change or remove that first line** when editing. New plans start with `# Story NN — …` per `generate-plan.md`; do not invent the API metadata comment. In later implementation sessions, treat the plan file as read-only unless the user explicitly asks to revise the plan.
 - Report back the path(s) you wrote and a one-line summary per file.

package/templates/agents/copilot/squad-plan.prompt.md

@@ -12,3 +12,5 @@ Generate an implementation plan using the squad-kit workflow.
 - Write the plan file to `.squad/plans/<feature-slug>/NN-story-<slug>[-<id>].md` and update `00-overview.md` / `00-index.md` as needed.
 
 Planning only. Do not modify application source code in this session.
+
+If a plan file already starts with `<!-- squad-kit:`, never change or remove that first line when editing (tooling / `squad list`). New plans start with `# Story NN — …` per `generate-plan.md`; do not fake the API metadata comment. In later implementation sessions, keep the plan file read-only unless the user explicitly asks to revise the plan.

package/templates/agents/cursor/squad-plan.md

@@ -24,3 +24,4 @@ You are generating an agent-executable implementation plan for this project usin
 - Planning only. Do **not** modify application source code in this session.
 - Concrete over clever. File paths, line ranges, type names, function signatures, verification commands.
 - Respect existing conventions — read neighbouring plan files first.
+- If a plan file already starts with `<!-- squad-kit:`, **never change or remove that first line** when editing the file. New plans you write start with `# Story NN — …` per `generate-plan.md`; do not fake the API metadata comment (only `squad new-plan --api` emits that header). In later **implementation** chats, treat the plan file as read-only unless the user explicitly asks to revise the plan.

package/templates/agents/gemini/squad-plan.toml

@@ -11,4 +11,6 @@ Steps:
 5. Write the plan file to .squad/plans/<feature-slug>/NN-story-<slug>[-<id>].md and update 00-overview.md / 00-index.md as needed.
 
 Planning only. Do not modify application source code in this session.
+
+If a plan file already starts with `<!-- squad-kit:`, never change or remove that first line when editing (tooling). New plans start with `# Story NN — …` per generate-plan.md; do not fake the API metadata comment. In later implementation sessions, keep the plan file read-only unless the user explicitly asks to revise the plan.
 """

package/templates/prompts/generate-plan.md

@@ -82,6 +82,9 @@ Every generated plan Markdown must follow this structure and tone.
 5. **Cross-feature links:** Use relative paths like `../other-feature/NN-story-….md`.
 6. **Index:** If introducing a **new** feature slug, add a row to `.squad/plans/00-index.md`.
 7. **Scope:** Produce planning Markdown only unless the user explicitly asks for code changes.
+8. **First-line metadata (`<!-- squad-kit: … -->`):** If an existing `NN-story-*.md` already begins (after any leading blank lines) with a single-line HTML comment `<!-- squad-kit: … -->`, **leave that first line unchanged** in every edit unless the user explicitly asks to change plan metadata. Do not replace it with status text, a title, or a different comment—`squad list` and other tooling read it. Status notes (*implementation complete*, etc.) belong in the body or elsewhere, not on that line.
+9. **New plan files you author here (e.g. copy-paste / in-agent planning):** Start the Markdown body with the **`# Story NN — …`** H1 from this document. Do **not** invent a `<!-- squad-kit: generated by … -->` line; only `squad new-plan --api` writes that exact header format.
+10. **Executor sessions (later):** When this plan is used for implementation (attach-only workflow), treat the plan file as **read-only** unless the user explicitly asks to revise the plan; implement in application sources and tests instead of rewriting the plan header.
 
 ---
 

package/templates/prompts/intake.md

@@ -18,8 +18,11 @@ This is **not** an implementation prompt. It is the input to the plan-generation
 ## Tracker (metadata only)
 
 - **Tracker type:** `{{trackerType}}`
-- **Work item id:** (used in filenames and plan tables; leave blank if tracker type is `none`)
-- **Work item type:** Story / Bug / Task / Chore / …
+- **Work item id:** `{{trackerWorkItemId}}` *(used in filenames and plan tables; fill manually if empty)*
+- **Work item type:** `{{trackerWorkItemType}}`
+- **Status:** `{{trackerStatus}}`
+- **Assignee:** `{{trackerAssignee}}`
+- **Labels:** `{{trackerLabels}}`
 
 External tracker links are **not** followed by the planner. Keep the id for naming and traceability only.
 
@@ -27,30 +30,30 @@ External tracker links are **not** followed by the planner. Keep the id for nami
 
 ## Title
 
-*(Paste the work item title verbatim.)*
+*(Paste the work item title verbatim. Prefilled when `squad new-story` fetched from a tracker.)*
 
 ```
-
+{{trackerTitle}}
 ```
 
 ---
 
 ## Description
 
-*(Paste the full work item description, including any formatting you rely on.)*
+*(Paste the full work item description. Prefilled when fetched from a tracker.)*
 
 ```
-
+{{trackerDescription}}
 ```
 
 ---
 
 ## Acceptance criteria
 
-*(Paste the acceptance criteria — checklist, bullets, Gherkin, whatever the tracker stores.)*
+*(Checklist, bullets, Gherkin, etc. Prefilled for Azure DevOps when the work item has acceptance criteria.)*
 
 ```
-
+{{trackerAcceptanceCriteria}}
 ```
 
 ---

package/templates/prompts/story-skeleton.md

@@ -2,6 +2,8 @@
 
 This file documents the structure of `NN-story-<slug>.md` plans that the planner produces. The planner reads `generate-plan.md`; this file exists so contributors can scan the target shape at a glance.
 
+When **`squad new-plan --api`** creates the file, the first line is often a single-line **`<!-- squad-kit: generated by … -->`** comment (tooling / `squad list`). **Preserve that line** when editing the plan; do not overwrite it with prose or a different comment unless the user explicitly asks to change metadata.
+
 ```md
 # Story NN — <title> (Story: <tracker-id?>)