docs(cc-218): spike tracking infrastructure — docs/spikes/ + body convention#125
Merged
Conversation
…vention v0.3.0 M0. The `spike` epic was already in pm-schema v1.2 (validate.sh valid_epic + schema.md §2.4.5) and CC-209 already carries it — so the remaining CC-218 scope is the spike-result home and the body convention. - docs/spikes/README.md (new) — spike-ticket body convention (fits the standard Problem/Why/Requirement body per schema §2.5; Investigation scope / Done-when / Result log live inside the Requirement section) + the docs/spikes/CC-NNN.md result-file format - pm/schema.md §2.4.5 — pointer to docs/spikes/README.md Docs-only. validate.sh error set unchanged vs main (31 pre-existing). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
v0.3.0 milestone M0 (CC-218). Spike-tracking infrastructure.
Most of CC-218's stated scope was already done: the
spikeepic is invalidate.shvalid_epic()+pm/schema.md§2.4.5 (pm-schema v1.2), and CC-209 already carries thespikeepic. The remaining work:docs/spikes/README.md(new) — defines the spike-ticket body convention and thedocs/spikes/CC-NNN.mdresult-file format. Schema-consistent:pm/schema.md§2.5 fixes the entry body toProblem/Why/Requirement, soInvestigation scope/Done-when/Result logare documented as a convention inside theRequirementsection, not as new sections.pm/schema.md§2.4.5 — pointer todocs/spikes/README.md.This is the M0 prerequisite for M5's spike agent (CC-220) and the CC-209 spike.
Notes
Docs-only diff (a new doc + a schema-doc prose line, no scripts) — no
/pr-gateper the data-vs-architecture policy.pm/scripts/validate.sherror set is unchanged vsorigin/main(31 pre-existing E-codes).Closes CC-218.
🤖 Generated with Claude Code