a-lottes

a-lottes/aSPARK

Plugin Claude Code

Marketplace for aSPARK — an agile AI product team for Claude Code (Specify, Plan, Act, Review, Keep).

a-lottes/aSPARK

Plugin Claude Code

An agile AI product team for Claude Code — Specify, Plan, Act, Review, Keep. A Product Owner, Designer, Engineering Manager, Reviewer, QA Tester and Release Manager work your feature through a gated delivery loop.

a-lottes/aSPARK

Instructions file

Instructions for a-lottes/aSPARK, covering project notes for claude code and refuted-with-finding is a valid ceremony outcome.

a-lottes/aSPARK

Agent

The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.

a-lottes/aSPARK

Agent

The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.

a-lottes/aSPARK

Agent

The Facilitator of the aSPARK team. Use with /charter to establish or amend the project constitution — the standing principles and constraints that bind every SPARK phase. Grounds the constitution in what the project actually is, proposes concrete defaults, and challenges aspirational entries the code doesn't back up.…

a-lottes/aSPARK

Agent

The Product Owner of the aSPARK team. Use in the Specify phase (/story-time) when a product idea or feature request must be challenged and turned into a spec with user stories and testable acceptance criteria. Also use when an existing spec needs re-prioritization or scope decisions, or in /next-steps to propose the…

a-lottes/aSPARK

Agent

The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…

a-lottes/aSPARK

Agent

The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.

a-lottes/aSPARK

Agent

The Reviewer of the aSPARK team. Use in the Review phase (/peer-review) to audit the diff produced by /increment with a staff-engineer eye: plan conformance, correctness, edge cases, error handling, security and test quality. Writes the review report and may fix obvious low-risk issues directly.

a-lottes/aSPARK

Skill Claude CodeCodex

Establish or amend the project constitution — the standing principles and constraints that bind every SPARK phase. Use once at project start to give the team its ground rules, or any time a project-wide decision (stack choice, quality bar, non-negotiable) changes and should apply to all future features.

a-lottes/aSPARK

Skill Claude CodeCodex

Hands-on QA in a real browser: the QA Tester clicks through the running app, verifies every acceptance criterion from the spec, explores beyond the happy path and files reproducible bugs. Use after /peer-review passes, or to re-test after fixes. Requires a running app and browser tooling.

a-lottes/aSPARK

Skill Claude CodeCodex

Start the Keep phase of the SPARK loop: the Release Manager runs fresh pre-flight checks, writes the user-facing changelog, prepares tag/PR/ deploy, publishes on the user's explicit go, and records the cycle's learnings. Use when review and QA have both passed and the increment should be released.

a-lottes/aSPARK

Skill Claude CodeCodex

Start the Act phase of the SPARK loop: build the increment strictly following the approved plan, task by task, with progress tracked in the plan. Use after the plan is approved, or to fix findings that came back from /peer-review or /demo-day.

a-lottes/aSPARK

Skill Claude CodeCodex

Run the Designer over a spec (design risks, usability heuristics, accessibility) or over an implemented UI (screenshots, running app). Use after /story-time for UI-facing features, or any time the user wants a design critique of a spec, mockup, page or component.

a-lottes/aSPARK

Skill Claude CodeCodex

Have the Product Owner survey the project's current state — shipped features, in-flight work, open findings, standing goals — and propose one concrete next feature ready to hand to /story-time or /spark. Use when the user has no idea in hand and asks "what should we build next", when a loop just closed and the next…

a-lottes/aSPARK

Skill Claude CodeCodex

Start the Review phase of the SPARK loop: the Reviewer audits the diff produced by /increment — plan conformance, correctness, edge cases, security, test quality — and writes the review report. Use after /increment reports done, or to re-review after fixes.

a-lottes/aSPARK

Skill Claude CodeCodex

Run the full SPARK loop end-to-end for one feature: Specify → Plan → Act → Review → Keep, pausing at every gate for the user's decision. Use when the user brings a feature idea and wants the whole agile team to take it from idea to release in one guided session — or wants to resume a feature that is somewhere mid-loop.

a-lottes/aSPARK

Skill Claude CodeCodex

Start the Plan phase of the SPARK loop: the Engineering Manager turns an approved spec into a technical plan — architecture decision with rejected alternatives, ordered task breakdown with definitions of done, test strategy and risks. Use after the spec is approved, or to revise a plan after review/QA findings.

a-lottes/aSPARK

Skill Claude CodeCodex

Start the Specify phase of the SPARK loop: the Product Owner interrogates a product idea and turns it into a spec with user stories and testable acceptance criteria. Use when the user brings a new feature idea, product idea or change request that has no spec yet — or wants an existing spec challenged and reworked.

a-lottes/aSPARK-graph

Instructions file

Instructions for a-lottes/aSPARK-graph, covering claude.md — aspark-graph, what this is, layout & the one load-bearing convention, non-negotiables (each retired a real risk — don't regress) and using aspark-graph in /peer-review (this repo).

a-lottes/aSPARK-graph

MCP server Claude CodeCodexCursor +2

A lean, local code-and-artifact knowledge graph that speaks SPARK. Runs locally from the aspark-graph Python package.