gov
gov delivers substantive code changes within your repository's governance framework, enforcing RFC and ADR authority while maintaining work-item traceability. It establishes current state, validates against normative specifications, and ensures completion evidence before closure.
gov executes implementation under your repository's governance model, tracking work items against RFCs and ADRs.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
gov executes implementation under your repository's governance model, tracking work items against RFCs and ADRs. gov delivers substantive code changes within your repository's governance framework, enforcing RFC and ADR authority while maintaining work-item traceability. It establishes current state, validates against normative specifications, and ensures completion evidence before closure.
Use it when
- gov manages the RFC and ADR lifecycle to establish authoritative decision records that guide implementation.
- gov tracks implementation work items with full traceability and closure verification.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
govctl-org/govctl/gov · repository language: Rust
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What is gov and how does it support governed implementation?
gov is an MIT-licensed skill that delivers substantive code changes within your repository's governance framework. It enforces RFC and ADR authority, maintains work-item traceability, establishes current state, validates against normative specifications, and ensures completion evidence before closure.
How does gov handle RFC and ADR authority in implementation workflow?
gov manages the RFC and ADR lifecycle to establish authoritative decision records that guide implementation. It uses these records as the foundation for executing code changes, ensuring that all substantive modifications are rooted in documented architectural decisions and formal requests for change.
How does gov track work item traceability and implementation closure?
gov tracks implementation work items with full traceability and closure verification. It maintains linkage between work items and code changes, records completion evidence, and ensures that each item is properly closed only when all governance requirements are satisfied.
Can gov verify implementation against risk-scoped guards and compliance?
Yes. gov verifies implementation against risk-scoped guards and compliance requirements. It validates code changes against normative specifications and governance rules before allowing closure, ensuring that all risk-scoped constraints are met throughout the delivery process.
What does gov do to establish governance baseline and discover work items?
gov establishes your governance baseline by discovering active work items and current state. It scans your repository to identify existing governance structures, active implementation tasks, and pending work, providing visibility into what needs to be tracked and governed.
How can I implement code changes with gov's governance model?
To implement with gov's governance model, you execute changes within the framework it establishes. gov enforces RFC and ADR authority, tracks your work items with traceability, verifies against compliance guards, and manages closure—ensuring all code delivery follows your governance rules.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Governed Implementation
Deliver $ARGUMENTS under the repository's governance model. Use this skill for
substantive implementation; use quick for trivial non-behavioral changes and
spec when no implementation is required.
Operational Baseline
Discovery
Establish current state before choosing a workflow:
govctl status
govctl work list active
govctl work list queue
govctl loop list open
govctl search <topic>
Read a matching Work Item with govctl work show <WI-ID> and inspect relevant
RFCs or ADRs through their show commands. Use govctl <resource> --help for
current syntax and diagnostics for recovery. In the govctl repository itself,
invoke the development binary as cargo run --quiet --.
Hard Stops
- RFCs are authoritative. Stop when the requested behavior conflicts with a normative RFC or is materially unspecified.
- Do not implement behavior that depends on a draft RFC.
- Obtain user
(truncated - see the full file via the links below)
File tree — 1 file
.claude/skills/gov/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Execute implementation under governance model with RFC/ADR authority”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
commit creates a coherent, single-outcome VCS change while enforcing governance rules and linking to active work items. It detects your repository type (Jujutsu or Git), validates against govctl policies, and ensures unrelated changes stay separate. The skill handles traceability, commit message formatting, and post-commit verification in one workflow.
RFC Writer guides you through composing normative RFCs—product contracts with observable obligations, invariants, and compatibility rules. It enforces separation between specification prose and implementation details, ensures each clause is independently testable, and hands off lifecycle operations to dedicated governance tools. Use it to author the contract itself, not design rationale or execution scope.
ADR Writer guides you through documenting architectural decisions by establishing the problem context, weighing real alternatives, explaining why one direction won, and recording both benefits and costs. It enforces boundaries between decision rationale and product obligations, keeping ADRs focused on justification rather than execution or RFC-level commitments.
discuss guides you through governance design conversations grounded in your repository's existing context. It helps identify constraints, compare design options, and produce durable artifacts like RFCs and ADRs that capture decisions and obligations without moving into implementation.
migrate helps you add govctl governance to an established project by examining existing evidence—documentation, code structure, VCS history, and configuration—to recover consequential decisions and specifications. It guides you through a discovery phase, presents candidates for backfill as Architecture Decision Records, RFCs, or Work Items, and executes only authorized changes in small coherent batches. The workflow preserves traceability, respects existing artifact state, and stops when evidence conflicts or authorization is unclear.
Decision Analysis exposes assumptions, failure paths, and success conditions for high-stakes design choices. It uses premortem and backcast reasoning to rank options against constraints, reversibility, and evidence quality, then returns a risk-calibrated recommendation. The skill routes obligations and rationale to their authoritative destinations—RFC, ADR, Work Item, or verification—rather than creating artifacts itself.
More skills detach (MIT)