feat(plan): Plan-as-pointer brief variant for host planning artifacts - #71
Merged
Conversation
…#67) Hosts may plan through their OWN artifacts with distinct change processes (ADRs, enhancement proposals, normative specs). PDCA's Plan step should accept a reference to the host's existing planning artifact rather than impose its own document shape (#67 requirement 4). - New templates/plan-pointer.md.tpl: a thin brief carrying a `Planning artifact:` pointer plus the minimal driver-parsed fields (slug, success criterion, repo + branch target, test file, disposition). Same parsed-field contract as a normal brief, so the state machine treats it as PLANNED with no engine change. - brief.planning_artifact() reader; the planner prompt offers the pointer template as a third option (alongside brief / design-proposal), and the Do builder prompt reads the referenced artifact as the authoritative plan and cites it. - docs/03-plan.md: "The Plan can be a pointer". Tests: new PlanPointerBrief class (parsed-field contract, planning_artifact reader, pointer-brief flows Do->Check->sign-off offline). Suite green (133). Part of #67 (does not close it). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Eduard Ralph <15236434+eduralph@users.noreply.github.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
Part of #67 (project-neutrality epic) — requirement #4: make the Plan artifact a pointer, not a prescribed shape. Does not close #67.
Hosts may plan through their own artifacts with distinct change processes (ADRs, enhancement proposals, normative specs under change control). PDCA's Plan step should accept a reference to the host's existing planning artifact as the Plan, rather than imposing its own document format.
Changes
templates/plan-pointer.md.tpl(new): a thin brief carrying a- **Planning artifact:** <path|url>pointer plus only the fields the driver parses (slug, success criterion, repo + branch target, test file, disposition). It uses the same parsed-field contract asbrief.md, so the state machine treats it as a normalPLANNEDbrief — no engine change.brief.planning_artifact()reader; the planner prompt offers the pointer template as a third option (alongsidebrief.md.tpl/design-proposal.md.tpl), and the Do builder prompt reads the referenced artifact as the authoritative plan and cites it.docs/03-plan.mdgains a "The Plan can be a pointer" subsection.Verification
PlanPointerBriefclass covers the parsed-field contract, theplanning_artifactreader (pointer present vs. a plain brief →""), and a pointer-brief flowing Do→Check→sign-off offline.🤖 Generated with Claude Code