Add delivery plan: slice the build into parallel specifications#2
Merged
Conversation
Translate the seven build-plan stages into spec-kit-shaped specifications, surface the dependency graph the stage-linear narrative leaves implicit, and identify genuine parallel-working lanes. Names five prerequisite document slices (register, knowledge-model, seam-contract, vignette, architecture) and sixteen build specifications, with the scorer (SPEC-07) identified as the critical-path linchpin and the depth theses fanning out behind it. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K11vXz8rcRbRio7N6ps1s6
b024804 to
728a39a
Compare
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
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 this adds
A new candidate canonical document,
assay-delivery-plan.md, that reads the existing root-level documents (assay-scaffold.md,assay-build-plan.md,assay-ui-design.md) and answers the question: how do we deliver this, and where can work run in parallel?It does not re-sequence the build plan or introduce methodology (that stays in the register, DEC-2). It translates the seven stages into spec-kit-shaped slices and makes the implicit dependency structure explicit.
Key content
D2 → D3 → SPEC-05 → SPEC-06 → SPEC-07 → SPEC-15 → SPEC-16, with float called out (generator SPEC-08 is sacrificial scope).Notes for review
assay-*.mdconvention and the task framing ("root level documents"); it is marked a candidate addition to the canonical set, not yet ratified.🤖 Generated with Claude Code
Generated by Claude Code