fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
c80e09e7322bc8327c5afabe6736ea5fb83f7a41
agentic-dev/docs/work/epics/walking-skeleton/_epic.md
Danijel Martinek 99180887f3 docs(work): decompose platform-retrofit and walking-skeleton epics 
platform-retrofit: 8 stories / 18 tasks (spec bundle into docs/product,
single-version release-please before deletions, demo feature removal,
web-next auth shell, optional cores, work-tree archive, library traces,
agent-doc rewrite). walking-skeleton: 11 stories / 28 tasks across
workspaces, discovery, core-runner-protocol, runner app, editor, and
the flagship connect-to-selection e2e; builds on platform-retrofit
(prose dependency note — cross-epic frontmatter unsupported).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
2026-07-12 12:28:51 +02:00

2.7 KiB
Raw Blame History

id, prd, title, type, status, features, created
id prd title type status features created
walking-skeleton docs/work/prds/walking-skeleton.prd.md Walking skeleton — one real component, end to end through the hosted spine epic in-progress
workspaces
discovery
core-runner-protocol
editor
runner
web-next
core-testing
2026-07-12T10:24:14Z

Goal

A signed-in user connects a fixture repo; a cloud runner clones and installs it; discovery finds one real component; the editor renders that component on the board through the repo's own Vite in an iframe; clicking it inside the iframe selects it in the editor. One thin, honest, end-to-end vertical through every seam that matters: control plane ↔ runner provisioning, runner ↔ repo toolchain, and editor ↔ iframe canvas across the origin boundary (ADR-027/028/029).

Why

Every Veect risk that matters lives in the seams, not the parts. The original tech spec front-loaded exactly this with its M0 walking skeleton, but its acceptance criteria died with the Electron distribution (ADR-027). Nothing yet proves the hosted spine works at all, and every subsequent PRD (workspaces, discovery, design-doc, codegen, projects, ai) builds on these seams. If the spine is wrong, we must find out before nine PRDs are stacked on it.

Sequencing note: this epic builds on the sibling platform-retrofit epic (clean floor, ADR-022 traces, scaffolded optional cores incl. core-events + core-realtime, pre-approved editor deps). platform-retrofit must complete before this epic starts; cross-epic depends-on frontmatter is not supported, so this note (and story 01's Why) is the dependency record.

Stories