squad-kit 0.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Momen
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,140 @@
1
+ # squad-kit
2
+
3
+ **Plan once, execute cheap.** A 3-step SDD-style workflow CLI for AI-assisted coding: **raw story → good plan → implementation**.
4
+
5
+ Your expensive model plans once. A cheap model executes many times. Squad-kit owns the folder conventions, the plan meta-prompt, and the agent slash-commands so the token cost goes where it pays off.
6
+
7
+ ```
8
+ .squad/
9
+ ├── prompts/ # meta-prompts you can edit
10
+ ├── stories/<feature>/<id>/ # intake + attachments (one per story)
11
+ └── plans/<feature>/ # NN-story-<slug>.md (one per executable plan)
12
+ ```
13
+
14
+ ---
15
+
16
+ ## Why not Spec-Kit?
17
+
18
+ Both aim at spec-driven development. They make different bets.
19
+
20
+ | | squad-kit | Spec-Kit |
21
+ |---|---|---|
22
+ | Commands | `init`, `new-story`, `new-plan`, `status`, `list`, `tracker link` | `constitution`, `specify`, `clarify`, `plan`, `tasks`, `analyze`, `checklist`, `implement` |
23
+ | `/implement` turn starts with | one plan file (~5–15 KB) | 5–7 command templates + cross-artifact reads (~15–25 KB) |
24
+ | Model-tier awareness | Built into the philosophy (planner ≠ executor) | Not prescribed |
25
+ | Generated artifacts per story | `intake.md`, `NN-story-<slug>.md`, overview row | `spec.md`, `plan.md`, `data-model.md`, `contracts/`, `research.md`, `quickstart.md`, `tasks.md` |
26
+ | Customization | Prompts live in your repo as plain Markdown. Edit freely. | Template override stack with presets/extensions |
27
+ | Runtime | Node + TypeScript, npm-distributable | Python + `uv` |
28
+ | Scope | Intentionally small | Broad, with safety nets (`clarify`, `analyze`) |
29
+
30
+ Spec-Kit ships safety rails. Squad-kit ships the cheap path and gets out of the way. Pick squad-kit when your planner already produces trustworthy plans; pick Spec-Kit when you want the process to catch planning mistakes for you.
31
+
32
+ See [`docs/philosophy.md`](docs/philosophy.md) for the token math and [`docs/vs-spec-kit.md`](docs/vs-spec-kit.md) for the full comparison.
33
+
34
+ ---
35
+
36
+ ## Install
37
+
38
+ ```bash
39
+ npm install -g squad-kit
40
+ # or
41
+ pnpm add -g squad-kit
42
+ ```
43
+
44
+ Requires Node 18+.
45
+
46
+ ---
47
+
48
+ ## Quickstart
49
+
50
+ In your project root:
51
+
52
+ ```bash
53
+ squad init # interactive: tracker, agents, name
54
+ squad new-story auth --title "SSO support"
55
+ # → edit .squad/stories/auth/sso-support/intake.md (paste title, description, criteria)
56
+
57
+ # then, in your agent (Claude Code / Cursor / Copilot / Gemini):
58
+ /squad-plan .squad/stories/auth/sso-support/intake.md
59
+
60
+ # → produces .squad/plans/auth/01-story-sso-support.md
61
+
62
+ # implementation: new agent chat, attach ONLY the plan file.
63
+ # a cheap model can execute it end-to-end.
64
+ ```
65
+
66
+ No slash commands in your agent? Pipe the prompt directly:
67
+
68
+ ```bash
69
+ squad new-plan .squad/stories/auth/sso-support/intake.md # prints to stdout, copies to clipboard
70
+ ```
71
+
72
+ ---
73
+
74
+ ## Commands
75
+
76
+ | Command | What it does |
77
+ |---|---|
78
+ | `squad init` | Bootstrap `.squad/` with prompts, config, and agent slash-commands |
79
+ | `squad new-story <feature> [--id ID] [--title ...]` | Scaffold a story intake folder |
80
+ | `squad new-plan <intake-path>` | Compose the plan-generation meta-prompt with the intake inlined; print to stdout + copy to clipboard |
81
+ | `squad status` | Count stories/plans, show next global `NN`, warn on duplicates |
82
+ | `squad list [--feature <slug>]` | Table of stories + their plan state |
83
+ | `squad tracker link <story> <id>` | Attach or update a tracker id on an intake |
84
+
85
+ ---
86
+
87
+ ## Agent integration
88
+
89
+ At `squad init` you pick which agents get native slash commands. Supported:
90
+
91
+ - **Claude Code** → `.claude/commands/squad-plan.md`, `.claude/commands/squad-new-story.md`
92
+ - **Cursor** → `.cursor/commands/squad-*.md`
93
+ - **GitHub Copilot** → `.github/prompts/squad-plan.prompt.md`
94
+ - **Gemini CLI** → `.gemini/commands/squad-plan.toml`
95
+
96
+ Unsupported agents work fine too — `squad new-plan` prints the composed prompt on stdout.
97
+
98
+ ---
99
+
100
+ ## Trackers
101
+
102
+ Optional. Configure in `.squad/config.yaml`:
103
+
104
+ ```yaml
105
+ tracker:
106
+ type: linear # none | github | linear | jira | azure
107
+ naming:
108
+ includeTrackerId: true
109
+ globalSequence: true
110
+ ```
111
+
112
+ `--id` on `new-story` is validated against the tracker's id format (e.g. `ENG-42` for Linear, `843806` for Azure). No API calls in v0.1.
113
+
114
+ ---
115
+
116
+ ## What's *not* in v0.1
117
+
118
+ We ship lean on purpose. Current non-goals:
119
+
120
+ - Direct Anthropic/OpenAI API invocation (cost stays with your agent subscription)
121
+ - MCP server
122
+ - `/clarify`, `/analyze`, constitution-equivalent
123
+ - Tracker API calls (id validation only)
124
+ - Telemetry
125
+
126
+ Open to revisiting these for v0.2 based on usage.
127
+
128
+ ---
129
+
130
+ ## Tradeoffs to know
131
+
132
+ - **Quality depends on the planning model.** squad-kit has no safety-net commands. Use a strong model for `new-plan`.
133
+ - **Plans are project-coupled.** They reference real file paths. That is the point — do not expect portability between projects.
134
+ - **Global `NN` can collide on parallel branches.** Rebase-and-renumber is the resolution. Documented in [`docs/customization.md`](docs/customization.md).
135
+
136
+ ---
137
+
138
+ ## License
139
+
140
+ MIT. Contributions welcome — see [`CONTRIBUTING.md`](CONTRIBUTING.md).