blackadder

Files (1)

• SKILL.md

SKILL.md (first lines)

# /blackadder — where are we, what's next

You are the dispatcher for the Blackadder Development Life Cycle. You never do phase work
yourself; you determine the phase, check the gate, and hand off to exactly one phase skill.

## 1. Read state (do not guess)

Check, in order:

1. `docs/blackadder/01-idea.md` … `04-design-system.md` — exist? front matter `status:`?
2. `docs/blackadder/slices.md` — exists? which slice rows are `done | building | verifying | stale | blocked`?
3. `.blackadder/units.tsv`, `.blackadder/ledger.tsv`, `.blackadder/gates.md` — open gates? unresolved questions?
4. `git log --oneline -20` and open PRs (if a `gh`/GitHub tool is available) — anything mid-flight?

If `docs/blackadder/` does not exist, this is a fresh project: route to `/ideate`.
If the repo already has code but no `docs/blackadder/`, this is **brownfield**: run `/architect --onboard`
first (reverse-engineer `03-architecture.md` from the code, marking every statement
`observed` or `inferred`), then `/ideate` scoped to the feature.

## 2. Determine the phase

| Condition | Phase | Next skill |
|---|---|---|
| no idea doc, or `status: draft` | Ideate | `/ideate` |
| idea `accepted`, no plan or plan `draft` | Plan | `/plan` |
| plan `accepted`, no architecture or `DESIGN.md` | Architect + Design | `/architect` and `/design --directions` → `--system` (parallel is fine) |
| `DESIGN.md` approved, a UI slice `ready` whose screen has no `/proto` | Screen design | `/design --screen S-NNN` before `/slice` |
| both `accepted`, slice `INC-00` not done | Skeleton | `/skeleton` |
| `INC-00` done, any slice not done | Build loop | `/slice <next ready id>` |
| all slices done, no release verdict | Release | `/release` |
| release verdict `pass`, not promoted | Deploy | `/release --promote` (hard gate) |
| an open change request | CR routing | `/change-request <id>` |

A phase whose gate is **hard** and not yet approved by a human is *not* passed. Do not
proceed past it. Post the gate question (see below) and stop.

## 3. Report, then hand off

Print a status block of at most 15 lines:

```
Blackadder status
Phase: build   Slice: INC-03 (round 2/3)   Open gates: none
Docs pinned: idea@a1b2c3 plan@d4e5f6 arch@0a1b2c design@7f8e9d
Slices: 2 done · 1 verifying · 4 ready · 0 stale
Spend: INC-03 $3.10 / $8.00 · project $21.40 / $150.00
Next: /slice INC-03
```

Budget check before routing: if the current slice's `spent_usd` ≥ `budget_usd_per_slice`,
or the project total ≥ `budget_usd_project`, do not dispatch; open a gate that shows the
spend and asks for `budget +N` or `split`. Read only front matter and the state files to
produce this block — never the full documents.

Then invoke the next skill, or if a human gate is open, write the gate entry to
`.blackadder/gates.md` in this exact shape and stop:

```
## G1 — Plan + slice ladder   (opened <date>, by <skill>)
Question: Approve docs/blackadder/02-plan.md and slices.md as written?
Default if you reply `go`: proceed to /architect and /design-system.
Why it matters: everything downstream is built from this ladder.
Reply: `go`, `go --with-notes: …`, or `redo: <reasons>`.
```

## Autonomy dial

`docs/blackadder/01-idea.md` front matter has `autonomy: supervised | balanced | autopilot`.

- `supervised`: every slice merge is a human gate.
- `balanced` (default): slices auto-proceed on verifier `pass` + CI green; the four hard gates remain.
- `autopilot`: same, and soft-gate questions auto-resolve to their defaults after being logged.

Stop conditions override every level: touching auth, payments, PII schema, data deletion,
public API changes, adding a paid service, or any production action always escalates.

## Design dials (same front matter)

- `design_source`: any of `agent`, `claude-design`, `figma`, `stitch` — where `/design`
  pulls directions, tokens and screens from.
- `design_review`: `annotate` (design-reviewer findings are always `minor`) or `block`
  (rubric categories marked B may be `major` and block a slice). Start with `annotate`;
  switch after ~5 UI slices if fewer than 1 in 5 findings were noise.

From roshanis/blackadder-dlc, MIT.

More from roshanis/blackadder-dlc