Skip to content

aSPARK v0.2.0 — spec-driven layer

Choose a tag to compare

View all tags
@a-lottes a-lottes released this 14 Jul 19:28
· 67 commits to main since this release
v0.2.0
fbcffe2

Adds a spec-driven-development layer on top of the SPARK loop: standing project context, sharper specs, and requirement traceability end to end. Fully backward compatible — existing .spark/ artifacts keep working.

✨ New

  • Project constitution — /charter and a new Facilitator agent capture project-wide principles, constraints, quality bars and non-negotiables in .spark/constitution.md, read by the Product Owner, Designer, Engineering Manager and Reviewer. Set the ground rules once instead of re-arguing them every feature.
  • Clarify pass — /story-time now runs a structured ambiguity sweep across an 8-category taxonomy (functional boundaries, data, permissions, error/edge cases, NFRs, integrations, UX states, out-of-scope) before the spec gate, logged in a Clarifications table.
  • Non-functional requirements — specs gain an NFR section with measurable, falsifiable NFR- entries that inherit the constitution's quality bars.
  • Traceability — US-/AC-/NFR- IDs flow spec → plan (Covers column) → review (Requirements Traceability table) → QA (NFR rows), enforced at each gate.

🔧 Changed

  • Templates: new constitution.md; spec.md, plan.md, review-report.md, qa-report.md extended with the sections and gate checks above.
  • Agents: product-owner, engineering-manager, reviewer, designer read the constitution; qa-tester verifies browser-observable NFRs.
  • Docs: docs/workflow.md gains Project-Wide Context and Traceability sections.

✅ Validation

  • claude plugin validate passes.
  • Dry-run-validated through the Plan phase on a sample project: /charter → /story-time (Clarify) → /look-and-feel → /sprint-plan, with the constitution binding every phase and full Must-AC coverage in the plan.

Full changelog: v0.1.0...v0.2.0

Assets 2
Loading