A gated agile delivery process for Claude Code that runs an AI product team through planning, building, browser QA and release, with a quality gate before each feature moves on. Suited to teams who want structured, reviewable delivery.
@a-lottesSeed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an…
@a-lottesStart a campaign draft: build `.spark/campaigns/<name>/campaign.md` from an existing campaign kind, asking only what the kind…
@a-lottesEstablish or amend the project constitution — the standing principles and constraints that bind every SPARK phase. Use once at…
@a-lottesHands-on QA in a real browser: the QA Tester clicks through the running app, verifies every acceptance criterion from the spec,…
@a-lottesStart the Keep phase of the SPARK loop: the Release Manager runs fresh pre-flight checks, writes the user-facing changelog,…
@a-lottesStart the Act phase of the SPARK loop: build the increment strictly following the approved plan, task by task, with progress…
@a-lottesRun the Designer over a spec (design risks, usability heuristics, accessibility) or over an implemented UI (screenshots, running…
@a-lottesHave the Product Owner survey the project's current state — shipped features, in-flight work, open findings, standing goals — and…
@a-lottesStart the Review phase of the SPARK loop: the Reviewer audits the diff produced by /increment — plan conformance, correctness,…
@a-lottesRun the full SPARK loop end-to-end for one feature: Specify → Plan → Act → Review → Keep, pausing at every gate for the user's…
@a-lottesStart the Plan phase of the SPARK loop: the Engineering Manager turns an approved spec into a technical plan — architecture…
@a-lottesStart the Specify phase of the SPARK loop: the Product Owner interrogates a product idea and turns it into a spec with user…
@a-lottesThe Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or…
@a-lottesThe Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan:…
@a-lottesThe Facilitator of the aSPARK team. Use with /charter to establish or amend the project constitution — the standing principles…
@a-lottesThe Product Owner of the aSPARK team. Use in the Specify phase (/story-time) when a product idea or feature request must be…
@a-lottesThe QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser:…
@a-lottesThe Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release:…
@a-lottesThe Reviewer of the aSPARK team. Use in the Review phase (/peer-review) to audit the diff produced by /increment with a…
@a-lottesIs this you? Claim your profilePut a plugin at the top of Plugins, from $9
