4.1 KiB
4.1 KiB
Session 0041.0 — Transcript
App: ecomm Start: 2026-06-22T07-06 (PST) Type: capture Posture: careful Claude-Session: af2d41d5-d230-4086-a383-1e5f5826db6b Status: PLACEHOLDER — claimed at session start; finalized at session end.
This file reserves session ID 0041 for ecomm. The driver replaces this body with the full transcript and renames the file to its final SESSION-0041.0-TRANSCRIPT-2026-06-22T07-06--.md form at session end.
Launch prompt
# SDL pipeline refactor — design brief (target state)
Restructure the Wiggleverse SDLC into a staged, gated pipeline where every
artifact handoff is a review gate. Built with TODAY's five session types — the
new session types don't exist yet (bootstrap).
## The artifact
ONE SPEC.md (Solution Design, handbook §3.3), authored by ACCRETION — each
design-track stage writes its lens INTO the same growing file, never separate
brd.md/prd.md fragments. superpowers:writing-plans expects ONE coherent spec
doc; accretion guarantees it.
## Design track (careful, once per Feature) — gate at every seam
1. wgl-brainstorming --lenses brd → SPEC Business lens → GATE
2. wgl-brainstorming --lenses prd → SPEC Product lens
+ Claude-Design-vs-Code decision → GATE
3. (if decision = Design) Claude Design → wgl-design-handoff → bundle → GATE
4. wgl-tech-design (NEW) → SPEC Engineering lens
(pure architecture/contract; NO task breakdown) → GATE
→ SPEC complete
## Build track (once per Feature) — gate at every seam
SPEC.md → wgl-writing-plans (ONE plan, whole Feature) → GATE
→ wgl-executing-plans (execute that plan) → PPE (§9)
No per-slice loop. The plan's native Task→Step structure IS the decomposition.
## Decisions (locked — do not re-litigate)
- Every seam is a gate for now; wrapping multiple gates into one session is a
later optimization.
- One SPEC = one plan = one execution. "Slice" is NOT used — superpowers has no
such concept (its grain is sub-project / spec / plan / Task / Step). The SPEC
Delivery Plan carries rollout/launch strategy only, NOT a task list.
- Two altitudes stay distinct: wgl-tech-design = architecture/contract (no
tasks); wgl-writing-plans = the full task breakdown.
- Terminology: "Solution Design" = the WHOLE SPEC. The new step is
wgl-tech-design (authors one lens), NOT wgl-solution-design.
- §4.3 reconciliation: a Feature = one SPEC = one plan = one execution; its
internal units are the plan's Tasks. The Feature→Story(slice) sub-layer
collapses — Stories become STANDALONE leaf issues only (R2(b)), not a Feature
sub-layer. R1–R4 otherwise intact.
- "Which lenses exist" is governed by issue type (§4.3): Feature → brd+prd
required (R3); leaf story/task/bug → lenses skippable, tech-design authors a
thin SPEC; nothing warranted → skip design track, build straight from the
issue (R2(b)).
## Superpowers mapping (native grain, no overlay)
- superpowers:brainstorming is a borrowed DIALOGUE technique only; wgl owns the
terminal state (a lens run never hands off to writing-plans).
- superpowers:writing-plans wants ONE spec doc and assumes scope decomposition
happened upstream; wgl-tech-design completing one SPEC satisfies that.
- superpowers:writing-plans and :executing-plans are already SEPARATE skills; the
plan doc is their handoff. wgl-writing-plans / wgl-executing-plans are thin
wrappers at native grain: one SPEC → one plan → one execution.
## Wiggleverse rules every session honors
- Docs lead automation (§4.1): handbook changes FIRST; skills CITE it, never
restate canonical taxonomy/pipeline (§4.1/§4.2).
- Deterministic-first (§4.2); branch → PR → merge (§5.4); plugin version bump per
change; git over SSH (§5.2).
(Session opened as: CAPTURE — turn this brief into typed, source-linked Gitea issues.)
Deferred decisions
Autonomous-mode low-confidence calls the driver made and would have liked operator input on. Appended as the session runs; surfaced at finalize. Empty if none.