the-super-power-team 0.13.0 → 0.14.1

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.
@@ -1,10 +1,10 @@
1
1
  {
2
2
  "name": "team",
3
- "version": "0.13.0",
4
- "description": "Eight agents that take a ticket from idea to pull request, with your approval after every step. Nobody in the team commits, pushes or posts — you do.",
3
+ "version": "0.14.1",
4
+ "description": "Ten agents that take a ticket from idea to pull request — and tell the world about it, with your approval after every step. Nobody in the team commits, pushes or posts — you do.",
5
5
  "author": { "name": "Waleed Al Shaikhli" },
6
- "homepage": "https://github.com/al-shaikhli-w/Pit-Crew",
7
- "repository": "https://github.com/al-shaikhli-w/Pit-Crew",
6
+ "homepage": "https://github.com/al-shaikhli-w/the-super-power-team",
7
+ "repository": "https://github.com/al-shaikhli-w/the-super-power-team",
8
8
  "license": "MIT",
9
9
  "keywords": ["agents", "workflow", "tickets", "code-review", "qa", "linear", "github"]
10
10
  }
package/README.md CHANGED
@@ -1,6 +1,5 @@
1
- <!-- Generated from the repository README by scripts/build-npm-readme.js. Edit README.md, not this file. -->
2
1
  <p align="center">
3
- <img src="https://raw.githubusercontent.com/al-shaikhli-w/Pit-Crew/master/assets/mark-light.svg" alt="The Super Power Team" width="64" height="64">
2
+ <img src="https://raw.githubusercontent.com/al-shaikhli-w/the-super-power-team/master/assets/mark-light.svg" alt="The Super Power Team" width="64" height="64">
4
3
  </p>
5
4
 
6
5
  <h1 align="center">The Super Power Team</h1>
@@ -8,10 +7,10 @@
8
7
  <p align="center"><strong>An agent team for Claude Code that takes a ticket from idea to pull request — while you stay in the driver's seat.</strong></p>
9
8
 
10
9
  <p align="center">
11
- <img src="https://img.shields.io/badge/version-0.13.0-155eef?style=flat-square" alt="version 0.13.0">
10
+ <img src="https://img.shields.io/badge/version-0.14.1-155eef?style=flat-square" alt="version 0.14.1">
12
11
  <a href="https://www.npmjs.com/package/the-super-power-team"><img src="https://img.shields.io/npm/v/the-super-power-team?style=flat-square&color=155eef&label=npm" alt="npm package"></a>
13
12
  <img src="https://img.shields.io/badge/Claude%20Code-plugin-155eef?style=flat-square" alt="Claude Code plugin">
14
- <a href="https://github.com/al-shaikhli-w/Pit-Crew/blob/master/LICENSE"><img src="https://img.shields.io/badge/license-MIT-155eef?style=flat-square" alt="MIT license"></a>
13
+ <a href="https://github.com/al-shaikhli-w/the-super-power-team/blob/master/LICENSE"><img src="https://img.shields.io/badge/license-MIT-155eef?style=flat-square" alt="MIT license"></a>
15
14
  </p>
16
15
 
17
16
  <p align="center">
@@ -19,14 +18,17 @@
19
18
  <a href="#the-workflow">Workflow</a> |
20
19
  <a href="#live-dashboard">Dashboard</a> |
21
20
  <a href="#command-map">Commands</a> |
22
- <a href="https://github.com/al-shaikhli-w/Pit-Crew/blob/master/CHANGELOG.md">Changelog</a> |
23
- <a href="https://github.com/al-shaikhli-w/Pit-Crew/issues">Issues</a>
21
+ <a href="https://github.com/al-shaikhli-w/the-super-power-team/blob/master/CHANGELOG.md">Changelog</a> |
22
+ <a href="https://github.com/al-shaikhli-w/the-super-power-team/issues">Issues</a>
24
23
  </p>
25
24
 
26
- The Super Power Team gives Claude Code a crew of eight specialised agents — product
27
- manager, researcher, project manager, developer lead, QA engineer, independent
28
- reviewer, reply writer and agent maintainer. They work one ticket at a time,
29
- step by step, and stop after every step for your approval. Requirements, plans,
25
+ The Super Power Team gives Claude Code a crew of ten specialised agents — product
26
+ manager, researcher, security engineer, project manager, developer lead, QA
27
+ engineer, independent reviewer, reply writer, agent maintainer, and Rafi, the
28
+ social media manager who tells the world what you shipped. They work a
29
+ ticket step by step and stop after every step for your approval — or several
30
+ tickets at once, like a real team, with a pool of developers and QA engineers
31
+ that grows and shrinks by itself. Requirements, plans,
30
32
  QA evidence and the shared brief stay as readable files in your project instead
31
33
  of disappearing with the chat.
32
34
 
@@ -42,8 +44,11 @@ Start with the [Quick start](#quick-start) below.
42
44
 
43
45
  | | |
44
46
  | --- | --- |
45
- | **What it is** | A Claude Code plugin: eight agents, eleven commands, a live dashboard. |
46
- | **What it does** | Takes one ticket from idea → requirements → plan → code → QA → review → pull request. |
47
+ | **What it is** | A Claude Code plugin: ten agents, thirteen commands, a live dashboard. |
48
+ | **What it does** | Takes a ticket from idea → requirements → security check → plan → code → QA → review → pull request. Up to three tickets build at the same time. |
49
+ | **Security** | A security engineer writes `security.md` — your security to-do list — and checks every ticket before and after it is built. |
50
+ | **Marketing** | Rafi writes a marketing plan and drafts social media posts for every feature you ship — you publish them. |
51
+ | **Saves tokens** | Every agent is a sub-agent with a short brief; simple jobs run on a cheaper model. |
47
52
  | **Who decides** | You. The team stops after every step and waits for approve, change or stop. |
48
53
  | **What it never does** | Commit, push, open PRs, or write to your tracker. You run every git command yourself. |
49
54
  | **Where it keeps its work** | Plain markdown files in `.claude/team/` inside your project. |
@@ -56,21 +61,70 @@ Start with the [Quick start](#quick-start) below.
56
61
 
57
62
  ## Table of contents
58
63
 
59
- 1. [Why use it?](#why-use-it)
60
- 2. [Quick start](#quick-start)
61
- 3. [The workflow](#the-workflow)
62
- 4. [Parallel work](#parallel-work)
63
- 5. [Live dashboard](#live-dashboard)
64
- 6. [What do you need?](#what-do-you-need)
65
- 7. [Command map](#command-map)
66
- 8. [The team](#the-crew)
67
- 9. [Tickets](#tickets)
68
- 10. [File-backed project state](#file-backed-project-state)
69
- 11. [Review and verification](#review-and-verification)
70
- 12. [Rolling back](#rolling-back)
71
- 13. [Tool support](#tool-support)
72
- 14. [Status and updates](#status-and-updates)
73
- 15. [Support and contributing](#support-and-contributing)
64
+ 1. [Explained for kids](#explained-for-kids)
65
+ 2. [Why use it?](#why-use-it)
66
+ 3. [Quick start](#quick-start)
67
+ 4. [The workflow](#the-workflow)
68
+ 5. [Parallel work](#parallel-work)
69
+ 6. [Several tickets at once](#several-tickets-at-once)
70
+ 7. [Security](#security)
71
+ 8. [Marketing with Rafi](#marketing-with-rafi)
72
+ 9. [Models and tokens](#models-and-tokens)
73
+ 10. [Live dashboard](#live-dashboard)
74
+ 11. [What do you need?](#what-do-you-need)
75
+ 12. [Command map](#command-map)
76
+ 13. [The team](#the-crew)
77
+ 14. [Tickets](#tickets)
78
+ 15. [File-backed project state](#file-backed-project-state)
79
+ 16. [Review and verification](#review-and-verification)
80
+ 17. [Rolling back](#rolling-back)
81
+ 18. [Tool support](#tool-support)
82
+ 19. [Status and updates](#status-and-updates)
83
+ 20. [Support and contributing](#support-and-contributing)
84
+
85
+ ## Explained for kids
86
+
87
+ Imagine you want to build a big LEGO castle, and you have a team of helpers.
88
+ Each helper is good at **one** thing:
89
+
90
+ | Helper | What they do — like in a LEGO team |
91
+ | --- | --- |
92
+ | 📋 **Product manager** | Listens to your wish and writes down exactly what the castle needs: "a tower, a gate, a bridge". |
93
+ | 🔎 **Researcher** | Looks at the bricks you already have and says: "Yes, we can build that" — or "we are missing blue bricks". |
94
+ | 🛡️ **Security engineer** | The castle guard. Checks that no door is left open, no key is lying around, and nobody can sneak in. They keep a list of everything that still needs a lock — that is `security.md`. |
95
+ | 🗺️ **Project manager** | Cuts the big job into small steps: "first the wall, then the tower". |
96
+ | 🧱 **Developer** | Builds it, one step at a time. |
97
+ | ✅ **QA engineer** | Tests everything: does the gate open? does the tower stand? They only say "it works" when they have *seen* it work. |
98
+ | 👀 **Reviewer** | A friend who was not there while you built. They look with fresh eyes and spot what everyone else missed. |
99
+ | ✉️ **Reply writer** | Writes nice answers when other people leave comments. |
100
+ | 🔧 **Agent maintainer** | Keeps the team's notebook up to date. |
101
+ | 📣 **Rafi, social media** | When the castle is finished, Rafi tells everyone about it: Rafi writes the posters and the posts ("Come see our new tower!") and makes a plan for who to tell, where and when. Rafi only *writes* them — you decide if they go up on the wall. |
102
+
103
+ **You are the boss.** After every step the team stops and asks you:
104
+ "Is this OK?" You say **yes**, **change it**, or **stop**. Nobody moves on
105
+ without your yes.
106
+
107
+ **Many castles at once.** If you have three castles to build, you do not
108
+ want one builder doing them one after another. So the team brings more
109
+ builders — up to three — and gives each one **their own table** (a "worktree").
110
+ Builders never take bricks from another builder's table. If two castles need
111
+ the *same* special brick, the second builder waits until the first one is
112
+ done, so nobody fights over it. When there is no more work, the extra
113
+ builders go home. Testers work the same way.
114
+
115
+ **Saving energy.** Every helper costs a bit of energy (we call it "tokens").
116
+ Easy jobs, like writing a short reply, go to a quicker helper who uses less
117
+ energy. Hard jobs, like building or guarding the castle, go to the strongest
118
+ helper.
119
+
120
+ **Telling the world.** A great castle nobody knows about is a lonely castle.
121
+ After every finished piece, Rafi writes the news for you — but never
122
+ shares secrets, never talks about unfinished parts, and never posts anything
123
+ alone.
124
+
125
+ **Nobody touches your treasure.** The team never saves, sends or publishes
126
+ anything by itself (no `git commit`, no `git push`). It hands you the
127
+ commands, and *you* press the button.
74
128
 
75
129
  ## Why use it?
76
130
 
@@ -80,16 +134,22 @@ one long chat, and when "done" or "tested" is not backed by output.
80
134
  The Super Power Team adds a controlled loop:
81
135
 
82
136
  - **One role per step.** A product manager writes requirements, a researcher
83
- checks feasibility in the code first, a project manager plans, a developer
84
- lead builds, a QA engineer verifies. Each one has its own instructions and
137
+ checks feasibility in the code first, a security engineer checks the risks,
138
+ a project manager plans, a developer lead builds, a QA engineer verifies. Each one has its own instructions and
85
139
  limits.
86
140
  - **You approve every step.** Approve, change or stop — a yes covers one step,
87
141
  never the next.
88
142
  - **A shared brief.** Agents never see each other's conversations. One page per
89
143
  ticket, `00-brief.md`, keeps them in the same direction: the goal, your
90
144
  decisions, the constraints and the notes they leave for each other.
91
- - **Proof before PASS.** QA runs the CI gate, the local review, a code review
92
- and a security review, and reports PASS only with the output that proves it.
145
+ - **Proof before PASS.** QA runs the CI gate, the local review and a code
146
+ review; the security engineer runs the security review. PASS only comes with
147
+ the output that proves it.
148
+ - **Security from day one.** On a project with code, setup writes
149
+ `security.md`: what the system protects, where its doors are, and a security
150
+ to-do list you can read and fix item by item.
151
+ - **A real team.** Several tickets at once, each on its own git worktree, with
152
+ developers and QA engineers added and removed as the work needs them.
93
153
  - **Fresh eyes.** After QA, an independent reviewer who sees only the
94
154
  requirements and the diff checks the work again.
95
155
  - **Your git, your tracker.** The crew hands you every git command instead of
@@ -159,11 +219,12 @@ Setup asks one question at a time, in your language:
159
219
  only here, or none — and whether to keep a local board too.
160
220
  4. **Independent review** and the **live dashboard**.
161
221
  5. **The project** — with code, the researcher reads it and writes
162
- `project-tech.md`; without code, a short interview turns your idea into
163
- `project-info.md`. Either way you get `project-plan.md`, the features in
164
- order. You approve each document.
165
- 6. **Branch names, CI command and git** — whether the crew's files stay local,
166
- are shared, or are committed. It writes only ignore lines.
222
+ `project-tech.md`, and the security engineer scans it and writes
223
+ `security.md`, your security to-do list; without code, a short interview
224
+ turns your idea into `project-info.md`. Either way you get
225
+ `project-plan.md`, the features in order. You approve each document.
226
+ 6. **Branch names, CI command, worktree setup and git** — whether the crew's
227
+ files stay local, are shared, or are committed. It writes only ignore lines.
167
228
  7. **Doctor** — a quick check that ends with one line, or with the problems and
168
229
  their fixes.
169
230
 
@@ -187,6 +248,11 @@ Learn these three commands first:
187
248
  /team-work <ticket> -> /team-work pr -> /team-status
188
249
  ```
189
250
 
251
+ ![One ticket, step by step: 1 the product manager writes the requirements; 2 the researcher and the security engineer check feasibility and threats side by side; 3 the project manager plans; you create the branch; 4 the developer lead builds one task at a time; 5 QA and the security engineer check side by side; 5b an independent reviewer looks with fresh eyes; 6 you commit, push and open the PR; after the merge Rafi drafts the posts. You approve after every step; a FAIL goes back to the build.](https://raw.githubusercontent.com/al-shaikhli-w/the-super-power-team/master/assets/workflow.png)
252
+
253
+ <details>
254
+ <summary>Text version</summary>
255
+
190
256
  ```text
191
257
  /team-work ABC-123
192
258
  │
@@ -194,33 +260,42 @@ Learn these three commands first:
194
260
  1 product-manager requirements ✋ approve
195
261
  │
196
262
  2 researcher feasibility ✋ approve
197
- │ not feasible → 1
263
+ security-engineer threat check (one approval for both)
264
+ │ not feasible / not safe → 1
198
265
  3 project-manager plan ✋ approve
199
266
  │
200
267
  ├─ you create the branch
201
268
  │
202
269
  4 developer-lead one task at a time ✋ each task
203
270
  │
204
- 5 qa-engineer CI, reviews, security
205
- │ FAIL → 4
271
+ 5 qa-engineer CI, local + code review
272
+ security-engineer security review
273
+ │ any FAIL → 4
206
274
  5b reviewer requirements + diff
207
275
  │ changes → 4
208
276
  6 hand-over PR title + commit
209
277
  │
210
278
  ▼
211
279
  you commit, push and open the PR
280
+ │
281
+ ▼
282
+ ★ social-media Rafi drafts posts after the merge
212
283
  ```
213
284
 
285
+ </details>
286
+
214
287
  Every ✋ is a stop: nothing moves on until you approve. Each step has a narrow job:
215
288
 
216
289
  | Step | Who | Saved as | You do |
217
290
  | --- | --- | --- | --- |
218
291
  | 1 Requirements | product-manager reads the ticket, comments, linked tickets | `01-requirements.md` | approve |
219
292
  | 2 Feasibility | researcher reads the code, runs existing tests | `02-research.md` | approve |
293
+ | 2 Threat check | security-engineer: what this ticket changes for security, and the rules the build must follow | `02-security.md` | approve (with feasibility) |
220
294
  | 3 Plan | project-manager splits the work into tasks | `03-plan.md` | approve |
221
295
  | — Branch | the coordinator gives you the commands | noted in `03-plan.md` | run them, say "done" |
222
296
  | 4 Build | developer-lead, one task at a time | `04-implementation.md` | approve each task |
223
- | 5 QA | qa-engineer runs the four checks | `05-qa.md` | read the verdict |
297
+ | 5 QA | qa-engineer runs CI, local review and code review | `05-qa.md` | read the verdict |
298
+ | 5 Security review | security-engineer checks every rule from step 2 and the diff | `05-security.md` | read the verdict |
224
299
  | 5b Independent review | reviewer, who never saw the plan, the build or QA's report | `05b-review.md` | pick which findings to fix |
225
300
  | 6 Hand-over | the coordinator | `06-pr.md` | commit, push, open the PR |
226
301
  | 7 PR rounds | `/team-work pr` — QA reads new comments and checks | `07-pr-rounds.md` | approve the fixes, post the drafted replies |
@@ -237,8 +312,120 @@ you the commands for your shell.
237
312
  At the start of a ticket the crew asks: **one agent at a time** or **several in
238
313
  parallel**. With several, the researcher reads the code while the requirements
239
314
  are written, build tasks that touch different files run at the same time, and
240
- the four QA checks run side by side. Approvals never run in parallel — you
241
- still decide after every step.
315
+ the QA checks and the security review run side by side. Approvals never run
316
+ in parallel — you still decide after every step.
317
+
318
+ ## Several tickets at once
319
+
320
+ Name more than one ticket and the crew works like a real team:
321
+
322
+ ```text
323
+ /team-work RB-12 RB-13 RB-14
324
+ ```
325
+
326
+ ![Several tickets, one team: tickets move from Planning (max 3) to Building (one developer per ticket, max 3) to Checking (QA plus security, max 3) to Hand-over, where you open the PR and Rafi drafts the posts. RB-14 waits because it changes the same file as RB-12. Every developer has their own worktree, and you decide one question at a time.](https://raw.githubusercontent.com/al-shaikhli-w/the-super-power-team/master/assets/several-tickets.png)
327
+
328
+ <details>
329
+ <summary>Text version</summary>
330
+
331
+ ```text
332
+ planning building checking
333
+ ┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
334
+ │ product manager │ │ Developer 1 RB-12│ │ QA 1 + security │
335
+ │ researcher │ ──▶ │ Developer 2 RB-13│ ──▶ │ QA 2 + security │ ──▶ you open the PRs
336
+ │ security engineer│ │ (free) │ │ (free) │
337
+ │ project manager │ └──────────────────┘ └──────────────────┘
338
+ └──────────────────┘ RB-14 waits for RB-12 — same file
339
+ ```
340
+
341
+ </details>
342
+
343
+ | What | How it works |
344
+ | --- | --- |
345
+ | **Stages** | Planning (requirements, feasibility, threat check, plan) → Ready → Building → Checking (QA, security review, independent review) → Hand-over. |
346
+ | **Grows and shrinks by itself** | A ticket whose plan is approved gets a developer as soon as a place is free; a ticket whose build is done gets a QA engineer and a security engineer. When a ticket leaves a stage its place is free again. You never set the size. |
347
+ | **Limits** | At most 3 tickets in planning, 3 developers and 3 QA engineers — `## Team size` in `team.md`. The limits count tickets, not agents. |
348
+ | **Isolation** | Every developer and QA engineer works on one ticket only and never sees another. Each ticket gets its own **git worktree** — a second checkout of the repository in its own folder, on its own branch. |
349
+ | **Same files** | Before a ticket starts building, the crew compares the files in its plan with every ticket still open. If two change the same file, the second **waits** until the first one's PR is merged, so you never get a merge conflict. `RB-14 go anyway` overrides it. |
350
+ | **Your approvals** | Still one question at a time, each tagged with its ticket: `[RB-13] Task 2 is done — approve it?`. Answer with the ticket: `RB-13 approve`. |
351
+ | **Worktree commands** | The crew never runs git. It gives you the commands — `git worktree add …`, then your setup command such as `npm ci` — and `git worktree remove …` after the merge. |
352
+ | **Names** | `/team-names` can give the pool several names: `developer-lead → Omar, Sami, Lina`. |
353
+ | **Stop one** | `stop RB-13` pauses only that ticket; `/team-work RB-13` resumes it. |
354
+
355
+ One ticket — `/team-work RB-12` — works exactly as before: no worktree, your
356
+ normal branch.
357
+
358
+ ## Security
359
+
360
+ The **security engineer** looks after the whole system and every ticket.
361
+
362
+ | When | What it does | File |
363
+ | --- | --- | --- |
364
+ | **Setup** (project has code) or `/team-security` | Reads the whole project: secrets in files, dependency advisories (with your package manager's own audit command), login and access checks, input handling, personal data, configuration, CI. | `.claude/team/project/security.md` |
365
+ | **Step 2 — threat check** | What this ticket changes for security, and the rules the build must follow. The rules go into the ticket's brief, and the plan turns each one into a task. | `02-security.md` |
366
+ | **Step 5 — security review** | Checks every rule against the diff, looks for new problems, runs the audit again when dependencies changed. Any FAIL goes back to the build. | `05-security.md` |
367
+
368
+ `security.md` is **your security to-do list**:
369
+
370
+ ```markdown
371
+ ## TODO
372
+ - [ ] SEC-1 · high · Stripe key in the repository — src/config.ts:4 — move it to an env variable and rotate it — S
373
+ - [ ] SEC-2 · medium · Any signed-in user can delete any recipe — api/recipes.ts:88 — check the owner — S
374
+ - [x] SEC-3 · low · No rate limit on login — api/auth.ts:12 — add one — M — fixed 2026-11-22 (SEC-3, PR #41)
375
+ ```
376
+
377
+ | Command | What it does |
378
+ | --- | --- |
379
+ | `/team-security` | Scan again: keeps every id, ticks what is fixed, adds what is new. |
380
+ | `/team-security list` | The open items, most dangerous first. |
381
+ | `/team-security fix SEC-2` | Works the item as a normal ticket; it is ticked when the PR is merged. |
382
+ | `/team-security accept SEC-4 <reason>` | Records a risk you accept on purpose. |
383
+
384
+ Problems found outside a ticket never block it — they go on the list. The
385
+ security engineer never attacks a running system, never scans hosts, never
386
+ shows a secret's value, and never edits your code. `security.md` lists your
387
+ weak spots: if your repository is public, keep it out of git (setup offers
388
+ this).
389
+
390
+ ## Marketing with Rafi
391
+
392
+ **Rafi** (`team:social-media`) is the team's social media manager, turning
393
+ what the team ships into posts people want to read.
394
+
395
+ | When | What Rafi does | File |
396
+ | --- | --- | --- |
397
+ | `/team-social` | The **marketing plan**: who the project is for, the one-sentence message, the best channels (X, LinkedIn, Instagram, TikTok, Reddit, Product Hunt, a newsletter…), a 30-day post calendar, the next launch moments and the numbers to watch. You approve it. | `.claude/team/marketing/marketing-plan.md` |
398
+ | A ticket is merged | **Feature posts**: one draft per channel — a hook, the user's benefit, a call to action, and an image or video idea. `Social posts` in `team.md`: `after merge`, `ask` (default) or `off`. | `marketing/posts/<date>-<ticket>.md` |
399
+ | `/team-social post RB-12` | Posts for one shipped ticket, any time. | same |
400
+ | `/team-social week` | A **weekly round-up** of everything shipped in the last seven days, plus a newsletter paragraph. | `marketing/posts/<date>-week.md` |
401
+ | `/team-social list` | Every draft with its status (`draft`, `posted`) and the next calendar rows. | — |
402
+
403
+ Rafi **only drafts** — never posts, schedules, sends or messages anyone —
404
+ you publish, then set the draft to `posted`. Rafi writes only about features
405
+ that are merged, and never mentions security findings, open tickets, internal
406
+ links, or customer and colleague names. Rename Rafi with `/team-names`.
407
+
408
+ ## Models and tokens
409
+
410
+ Every agent is a **sub-agent**: it starts with a clean context and gets only
411
+ the brief, the file names and its job. The coordinator never pastes file
412
+ contents and never reads diffs itself, so your main session stays small.
413
+
414
+ Simple jobs run on a cheaper model, hard ones on yours. `## Models` in
415
+ `team.md`:
416
+
417
+ | Agent | Job | Model |
418
+ | --- | --- | --- |
419
+ | reply-writer | all | haiku |
420
+ | social-media (Rafi) | all | sonnet |
421
+ | agent-maintainer | all | haiku |
422
+ | researcher | all | sonnet |
423
+ | qa-engineer | CI gate, local review, PR round check | sonnet |
424
+ | qa-engineer | code review | your model |
425
+ | security-engineer, product-manager, project-manager, developer-lead, reviewer | all | your model |
426
+
427
+ Change any row. A job that turns out too hard for its model is run once more
428
+ on your model, and the crew says so.
242
429
 
243
430
  ## Live dashboard
244
431
 
@@ -246,7 +433,7 @@ See every agent, every ticket and everything that waits for you in one page in
246
433
  your browser. It refreshes every 4 seconds, works offline, and needs no server
247
434
  or install.
248
435
 
249
- ![The Super Power Team dashboard: a question waiting for approval, the commands ready to commit, and a ticket's workflow with the independent reviewer working and its live panel](https://raw.githubusercontent.com/al-shaikhli-w/Pit-Crew/master/assets/dashboard-live.png)
436
+ ![The Super Power Team dashboard: a question waiting for approval, the commands ready to commit, and a ticket's workflow with the independent reviewer working and its live panel](https://raw.githubusercontent.com/al-shaikhli-w/the-super-power-team/master/assets/dashboard-live.png)
250
437
 
251
438
  ```text
252
439
  /team-dashboard
@@ -256,7 +443,10 @@ or install.
256
443
  | --- | --- |
257
444
  | **Needs you** | The crew's open question with Approve, Change and Stop buttons that copy your answer. |
258
445
  | **Ready to commit** | The commit message and every command — stage, commit, push, PR — each with a copy button. The page never runs anything. |
259
- | **Workflow** | Each ticket's steps as connected nodes; the running agent glows with what it does this second. Click a step for its agent's panel: task, timer, every step, files changed and read, and its final report. |
446
+ | **Workflow** | Each ticket's steps as connected nodes, with the security engineer under Research (threat check) and QA (security review) and Rafi under PR (posts); the running agent glows with what it does this second. Click a step for its agent's panel: task, timer, every step, files changed and read, and its final report. |
447
+ | **Team** | With several tickets: each developer and QA engineer with the ticket and step they are on, the free places, and the tickets waiting for another one. |
448
+ | **Security** | Your security to-do list from `security.md`: open items by severity with a **Fix** button (copies `/team-security fix SEC-<n>`), accepted risks and fixed items. A counter in the workflow bar turns red when an item is high. Only titles are shown — never the fix or a secret. |
449
+ | **Marketing** | Rafi's marketing plan and its one-sentence message, the next days on the post calendar, and every post draft with its channels and status (`draft` or `posted`). |
260
450
  | **Timeline** | The last 30 minutes as bars, or Today, Week, Sprint and All projects as a heat map per agent. |
261
451
  | **Tickets** | What is in progress, the list for Today, Week or Sprint, and what is next on the plan — each with a Start button. |
262
452
  | **Board** | Your local tickets in four columns: Plan, Do, Check, Done. |
@@ -276,6 +466,11 @@ and only while the dashboard is on. `/team-dashboard off` stops it.
276
466
  | "Build this idea — there is no ticket." | `/team-work "export recipes as CSV"` |
277
467
  | "Reviewers left comments on my PR." | `/team-work pr` |
278
468
  | "Get a second opinion on this change." | `/team-work review` |
469
+ | "Work three tickets at once." | `/team-work RB-12 RB-13 RB-14` |
470
+ | "How secure is my project?" | `/team-security` |
471
+ | "Fix a security problem." | `/team-security fix SEC-2` |
472
+ | "How do I market this project?" | `/team-social` |
473
+ | "Write posts about what we shipped." | `/team-social post RB-12` or `/team-social week` |
279
474
  | "Where does everything stand?" | `/team-status` |
280
475
  | "Add a ticket to the board." | `/team-ticket new` |
281
476
  | "Undo a ticket we shipped." | `/team-rollback ABC-123` |
@@ -292,6 +487,7 @@ and only while the dashboard is on. `/team-dashboard off` stops it.
292
487
  | **/team-work** | Today's list; with `week` or `sprint`, a longer horizon. |
293
488
  | **/team-work `<ticket>`** | Work a ticket step by step; it resumes at the first unapproved step. |
294
489
  | **/team-work `"<idea>"`** | Work an idea without a ticket. |
490
+ | **/team-work `<ticket> <ticket> …`** | Several tickets at once with a developer and QA pool (up to 3 each). |
295
491
  | **/team-work pr** | One review round on the open PR: comments, failed checks, fixes, drafted replies. |
296
492
  | **/team-work review** | An independent review of the current work, now. |
297
493
 
@@ -311,6 +507,18 @@ and only while the dashboard is on. `/team-dashboard off` stops it.
311
507
  | **/team-dashboard** | The live page in your browser; `off` stops it. |
312
508
  | **/team-doctor** | A quick setup check; `fix` walks through the problems. |
313
509
 
510
+ ### Security
511
+
512
+ | Command | Purpose |
513
+ | --- | --- |
514
+ | **/team-security** | Scan the project and write or refresh `security.md`; `list`, `fix SEC-<n>`, `accept SEC-<n> <reason>`. |
515
+
516
+ ### Marketing
517
+
518
+ | Command | Purpose |
519
+ | --- | --- |
520
+ | **/team-social** | Rafi's marketing plan; `post <ticket>` drafts posts for a shipped feature, `week` a weekly round-up, `list` the drafts. |
521
+
314
522
  ### Set up and maintain
315
523
 
316
524
  | Command | Purpose |
@@ -327,11 +535,13 @@ and only while the dashboard is on. `/team-dashboard off` stops it.
327
535
  | --- | --- | --- | --- |
328
536
  | `team:product-manager` | Today's list, requirements, triage of PR problems, final review | No | Yes |
329
537
  | `team:researcher` | Feasibility check (code first), docs and tool research | No | Yes |
538
+ | `team:security-engineer` | Security scan and `security.md`, threat check per ticket, security review | `security.md`, its step files, security tests | Advisories and official docs only |
330
539
  | `team:project-manager` | Splits the work into tasks, writes the plan | Only the plan | Yes |
331
540
  | `team:developer-lead` | Builds the approved plan with tests | Code + tests | No |
332
- | `team:qa-engineer` | CI, local review, code review, security review; reads PR comments | Tests + its reports | No |
541
+ | `team:qa-engineer` | CI, local review, code review; reads PR comments | Tests + its reports | No |
333
542
  | `team:reviewer` | Independent review after QA: sees only the requirements and the diff | No | No |
334
543
  | `team:reply-writer` | Drafts replies to PR, GitHub and tracker comments in your style | No | No |
544
+ | `team:social-media` — **Rafi** | Marketing plan, feature posts, weekly round-up — drafts only | `.claude/team/marketing/` only | Research only |
335
545
  | `team:agent-maintainer` | Keeps the project profile up to date | `.claude/team/team.md` only | No |
336
546
 
337
547
  Need a design reviewer, an accessibility checker or a performance auditor?
@@ -348,7 +558,7 @@ board**, alone or next to your tracker:
348
558
  | --- | --- | --- | --- |
349
559
  | written down; requirements and plan not approved yet | being built | QA, independent review, PR open | merged or closed |
350
560
 
351
- ![The Super Power Team board with Plan, Do, Check and Done columns; cards show priority, what they wait for, and tickets taken from Linear and GitHub](https://raw.githubusercontent.com/al-shaikhli-w/Pit-Crew/master/assets/dashboard-board.png)
561
+ ![The Super Power Team board with Plan, Do, Check and Done columns; cards show priority, what they wait for, and tickets taken from Linear and GitHub](https://raw.githubusercontent.com/al-shaikhli-w/the-super-power-team/master/assets/dashboard-board.png)
352
562
 
353
563
  `/team-ticket new` first asks where the ticket comes from:
354
564
 
@@ -371,19 +581,23 @@ Everything lives under `.claude/team/` in your project:
371
581
  | `project/project-info.md` | The idea, users and goals — in your words. |
372
582
  | `project/project-tech.md` | Stack, structure, commands and risks — read from the code, or proposed. |
373
583
  | `project/project-plan.md` | The features in order. |
584
+ | `project/security.md` | The security picture and your security to-do list. |
585
+ | `marketing/marketing-plan.md` | Rafi's marketing plan. |
586
+ | `marketing/posts/` | Post drafts, one file per shipped ticket or week. |
374
587
  | `ideas/idea-v<N>.md` | Wishes not planned yet. |
375
588
  | `tickets/<ID>.md` | The local board, when it is on. |
376
- | `work/active/<ticket>/` | One file per step, plus `00-brief.md`. |
589
+ | `work/active/<ticket>/` | One file per step, plus `00-brief.md` (which names the ticket's worktree when several tickets run). |
377
590
  | `work/history/` | Finished tickets and `INDEX.md`. |
378
591
 
379
592
  ```text
380
593
  .claude/team/
381
594
  ├── team.md
382
- ├── project/ project-info.md · project-tech.md · project-plan.md
595
+ ├── project/ project-info.md · project-tech.md · project-plan.md · security.md
383
596
  ├── ideas/ idea-v1.md (closed) · idea-v2.md (open)
384
597
  ├── tickets/ RB-12.md · ABC-41.md
598
+ ├── marketing/ marketing-plan.md · posts/2026-11-22-rb-12.md
385
599
  └── work/
386
- ├── active/abc-123/ 00-brief.md · 01-requirements.md · … · 07-pr-rounds.md
600
+ ├── active/abc-123/ 00-brief.md · 01-requirements.md · 02-security.md · … · 05-security.md · 07-pr-rounds.md
387
601
  └── history/ INDEX.md · 2026-11-19-abc-123/
388
602
  ```
389
603
 
@@ -398,7 +612,8 @@ it.
398
612
  | **CI gate** | qa-engineer | The project's full gate passes, with its output. |
399
613
  | **Local review** | qa-engineer | Your review tool's findings, each checked against the code. |
400
614
  | **Code review** | qa-engineer | Correctness, regressions, edge cases, project rules, and tests that test behaviour. |
401
- | **Security review** | qa-engineer | No secrets, unescaped input, missing server checks or leaking data. |
615
+ | **Threat check** | security-engineer | Before the plan: the security rules this ticket must follow. |
616
+ | **Security review** | security-engineer | Every rule from the threat check holds; no secrets, unescaped input, missing server checks, leaking data or vulnerable new dependencies. |
402
617
  | **Independent review** | reviewer | A fresh look with only the requirements and the diff. |
403
618
  | **PR rounds** | qa-engineer | Every new review comment and failed check: valid, not valid, or already fixed. |
404
619
 
@@ -410,6 +625,7 @@ PASS goes back to the build.
410
625
 
411
626
  - stops after each step until you approve;
412
627
  - gives you git commands instead of running them;
628
+ - never posts on social media — Rafi's posts are drafts for you;
413
629
  - treats the tracker and GitHub as read-only — replies are drafts for you to post;
414
630
  - reports PASS only with the output that proves it;
415
631
  - answers short: tables and lists, no recap.
@@ -443,7 +659,7 @@ back.
443
659
  | Task | Command |
444
660
  | --- | --- |
445
661
  | **Update to the newest version** | `npx the-super-power-team@latest` |
446
- | **Install a specific version** | `npx the-super-power-team@0.13.0` |
662
+ | **Install a specific version** | `npx the-super-power-team@0.14.1` |
447
663
  | **See which version you have** | `claude plugin list` |
448
664
  | **Uninstall** | `npx the-super-power-team uninstall` |
449
665
  | **Help** | `npx the-super-power-team help` |
@@ -457,7 +673,7 @@ files are older than the plugin.
457
673
  Uninstalling removes the plugin and `~/.claude/the-super-power-team/`; the
458
674
  `.claude/team/` files in your projects stay.
459
675
 
460
- See what changed in each version in the [Changelog](https://github.com/al-shaikhli-w/Pit-Crew/blob/master/CHANGELOG.md).
676
+ See what changed in each version in the [Changelog](https://github.com/al-shaikhli-w/the-super-power-team/blob/master/CHANGELOG.md).
461
677
 
462
678
  ### Troubleshooting
463
679
 
@@ -471,13 +687,17 @@ See what changed in each version in the [Changelog](https://github.com/al-shaikh
471
687
  | An agent uses an old command or path | `/team-work sync` |
472
688
  | Crew files show up in `git status` | Run `/team-setup` again and choose a git option, or add `.claude/team/` to `.git/info/exclude` |
473
689
  | You want to stop mid-ticket | Just stop; `/team-work <ticket>` resumes at the first unapproved step |
690
+ | A ticket waits and never starts | It shares a file with an open ticket; merge that one, or say `<ticket> go anyway` |
691
+ | `git worktree add` says the branch exists | Use `git worktree add "<path>" <branch>` without `-b`, or remove the old worktree with `git worktree remove "<path>"` |
692
+ | Old worktrees pile up | `/team-doctor` lists them with the `git worktree remove` command |
693
+ | No `security.md` | `/team-security` (needs code in the project) |
474
694
 
475
695
  ## Support and contributing
476
696
 
477
697
  Found a bug or an agent that works from old information? Open an
478
- [issue](https://github.com/al-shaikhli-w/Pit-Crew/issues). Changes are
479
- listed in the [Changelog](https://github.com/al-shaikhli-w/Pit-Crew/blob/master/CHANGELOG.md).
698
+ [issue](https://github.com/al-shaikhli-w/the-super-power-team/issues). Changes are
699
+ listed in the [Changelog](https://github.com/al-shaikhli-w/the-super-power-team/blob/master/CHANGELOG.md).
480
700
 
481
701
  ## License
482
702
 
483
- MIT — see [LICENSE](https://github.com/al-shaikhli-w/Pit-Crew/blob/master/LICENSE).
703
+ MIT — see [LICENSE](https://github.com/al-shaikhli-w/the-super-power-team/blob/master/LICENSE).
@@ -2,7 +2,7 @@
2
2
  name: agent-maintainer
3
3
  description: Use to keep the agent team up to date — compares the agent files, the /team workflow and the team profile with the project's current rules, tools, versions and layout, reports what is out of date, and applies the approved updates. Run it after the project rules, package versions, CI script or connected tools change, or when an agent worked from old information. Edits only the team's own files.
4
4
  tools: Read, Grep, Glob, Bash, Write, Edit
5
- model: inherit
5
+ model: haiku
6
6
  effort: medium
7
7
  ---
8
8
 
@@ -47,7 +47,7 @@ No finding without a `file:line` or command output. All current? One line.
47
47
 
48
48
  ## Language and project documents
49
49
  - Answer in `Reply language` from `.claude/team/team.md`; write files under `.claude/team/` in `Document language`. Code, commits and PR titles follow the project.
50
- - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
50
+ - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), `security.md` (the security picture and to-do list), `../marketing/marketing-plan.md` (Rafi's marketing plan), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
51
51
 
52
52
  ## Limits
53
53
  - No internet, no installs, read-only git. Whether `.claude/team/` is committed is the developer's choice in `team.md`; you never stage it.
@@ -29,7 +29,7 @@ New dated section per round. Not finished until QA has verified it.
29
29
 
30
30
  ## Language and project documents
31
31
  - Answer in `Reply language` from `.claude/team/team.md`; write files under `.claude/team/` in `Document language`. Code, commits and PR titles follow the project.
32
- - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
32
+ - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), `security.md` (the security picture and to-do list), `../marketing/marketing-plan.md` (Rafi's marketing plan), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
33
33
 
34
34
  ## Shared brief
35
35
  Working on a ticket? Read `00-brief.md` in its work folder first. It holds the approved goal, decisions, constraints, the current task, and notes from the other agents.
@@ -41,6 +41,8 @@ Working on a ticket? Read `00-brief.md` in its work folder first. It holds the a
41
41
  - Read-only git. No commit, push, branch change or PR.
42
42
  - No internet, also not through the shell. Outside questions go to the researcher.
43
43
  - Never report a check as passed without its output.
44
+ - **Worktree.** When the prompt names a worktree path, read, edit and run commands only inside it (`cd "<path>" && …` for every command). Never open another ticket's work folder or worktree.
45
+ - Follow every security condition in `02-security.md`; one you cannot meet goes back as a question, never silently skipped.
44
46
 
45
47
  ## Output
46
48
  Short. What changed, why, anything unexpected. No file-by-file walk-through, no recap of the plan.
@@ -42,7 +42,7 @@ Your whole answer is that table and that line. One list call to the tracker is e
42
42
 
43
43
  ## Language and project documents
44
44
  - Answer in `Reply language` from `.claude/team/team.md`; write files under `.claude/team/` in `Document language`. Code, commits and PR titles follow the project.
45
- - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
45
+ - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), `security.md` (the security picture and to-do list), `../marketing/marketing-plan.md` (Rafi's marketing plan), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
46
46
 
47
47
  ## Shared brief
48
48
  Working on a ticket? Read `00-brief.md` in its work folder first. It holds the approved goal, decisions, constraints, the current task, and notes from the other agents.
@@ -9,7 +9,7 @@ effort: medium
9
9
  You are the project manager. Project facts: `.claude/team/team.md`. Rules: `CLAUDE.md`.
10
10
 
11
11
  ## Job — ticket plan
12
- From `01-requirements.md` and `02-research.md`, write `03-plan.md` in the ticket's work folder — the only file you create or edit.
12
+ From `01-requirements.md`, `02-research.md` and `02-security.md` (when it exists), write `03-plan.md` in the ticket's work folder — the only file you create or edit.
13
13
 
14
14
  ```markdown
15
15
  # Plan — <ticket> <title>
@@ -31,6 +31,8 @@ From `01-requirements.md` and `02-research.md`, write `03-plan.md` in the ticket
31
31
  - Status: `todo`, `in progress`, `blocked`, `done`. `done` only after QA reports PASS.
32
32
  - A blocker names who or what it waits on.
33
33
  - Every plan covers the tests and texts the project rules require.
34
+ - Every condition in `02-security.md` is the "Done when" of a task, with a test where one can prove it.
35
+ - **Files / area** names real paths (files or folders), so tickets running side by side can be checked for overlap. Write an area name only when no path is known yet.
34
36
  - Review-round fixes go in a new section `## Round <n> — <date>`. Update rows; never delete a section.
35
37
 
36
38
  ## Job — step back
@@ -50,7 +52,7 @@ Then at most three lines on the plan as a whole: a row that should move, one tha
50
52
 
51
53
  ## Language and project documents
52
54
  - Answer in `Reply language` from `.claude/team/team.md`; write files under `.claude/team/` in `Document language`. Code, commits and PR titles follow the project.
53
- - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
55
+ - The project's big picture: `.claude/team/project/project-info.md` (idea, users, goals), `project-tech.md` (stack, structure, risks), `project-plan.md` (features in order), `security.md` (the security picture and to-do list), `../marketing/marketing-plan.md` (Rafi's marketing plan), and `.claude/team/ideas/idea-v<N>.md` (wishes not planned yet). Read what your job needs; do not repeat it back.
54
56
 
55
57
  ## Shared brief
56
58
  Working on a ticket? Read `00-brief.md` in its work folder first. It holds the approved goal, decisions, constraints, the current task, and notes from the other agents.