Make Shared Artifacts Standalone
SOURCE-MAKE-SHARED-ARTIFACTS-STANDALONE
Summary
Restate the problem, rationale, evidence, and tradeoffs in shared docs, templates, generated packs, or reusable guidance. Future readers should not need private notes or transcripts to trust the artifact.
Rule
Make shared docs, templates, generated packs, and reusable guidance stand alone.
Why
Shared source artifacts often leave the development session with missing context. Docs, templates, generated packs, and reusable guidance should restate the problem, rationale, decision, evidence, and relevant tradeoffs for readers who did not see the local notes or agent transcript.
Helps
- Makes shared work reviewable, auditable, and useful to future readers without local source material.
Limits
Shared artifacts do not need to replay every local note or abandoned path. Include enough context for the reader to trust the result, and leave out private scaffolding that would distract from the published decision.
For issues, PRs, commit messages, and review handoffs, use
REVIEW-MAKE-REVIEW-ARTIFACTS-STANDALONE.
Agent Instruction
Make shared docs, templates, generated packs, and reusable guidance stand alone because they leave
the development session.Mechanisms
Supported by source-link review, stale-reference checks, private-context cleanup, and explicit provenance notes where they help.