20 tagged project governance, measured the same way as everything else here.
Browse within: ai-development 10codex-plugin 8openai-codex 8
Skill Claude CodeCodex
A project-governance skill for examining a codebase, its development process, and its supporting materials. It can follow an implementation plan, investigate root causes, and organize project-wide responsibilities when explicitly asked.
Solismuchengxue/skill_swift_cycle
Skill Claude CodeCodex
A lightweight project-maintenance workflow documented in Chinese and English. It reads the project's current files and records what is confirmed, inferred, unknown, changed, and verified.
Skill Claude CodeCodex
A read-only investigation mode for finding root causes, semantic drift, or incomplete capabilities before making changes. It prevents project files from being edited during diagnosis.
Skill Claude CodeCodex
Use when the user wants one simple entry to initialize, update, repair, migrate, or resume the CoTend development framework, or asks whether a project can continue under it. Delegates once to the currently installed Project Init, propagates its canonical result, and returns one outer handback without becoming a second…
Skill Claude CodeCodex
Initialize, update, repair, migrate, or resume under CoTend, including named upstream Dual handoff/adoption/install or an external platform-adapter sync. Resolves impact before broad reads, loads triggered owners, preserves protected boundaries, validates real governance writes, and returns one handback.
Skill Claude CodeCodex
A governance guide for long-running, multi-stage software or project work. It helps establish the authoritative project location, ownership, permissions, review gates, delivery evidence, and handover rules.
Skill Claude CodeCodex
Govern open development batches, non-routine Git or repository boundaries, version closeout, artifacts, deployment, rollback, or production state. Not for ordinary implementation inside an already-governed batch.
Skill Claude CodeCodex
Govern engineering contracts, architecture, technical debt, testing, or refactoring when project rules are missing, conflicting, or changing. Not for ordinary code changes already governed by active project instructions.