Menu
Gate check before tagging and releasing a new version. Run this skill before any `git tag vX.Y.Z` operation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | release-readiness |
| description | Gate check before tagging and releasing a new version. Run this skill before any `git tag vX.Y.Z` operation. |
| triggers | ["release version X","tag a release","prepare for release","is this ready to release?"] |
| references | ["docs/runbooks/release.md","docs/changelog.md",".github/workflows/ci.yml"] |
Before any version tag or deployment to a production/shared instance.
Work through this checklist in order. Do not proceed to the next step if any item fails.
pytest -v
All tests must pass. Zero failures, zero errors.
grep -n "Unreleased" docs/changelog.md
There must be at least one entry under ## [Unreleased].
If the section says _(nothing pending)_, the changelog has NOT been updated — stop here.
Using Semantic Versioning:
MAJOR — breaking API or behaviour change (existing clients must change)MINOR — new feature, backwards-compatiblePATCH — bug fix, backwards-compatibleCheck docs/changelog.md for the current version to determine the next version.
In docs/changelog.md:
## [Unreleased] to ## [X.Y.Z] — YYYY-MM-DD## [Unreleased] section at the top with _(nothing pending)_git add docs/changelog.md
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z
git push origin vX.Y.Z
Check that the CI workflow passes on the tagged commit.
See .github/workflows/ci.yml.
.env.example if any new environment variables were introduced.README.md if setup instructions changed.python telegram_bot.py (if configured).pytest -v exits 0docs/changelog.md [Unreleased] section had entriesgit tag vX.Y.Z created.env.example updated if neededREADME.md updated if neededIf a release is found to be broken after tagging:
git tag -d vX.Y.Z && git push origin :refs/tags/vX.Y.Zgit revert HEADOnboard a new client/company onto this platform's real Agentic OS: create the company record, scan its websites/repos, auto-provision specialist agents, activate its 24x7 agency runtime, and know exactly which "OS" building blocks (memory, integrations, dashboard) already exist versus which are roadmap gaps. ADAPTED FROM: a third-party giveaway skill ("agentic-os-installer" by Gennaro Santoro / Operations Heroes) that described a generic vault + Google-suite + skill-pack installer. That skill's product (Obsidian vault, Gmail/Calendar/ Drive wiring, "skill packs") does not exist in this repo and its promotional content (Skool community link) does not belong here. This is a clean-room rewrite that keeps the useful idea — "stand up a working agency OS for a client from a short checklist" — and maps every step to the real module that already implements it in this codebase, per CLAUDE.md architecture rules.
Agile sprint planning, velocity tracking, and burndown metrics for agent-managed projects
Initiative-level portfolio management with dependency tracking and milestone coordination
AI-assisted engineering impact analysis — productivity metrics and code quality insights
Cross-harness agent patterns — standardize agent execution across different coding assistants
Temporal context graph for agent memory — track entity relationships and state changes over time