squad-kit 0.3.0 → 0.4.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "squad-kit",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "author": "Momen Yasser <momenysr@gmail.com>",
   "description": "Plan once, execute cheap. A token-efficient, 3-step SDD workflow CLI (stories → plans → implementation).",
   "keywords": [

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?>)