docs(aep): walking skeleton as a living artifact (skeleton forest + product spine) - #17
Open
memorysaver wants to merge 1 commit into
Open
docs(aep): walking skeleton as a living artifact (skeleton forest + product spine)#17memorysaver wants to merge 1 commit into
memorysaver wants to merge 1 commit into
Conversation
…roduct spine) Design proposal recording why the walking skeleton rots while layer/wave/release-line stay maintained (no currency reader), grounded in Patton/Cockburn and AEP's own glossary + v2 multi-map roadmap. Proposes a two-level model (per-capability walking_skeleton forest + bet-anchored product spine), forcing functions via existing skills (no new commands), an additive-first migration, and looplia as the worked example. Proposal only — no schema/skill changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WFAeDemRdH8KzcYhiDTrto
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a design proposal doc:
docs/decisions/walking-skeleton-as-living-artifact.md.It records — precisely, so follow-up schema/skill PRs can be built against it — why AEP's walking skeleton rots while layer / wave / release-line stay maintained, and proposes a fix.
Why
Surfaced by the downstream product looplia: it faithfully maintains layer/wave/release-line across 23+ layers, but its walking skeleton is lost. Root cause is a framework-level asymmetry, not project discipline:
/aep-dispatchreads them every cycle) → maintained.The doc grounds this in the methodology (Patton / Cockburn: one walking skeleton per journey, each new journey introduced skeleton-first, the map is a deliberately-ephemeral conversation artifact that AEP repurposed as durable product-context without adding keep-it-alive machinery), and shows AEP already designed per-capability Layer-0 walking skeletons (
aep-v2-improvement-guideline.md§1.5; glossary "Capability Map") but the shipped implementation collapsed them onto global layer numbers.Proposed model (in the doc, not implemented here)
maps/<cap>/map.yamldeclares its ownwalking_skeleton(completes the §1.5 design).product/index.yamlgains a curated, bet-anchoredspinethreading the thinnest end-to-end path across capabilities;product.activitiesbecomes a build-generated union./aep-validatecurrency check,/aep-envisionreshape re-baseline,/aep-reflectre-slice/reshape split,/aep-mapskeleton-first,/aep-dispatchadvisory.Scope
git diff --stat= 1 file changed._shared/schema change, skill change,build-skills.sh, looplia edits, or downstream re-pin. Those are follow-ups, built against this doc.🤖 Generated with Claude Code
https://claude.ai/code/session_01WFAeDemRdH8KzcYhiDTrto