Sponsored by

Find leads on Reddit on auto pilot

Agent skills
governance

Topic: governance

76 skills in this topic.

implement Implement an approved plan. Write code, tests, and docs following the sprint checklist in NEXT-TASKS.md.
cortex-tms/cortex-tms 173
release Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
cortex-tms/cortex-tms 173
sync Synchronize task files and source-of-truth documents. Update NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README, and CHANGELOG to reflect current project state.
cortex-tms/cortex-tms 173
validate Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
cortex-tms/cortex-tms 173
new-command Scaffold a new CLI command for Cortex TMS following the existing codebase patterns.
cortex-tms/cortex-tms 173
plan Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.
cortex-tms/cortex-tms 173
adr-writer Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives
govctl-org/govctl 102
commit Commit changes with govctl integration — check work item status, update journal or notes, and run govctl check
govctl-org/govctl 102
gov Execute governed implementation workflow with work items, RFC/ADR checks, phase gates, testing, and closure. Use when: (1) User invokes /gov, (2) A non-trivial change needs work item tracking, (3) Implementation may require RFC/ADR handling
govctl-org/govctl 102
spec Maintain governance artifacts without implementation work. Use when: (1) Accepting or refining ADRs, (2) Clarifying or amending RFCs without code changes, (3) Governance-only docs/check/render updates
govctl-org/govctl 102
decision-analysis Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off
govctl-org/govctl 102
discuss Facilitate design discussion — research context, clarify requirements, draft RFC/ADR
govctl-org/govctl 102
guard-writer Write well-structured Verification Guards. Use when: (1) Creating a new guard, (2) Editing guard check commands or patterns, (3) User mentions guard, verification, or check
govctl-org/govctl 102
wi-writer Write well-structured work items with proper acceptance criteria. Use when: (1) Creating work items, (2) Adding acceptance criteria, (3) User mentions work item, task, WI, or ticket
govctl-org/govctl 102
rfc-writer Write well-structured RFCs with normative clauses. Use when: (1) Creating a new RFC, (2) Adding or editing RFC clauses, (3) User mentions RFC, specification, or normative requirements
govctl-org/govctl 102
migrate Adopt govctl in an existing project. Discovers undocumented decisions, backfills ADRs/RFCs, annotates source code. Use when: (1) Project has no governance yet, (2) User mentions migrate, adopt, onboard, or brownfield
govctl-org/govctl 102
quick Execute the fast path for trivial changes with minimal governance ceremony. Use when: (1) User invokes /quick, (2) Change is doc-only or non-behavioral, (3) No RFC or ADR work is needed
govctl-org/govctl 102
init Set up govctl in the current project. Installs the binary if missing, initializes governance structure.
govctl-org/govctl 102
agi-autonomous-controller AGI-level autonomous controller — self-healing, self-optimizing, constitutionally governed by arifOS F1-F13
ariffazil/arifOS 39
memory-archivist Cross-reference and synthesise daily memory files into patterns, insights, and carry-forward items. Use when asked to review memory, generate weekly synthesis, find forgotten tasks, detect decision patterns, or audit what was carried forward vs dropped. Also triggers on "what did I decide about X", "what's still pending", "weekly review", "memory synthesis", "what patterns do you see".
ariffazil/arifOS 39
tasks Task & project management — GitHub Projects (native), Linear (API), Notion DB (API)
ariffazil/arifOS 39
github GitHub operations — issues, PRs, commits, code search, CI/CD via gh CLI
ariffazil/arifOS 39
git-sync Git operations on VPS repos — status, commit, push, pull, diff, branch management
ariffazil/arifOS 39
skill-composer Chains multi-step workflows constitutionally — research → plan → judge → execute → verify → log → vault — without human step-by-step prompting
ariffazil/arifOS 39