roshanis/blackadder
Blackadder DLC for Cursor: idea → plan → architecture + design system → walking skeleton → verified tracer-bullet slices → release. Portable manifest alongside .cursor-plugin/plugin.json.
Blackadder phase 2a. Produces docs/blackadder/03-architecture.md plus the initial Supabase migration, RLS policies, seed files and ADRs from the accepted plan. Also --onboard for brownfield repos. Runs in parallel with /design-system.
Blackadder DLC dispatcher. Use when the user asks "where are we", "what's next", "run the pipeline", or names a phase without a skill. Reads project state and routes to the right phase skill.
Blackadder feedback router. Turns a finding from any tester, reviewer or production into a change request with an impact level L1-L4 and routes it to the lowest document that must change - without re-running the pipeline. Usage /change-request <finding or CR id>.
Blackadder phase 2b, the design track. Produces rendered direction boards, DESIGN.md (Google's open design-system format), packages/ui + the /design-system reference route, and per-screen prototypes that become visual baselines. Syncs from Claude Design, Figma or Stitch. Usage /design --directions | --system | --screen S-NNN | --sync <source>.
Alias kept for compatibility. The Blackadder design track is /design (--directions, --system, --screen, --sync). Invoking /design-system runs /design --system.
Blackadder phase 0. Interactive ideation with the requester that produces docs/blackadder/01-idea.md (problem, users, scope, non-goals, build-vs-buy, kill criteria). Use for a new product or a new feature on an existing one.
Blackadder phase 1. Turns an accepted Idea doc into docs/blackadder/02-plan.md (stories, Given/When/Then acceptance criteria, NFRs) and slices.md (the ordered tracer-bullet ladder). Also runs bounded plan reconciliation after architecture.
Blackadder phase 5. Release verification on staging (cross-slice journeys, NFRs, security checklist, a11y/UX pass), release notes with migration risk class, and the human-gated promote to production. Usage /release, then /release --promote.
Blackadder phase 4. Builds ONE tracer-bullet slice from slices.md end to end - acceptance tests first in a separate context, then build, CI, fresh-context verification, bounded to 3 rounds, then a PR for the human. Usage /slice INC-03.
Blackadder verifier procedure. Run in a FRESH context against a slice PR - executes acceptance + regression suites on the preview URL, does bounded adversarial checks, screenshot/axe pass for UI, checks architecture and design deltas, and records a SHA-keyed verdict in .blackadder/ledger.tsv. Never modifies application code.