Write Back Discipline
Description
--- name: write-back-discipline description: Skill governing when and how to persist useful outputs back into the knowledge base instead of leaving them only in conversation type: rigid --- # Write-Back Discipline Skill The cardinal rule of this knowledge system: **useful outputs must be written back.** Conversation is ephemeral. The knowledge base is persistent. If you generate something reusable, it belongs in the wiki. ## The write-back decision After generating any substantive output (an
Installation
Installs to ~/.claude/skills/bradduy-wiki-knowledge-compiler-write-back-discipline/SKILL.md
mkdir -p ~/.claude/skills/bradduy-wiki-knowledge-compiler-write-back-discipline && curl -fsSL https://raw.githubusercontent.com/bradduy/wiki-knowledge-compiler/HEAD/skills/write-back-discipline.md -o ~/.claude/skills/bradduy-wiki-knowledge-compiler-write-back-discipline/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Auto Update
Pull the latest ECC repo changes and reinstall the current managed targets.
Ecc Guide
Navigate ECC's current agents, skills, commands, hooks, install profiles, and docs from the live repository su
Epic Claim
Claim an epic issue, stamp coordination state, and sync local ownership.
Epic Publish
Publish a validated epic update back to the issue and local cache.
Epic Review
Mark epic review requested, approved, or changes requested.
Epic Unblock
Sweep blocked epic issues and reopen anything whose dependencies are closed.