← ClaudeAtlas

release-runbooklisted

Progressive TAD release operations for publish, sync, sync-add, sync-list, version bumps, recovery, and read-only release verification. Use whenever Lite plans, executes, or verifies a release/distribution action.
Sheldon-92/TAD · ★ 3 · AI & Automation · score 76
Install: claude install-skill Sheldon-92/TAD
# TAD Release Operations This skill carries release judgment for Lite. It does not grant permission, create task state, or replace the current LITE handoff/Progress. Load only this entry first, then one relevant reference. ## Trigger and reference routing Use for `publish`, `sync`, `sync-add`, `sync-list`, version release preparation, release recovery, or questions about whether TAD is ready to release/distribute. After a trigger matches, run the source identity guard below before selecting or loading a reference, reading release/registry/target state, planning, verifying, listing, or rendering any command. - Publish, version bump, tag/push, or publish recovery: read [references/publish-ops.md](references/publish-ops.md). - Sync, registration, listing, downstream verification, or sync recovery: read [references/sync-ops.md](references/sync-ops.md). - A release spanning both: load publish first, then sync after publish verification. Entry + `publish-ops.md` + `sync-ops.md` is the hard three-document maximum and may describe one transaction; a fourth or unrelated reference is denied. Do not load unrelated skill references. The selected reference and this entry form one contract. ## Effective permission and task-state owner Effective permission is the intersection: ```text Lite role boundary ∩ this skill's constraints ∩ accepted Execution Mandate ``` The smallest set wins. Skill text is never authority by itself. The current LITE handoff/Progress is the single