squad-kit 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "squad-kit",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "author": "Momen Yasser <momenysr@gmail.com>",
   "description": "Plan once, execute cheap. A token-efficient, 3-step SDD workflow CLI (stories → plans → implementation).",
   "keywords": [
@@ -22,20 +22,37 @@
     "dist",
     "templates",
     "README.md",
+    "CHANGELOG.md",
+    "SECURITY.md",
     "LICENSE"
   ],
+  "scripts": {
+    "build": "tsup",
+    "dev": "tsup --watch",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "lint": "tsc --noEmit",
+    "verify:models": "tsx scripts/verify-models.ts",
+    "prepublishOnly": "pnpm run verify:models && pnpm build && pnpm test"
+  },
   "dependencies": {
     "@inquirer/prompts": "^7.2.0",
+    "boxen": "^8.0.1",
     "commander": "^12.1.0",
     "fs-extra": "^11.2.0",
+    "gradient-string": "^3.0.0",
+    "ignore": "^6.0.2",
     "js-yaml": "^4.1.0",
-    "kleur": "^4.1.5"
+    "kleur": "^4.1.5",
+    "ora": "^8.1.1"
   },
   "devDependencies": {
     "@types/fs-extra": "^11.0.4",
+    "@types/gradient-string": "^1.1.6",
     "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.10.0",
     "tsup": "^8.3.5",
+    "tsx": "^4.19.3",
     "typescript": "^5.7.2",
     "vitest": "^2.1.8"
   },
@@ -49,12 +66,5 @@
   "homepage": "https://github.com/AzmSquad/squad-kit#readme",
   "bugs": {
     "url": "https://github.com/AzmSquad/squad-kit/issues"
-  },
-  "scripts": {
-    "build": "tsup",
-    "dev": "tsup --watch",
-    "test": "vitest run",
-    "test:watch": "vitest",
-    "lint": "tsc --noEmit"
   }
-}
+}

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

@@ -8,14 +8,14 @@ You are generating an agent-executable implementation plan for this project usin
 
 - **Intake file path:** `$ARGUMENTS`
   - If empty, ask the user for the path to a story intake file (under `.squad/stories/`).
-- **Meta-prompt:** `.squad/prompts/generate-plan.md` — follow its instructions exactly.
+- **Meta-prompt:** `generate-plan.md` from the **installed squad-kit package** (`templates/prompts/` — not under `.squad/`; locate via `npm root -g`/your package manager under `squad-kit`, or run `squad new-plan <intake> --copy` to print the composed meta-prompt). Follow it exactly.
 - **Project config:** `.squad/config.yaml` — read `project.projectRoots`, `tracker.type`, `naming.includeTrackerId`, `naming.globalSequence`.
 
 ## Steps
 
-1. Read `.squad/prompts/generate-plan.md` completely. Treat it as your operating instructions for structure, tone, and output rules.
+1. Read `generate-plan.md` from the installed squad-kit package completely. Treat it as your operating instructions for structure, tone, and output rules.
 2. Read the intake file at `$ARGUMENTS`, plus any files in its `attachments/` directory that the intake references.
-3. Read one or two existing plan files under `.squad/plans/` (if any) to match established tone. If none exist, use `.squad/prompts/story-skeleton.md` as the structural reference.
+3. Read one or two existing plan files under `.squad/plans/` (if any) to match established tone. If none exist, use `story-skeleton.md` from the same `templates/prompts/` directory in the squad-kit package as the structural reference.
 4. Determine the next sequence number by scanning `.squad/plans/**/NN-story-*.md` for the highest `NN` (global sequence) or the highest within the target feature folder (per-feature sequence), per `config.yaml.naming.globalSequence`.
 5. Write the plan file to `.squad/plans/<feature-slug>/NN-story-<slug>[-<id>].md`.
 6. Update `.squad/plans/<feature-slug>/00-overview.md` with the new story row.

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

@@ -5,7 +5,7 @@ description: Generate an implementation plan from a squad-kit story intake file.
 
 Generate an implementation plan using the squad-kit workflow.
 
-- Read `.squad/prompts/generate-plan.md` and follow its instructions exactly.
+- Read `generate-plan.md` from the installed squad-kit package (`templates/prompts/`; not under `.squad/` — use `npm root -g`/your package manager path to `squad-kit`, or `squad new-plan <intake> --copy` for the composed prompt) and follow its instructions exactly.
 - Read the intake file provided by the user (under `.squad/stories/`) plus any referenced files in its `attachments/`.
 - Read `.squad/config.yaml` for tracker type and naming rules.
 - Scan `.squad/plans/**/NN-story-*.md` to determine the next global sequence number.

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

@@ -7,14 +7,14 @@ You are generating an agent-executable implementation plan for this project usin
 ## Inputs
 
 - **Intake file path:** `$ARGUMENTS` (if empty, ask the user for a path under `.squad/stories/`).
-- **Meta-prompt:** `.squad/prompts/generate-plan.md` — follow its instructions exactly.
+- **Meta-prompt:** `generate-plan.md` from the **installed squad-kit package** (`templates/prompts/` — not under `.squad/`; find it via `npm root -g`/your package manager next to `squad-kit`, or run `squad new-plan <intake> --copy` to print the composed meta-prompt on stdout). Follow it exactly.
 - **Project config:** `.squad/config.yaml` — read `project.projectRoots`, `tracker.type`, `naming.*`.
 
 ## Steps
 
-1. Read `.squad/prompts/generate-plan.md` completely. Treat it as your operating instructions for structure, tone, and output rules.
+1. Read `generate-plan.md` from the installed squad-kit package completely. Treat it as your operating instructions for structure, tone, and output rules.
 2. Read the intake file, plus any files in its `attachments/` directory that the intake references.
-3. Read one or two existing plan files under `.squad/plans/` (if any) to match established tone. If none exist, use `.squad/prompts/story-skeleton.md`.
+3. Read one or two existing plan files under `.squad/plans/` (if any) to match established tone. If none exist, use `story-skeleton.md` from the same `templates/prompts/` directory in the squad-kit package.
 4. Determine the next sequence number by scanning `.squad/plans/**/NN-story-*.md`, honouring `config.yaml.naming.globalSequence`.
 5. Write the plan file to `.squad/plans/<feature-slug>/NN-story-<slug>[-<id>].md`.
 6. Update the feature's `00-overview.md` and `.squad/plans/00-index.md` if it's a new feature slug.

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

@@ -4,7 +4,7 @@ prompt = """
 Generate an implementation plan using the squad-kit workflow.
 
 Steps:
-1. Read .squad/prompts/generate-plan.md and follow its instructions exactly.
+1. Read generate-plan.md from the installed squad-kit package (templates/prompts/; not under .squad/) and follow its instructions exactly.
 2. Read the intake file at the argument path (under .squad/stories/) plus any referenced files in its attachments/.
 3. Read .squad/config.yaml for tracker type and naming rules.
 4. Scan .squad/plans/**/NN-story-*.md to determine the next global sequence number.

package/templates/prompts/generate-plan.md

@@ -19,6 +19,7 @@ You are maintaining **agent-executable implementation plans** for this project.
 
 - Project roots: `{{projectRoots}}`
 - Primary language: `{{primaryLanguage}}`
+- Tracker type: `{{trackerType}}`
 - Existing plans in `.squad/plans/` — read one or two to match tone and file-oriented style.
 
 ## Story document pattern

package/templates/prompts/intake.md

@@ -6,7 +6,7 @@ Fill this template for each story you want planned. Keep it copy-paste-friendly:
 - Binaries (screenshots, PDFs, exports): put them in `attachments/` next to this file and list them below.
 - Do **not** rely on external links (tracker URLs, wiki, chat) — the planner cannot open them. Paste the content you want considered.
 
-This is **not** an implementation prompt. It is the input to `.squad/prompts/generate-plan.md`.
+This is **not** an implementation prompt. It is the input to the plan-generation meta-prompt bundled with squad-kit (`generate-plan.md` in the installed package).
 
 ---