Skip to content

aSPARK v0.1.0 — agile AI product team for Claude Code

Choose a tag to compare

View all tags
@a-lottes a-lottes released this 13 Jul 20:31
· 77 commits to main since this release
v0.1.0
51acd90

aSPARK turns Claude Code from a coding copilot into a gated delivery process — an agile AI product team where a Product Owner challenges your idea, a Designer spots bad design, an Engineering Manager locks the architecture, a Reviewer finds your bugs, a QA Tester clicks through your app in a real browser, and a Release Manager ships it.

Every feature travels through five phases — Specify → Plan → Act → Review → Keep — and may only move forward when the previous phase's quality gate is green.

What's in this release

  • 6 team agents — product-owner, designer, engineering-manager, reviewer, qa-tester, release-manager, each with its own mindset, standards and hard rules.
  • 7 ceremony skills — /story-time, /look-and-feel, /sprint-plan, /increment, /peer-review, /demo-day, /go-live.
  • /spark orchestrator — runs the whole loop end-to-end with gate stops, resume support and feedback-loop escalation.
  • 5 gated artifact templates — spec, plan, review, QA and release notes, each ending in an explicit gate checklist. Artifacts live in .spark/<feature>/ inside your project, so the whole decision trail is transparent and reviewable.
  • Workflow deep-dive (docs/workflow.md) — the artifact chain, gate invariants, feedback loops and role boundaries.

Validated end-to-end

This release passed a full dry run: the loop took a vanilla-JS quick-todo app from idea to release — PO → Designer → EM → build → code review → real-browser QA → release — with all five gates enforced. Plugin structure verified with claude plugin validate.

Install

In a normal (interactive) Claude Code session:

/plugin marketplace add a-lottes/aSPARK
/plugin install aspark@aspark

Then restart Claude Code. See the README for the step-by-step guide and the non-interactive CLI variant.

MIT licensed.

Assets 2
Loading