Add aSPARK — gated agile delivery process plugin for Claude Code

[a-lottes]

Adds aSPARK to the list.

aSPARK turns Claude Code into a gated delivery process with an AI product team. Every feature moves through five phases (Specify → Plan → Act → Review → Keep) and can only advance when the previous phase's quality gate is green. Includes real-browser QA that verifies each acceptance criterion before release, and keeps all decision artifacts inside the project as a reviewable trail.

• Repo: https://github.com/a-lottes/aSPARK
• License: MIT
• Install: /plugin marketplace add a-lottes/aSPARK then /plugin install aspark@aspark

I've matched the existing table format and added the entry to the Plugins & Extensions table (and bumped the plugin count in the Status table). Happy to adjust categorization.

[qodo-code-review]

PR Summary by Qodo

Add aSPARK plugin entry to README and update plugin count

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Add aSPARK to the Plugins & Extensions table with link, author, and summary.
• Increment the "Plugins listed" metric to reflect the new entry.

High-Level Assessment

The following are alternative approaches to this PR:

1. Auto-generate README counts (CI/script)

• ➕ Eliminates manual count drift when adding/removing entries
• ➕ Makes list updates less error-prone as the table grows
• ➖ Adds build/CI or scripting overhead for a simple curated list
• ➖ Still requires a source-of-truth format (YAML/JSON) and review of generated output

Recommendation: For the current lightweight, curated README, the PR’s manual update is appropriate. If the list grows significantly or count mismatches become common, consider moving entries to a structured data file and generating the README tables/counts in CI.

Files changed (1) +2 / -1

Documentation (1) +2 / -1

README.mdAdd aSPARK to plugin list and bump plugin count +2/-1

Add aSPARK to plugin list and bump plugin count

• Updates the status metrics to increase the "Plugins listed" count from 4 to 5. Adds a new row to the Plugins & Extensions table for aSPARK, including repository link, author, and a short description.

README.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 2 rules

1. Overlong table description 🐞 Bug ⚙ Maintainability

Description

The newly added aSPARK row uses a much more verbose description than surrounding entries and omits a
trailing period, reducing scanability and conflicting with the repo’s contribution guidance for
short/simple descriptions ending with a period.

Code

README.md[33]

+| [aSPARK](https://github.com/a-lottes/aSPARK) | a-lottes | Gated agile delivery process with a full AI product team (PO, Designer, EM, Reviewer, QA, Release) and real-browser QA gates |

Evidence

The README change adds a long description for the aSPARK row, while the contribution guidelines
explicitly ask for short/simple descriptions that end with a period.

README.md[25-34]
contributing.md[7-10]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The new `aSPARK` entry’s description is substantially longer than neighboring rows and does not end with a period, which hurts consistency and readability of the table.

### Issue Context
`contributing.md` asks to keep descriptions short/simple and end them with a period. While the README uses a table (not the exact `[Title](link) - Description.` layout), the description-length and punctuation guidance still applies for consistency.

### Fix Focus Areas
- README.md[33-33]

### Suggested change (example)
Replace the current description with a concise one that ends in a period, e.g.:
- `Gated agile delivery process with an AI product team and QA gates.`

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Overlong table description 🐞 Bug ⚙ Maintainability

The newly added aSPARK row uses a much more verbose description than surrounding entries and omits a
trailing period, reducing scanability and conflicting with the repo’s contribution guidance for
short/simple descriptions ending with a period.

Agent Prompt

### Issue description
The new `aSPARK` entry’s description is substantially longer than neighboring rows and does not end with a period, which hurts consistency and readability of the table.

### Issue Context
`contributing.md` asks to keep descriptions short/simple and end them with a period. While the README uses a table (not the exact `[Title](link) - Description.` layout), the description-length and punctuation guidance still applies for consistency.

### Fix Focus Areas
- README.md[33-33]

### Suggested change (example)
Replace the current description with a concise one that ends in a period, e.g.:
- `Gated agile delivery process with an AI product team and QA gates.`

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools