altivum-claude-plugins (PRIVATE dev repo)
Altivum's private Claude Code plugin dev repo — full history, work-in-progress, and
the source of truth for our plugins. Marketplace name: altivum-dev (team-only).
Hybrid model: develop + iterate here (private); ship vetted, stable releases to the
public repo AltivumInc-Admin/claude-plugins-public
(marketplace name altivum) via scripts/release.sh. End users /
the community install from the public repo; the team can also dogfood from here.
Team install (from this private repo)
Requires GitHub read access to this private repo (your normal gh/SSH git creds).
claude plugin marketplace add AltivumInc-Admin/claude-plugins
claude plugin install altivum-feature-dev-pipeline@altivum-dev
Release to the public repo
After bumping the plugin's version in its plugin.json and validating:
scripts/release.sh # default: altivum-feature-dev-pipeline
# scripts/release.sh <plugin-name> # for a specific plugin
This clones/updates the public working copy, mirrors the plugin dir, validates, then
commits + tags (<plugin>--v<version>, the claude plugin tag format) + pushes to claude-plugins-public.
Plugins in this marketplace
| Plugin | Version | What it does |
|---|
hone | 0.1.0 | Intent-anchored refinement loop: /hone:intent (author the north star) → /hone:gap (sensors measure deviation, clause-cited, zero-valid) → /hone:loop (pick → parallel build → functional gate → auto-PR/auto-merge → journal). Supersedes altivum-feature-dev-pipeline. |
altivum-feature-dev-pipeline | 0.4.0 | eval → plan → execute → deploy pipeline: a /ship orchestrator + phase commands, five analysis lenses + /recon audit + /refine continuous quality-gated loop (auto-PR/auto-merge), read-only analysis & review subagents, and a blocking pre-deploy gate. |
Repo layout
altivum-claude-plugins/
├── .claude-plugin/
│ └── marketplace.json # lists every plugin (source = subdir path)
├── scripts/
│ └── release.sh # mirror + validate + tag + push a plugin to the public repo
└── plugins/
├── hone/
│ ├── .claude-plugin/plugin.json
│ ├── commands/ agents/ workflows/ hooks/ README.md
└── altivum-feature-dev-pipeline/ # superseded by hone; kept during transition
├── .claude-plugin/plugin.json
├── commands/ agents/ workflows/ hooks/ README.md
Adding a new plugin
mkdir -p plugins/<new-plugin>/.claude-plugin and add a plugin.json
(name, description, version).- Add
commands/, agents/, hooks/ as needed.
- Append an entry to
.claude-plugin/marketplace.json with
"source": "./plugins/<new-plugin>".
claude plugin validate . to check, then commit + push.
Validate the whole marketplace anytime with:
claude plugin validate .
