organvm-governance-pack
Curated bundle of governance and quality skills for ORGANVM ecosystem management. Includes ecosystem autopsy and discovery, promotion readiness, onboarding flows, stranger testing, repository standards, verification, and coding standards. Use when establishing or auditing governance practices for repositories.
Best use case
organvm-governance-pack is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Curated bundle of governance and quality skills for ORGANVM ecosystem management. Includes ecosystem autopsy and discovery, promotion readiness, onboarding flows, stranger testing, repository standards, verification, and coding standards. Use when establishing or auditing governance practices for repositories.
Teams using organvm-governance-pack should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/organvm-governance-pack/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How organvm-governance-pack Compares
| Feature / Agent | organvm-governance-pack | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Curated bundle of governance and quality skills for ORGANVM ecosystem management. Includes ecosystem autopsy and discovery, promotion readiness, onboarding flows, stranger testing, repository standards, verification, and coding standards. Use when establishing or auditing governance practices for repositories.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ORGANVM Governance Pack A curated bundle of skills for managing repository lifecycle, quality gates, and governance compliance across the ORGANVM ecosystem. ## What's Included - **ecosystem-autopsy** — Discovery entrypoint. Orchestrate `organvm ecosystem` + `organvm irf` to surface unregistered repos and drift, then emit migration signals routing to downstream skills below - **promotion-readiness-checklist** — Assess repositories against promotion state requirements (LOCAL → CANDIDATE → PUBLIC_PROCESS → GRADUATED) - **repo-onboarding-flow** — Scaffold and integrate new repositories with seed.yaml, CI/CD, and documentation - **stranger-test-protocol** — Validate that documentation is comprehensible to someone with zero context - **github-repository-standards** — Enforce repository organization and README standards - **verification-loop** — Comprehensive build/type/lint/test/security verification - **coding-standards-enforcer** — Automated code style enforcement with linters and pre-commit hooks ## Getting Started Install this bundle to establish governance practices across your repositories. The recommended workflow: 1. **Discovery:** Run ecosystem-autopsy to map the workspace, find unregistered repos, and emit drift signals 2. **New repos:** Use repo-onboarding-flow to scaffold and integrate 3. **Quality baseline:** Apply coding-standards-enforcer and verification-loop 4. **Documentation:** Run stranger-test-protocol to validate docs 5. **Promotion:** Use promotion-readiness-checklist to assess and advance governance state This pack is designed for the ORGANVM eight-organ ecosystem but applies to any multi-repo system with governance requirements. Phase 1 (Discovery) feeds the downstream phases via the signal records ecosystem-autopsy emits.
Related Skills
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
session-governance-audit
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.
security-essentials-pack
Curated bundle of essential security skills for building secure applications. Includes threat modeling, hardening guides, audit checklists, compliance frameworks, and contract analysis. Use when establishing security practices for a project.
python-packaging-patterns
Structure Python projects for distribution with pyproject.toml, src layouts, dependency management, and publishing workflows. Covers packaging tools (hatch, setuptools, flit, poetry), versioning strategies, and editable installs. Triggers on Python project setup, packaging configuration, or dependency management requests.
python-backend-pack
Curated bundle of essential Python backend development skills. Includes FastAPI patterns, packaging, database migrations, CLI design, and Redis caching. Use when building Python API services or backend systems.
monorepo-devops-pack
Curated bundle for managing monorepos with containerized deployment pipelines. Includes monorepo management, Docker containerization, CI/CD deployment, and coding standards. Use when setting up or improving multi-package repository infrastructure.
fullstack-starter-pack
Curated bundle of essential skills for fullstack web development. Installs API design, testing, deployment, backend patterns, frontend architecture, and code quality skills together. Use when starting a new fullstack project or onboarding onto a codebase.
agent-development-pack
Curated bundle for building, testing, and coordinating AI agent systems. Includes multi-agent orchestration, agent testing, cross-agent handoff, MCP server building, and prompt engineering. Use when developing AI agent workflows or multi-agent systems.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.