Note optional second-order effects on material plans - #6
Merged
Merged
Conversation
Invite a one-line forward look only for architecture, breaking changes, several surfaces, or schema and deploy. Routine fixes and small plans omit it. Co-authored-by: Dennis Geldmacher <geldmacher.dennis@outlook.de>
geldmacher
marked this pull request as ready for review
September 24, 2026 13:20
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
2 participants
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
Material plans now include a short, optional forward look at second-order effects. The cue applies only when the change is architecture, a breaking change, several surfaces, or schema and deploy. Where those effects matter, the plan notes one line each for caller impact, data or migration, deploy and rollback, and security or auth, and marks speculation as speculation.
Routine fixes and small plans leave the note out. There is no new skill, no effects tree, and no required checklist or gate.
Version stays 7.4.5. Recent documentation-only commits leave the changelog and version bump to the release step.
Where it lives
skills/plan-work/SKILL.md— with the other plan contents, where the plan is writtendocs/manual-workflow.md— the same optional note in the usage guidedocs/behavior-validation.md— instruction-level expected decisions for a material change and a small planChecks
npm run validate,npm run context-budget, andnpm run link-checkpassed. Cursor plan instructions are about 2750 estimated tokens, under the 2900 limit.npm testpassed for the plugin, context, and packaging suites. The GitHub release tests fail in this environment because a global Git URL rewrite embeds credentials inorigin; the same file passes when that rewrite is absent.