a-lottes/aSPARK

<div align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="assets/aspark-logo-dark.png" /> <img src="assets/aspark-logo.png" alt="aSPARK — an agile AI product team for Claude Code" width="440" /> </picture> </div>

An agile AI product team for Claude Code. You bring the idea. A Product Owner challenges it, an Engineering Manager plans it, the Developer builds it, a Reviewer audits the diff, a QA Tester clicks through your app in a real browser, and a Release Manager ships it — and nothing moves to the next phase until the previous gate is green.

aSPARK is a Claude Code plugin. No service, no account, no runtime: it is Markdown that installs into your project and leaves a reviewable paper trail in .spark/.

https://github.com/user-attachments/assets/714d2813-15d5-44f5-9644-dfaabf6524f9

<p align="center">_{<b>The 100-second demo, narrated</b> — one real 47-minute session, /spark to /go-live. Every time-lapse is marked. Also on <a href="https://aspark.lottes.dev/en/#showcase">aspark.lottes.dev</a>.}</p>

---

See it work

One command runs the whole loop. It stops at every gate and shows you the artifact before moving on — you stay the decision maker.

You:     /spark I want a dashboard where users see their weekly stats

Claude:  [Product Owner]  Challenges the idea, asks what "weekly" means for a user
                          in another timezone, writes spec.md with US-1…US-3 and
                          testable acceptance criteria. → Gate: you approve the spec.
         [Designer]       Flags an empty-state gap and a contrast risk in the spec.
         [Eng. Manager]   Decides the architecture, cuts 6 tasks into plan.md, each
                          mapped to a story. → Gate: you approve the plan.
         [Developer]      Builds task by task. No scope creep — the plan is the fence.
         [Reviewer]       Reads the diff, finds an off-by-one in the week boundary,
                          file