Accelerated-Innovation

govkit-eval-suite-planning

Plan a provider-neutral evaluation suite for an LLM feature. Use when the user asks to plan model evaluations or invokes /govkit-eval-suite-planning.

govkit-genai-preflight

Validate Level 5 provider-neutral LLM architecture decisions before planning. Use after /govkit-architecture-preflight for features with mode:llm or when invoking /govkit-genai-preflight.

govkit-multi-agent-design

Design a governed agent topology and produce agent_topology.md. Use for multi-agent features, delegation, adaptive orchestration, or when invoking /govkit-multi-agent-design.

Generate an ordered implementation checklist with evaluation compliance summary from a validated preflight. Use when the user asks to draft implementation steps or invokes /govkit-implementation-plan.

govkit-spec-planning

Generate a feature plan (plan.md) and eval_criteria.yaml from NFRs and acceptance scenarios. Use when the user asks to plan a feature or invokes /govkit-spec-planning.

incremental-planning

Plan implementation work as a sequence of the smallest independently demonstrable increments. Use when given a feature request, a body of work, or any implementation task that must be broken down or sequenced BEFORE coding — it classifies the request, identifies the next demonstrable behaviors, and recommends (advisory) an appropriate model tier for implementing each increment. This skill plans; it does not write code, tests, commits, or architecture.

superior-unit-tests

Write or improve unit tests following a strict determinism, F.I.R.S.T., and fast-feedback-budget discipline. Use when asked to write tests, improve tests, review test quality, classify tests, or assess a test suite against a 30-second fast-feedback budget. Invokes a structured output protocol that identifies behaviors under protection, classifies each test by level and feedback loop, and flags nondeterminism risks.

unit-testing-rubric

Standards for writing, reviewing, and evaluating unit tests. Use whenever writing new tests, reviewing existing tests, deciding what to test, assigning a test to a fast vs. full feedback loop, or diagnosing flaky, slow, or low-value tests. Covers structural fidelity, the FIRST properties, behavioral invariants, and coverage-as-diagnostic.

zom-representation

Zero-One-Many Representation Evolution — use this skill whenever working with existing code that needs to change, grow, or be refactored. Triggers include: "refactor this", "add a new X to this", "this is getting messy", "how should I represent this", "there's a lot of duplication here", or any time numbered variables, growing conditionals, repeated parameter groups, or scattered constants are observed. Also use proactively when reviewing code for design quality, assessing coherence and development level, or applying the 8 Code Virtues framework. Do not wait to be asked — if you see representation pressure in the code, surface it.

govkit-architecture-preflight

Validate architecture boundaries, standards alignment, and ADR need before planning a feature. Use when starting a new feature or invoking /govkit-architecture-preflight.

govkit-ui-architecture-preflight

Validate UI architecture boundaries, backend contracts, and ADR need before spec planning. Use when starting a new UI feature or invoking /govkit-ui-architecture-preflight.

govkit-ui-implementation-plan

Generate an ordered UI implementation checklist from a validated plan and preflight. Use when the user asks to draft UI implementation steps or invokes /govkit-ui-implementation-plan.

govkit-ui-spec-planning

Generate a UI feature plan (plan.md) and eval_criteria.yaml from NFRs, acceptance scenarios, and architecture preflight. Use when the user asks to plan a UI feature or invokes /govkit-ui-spec-planning.

API & Backend Listed

govkit-adr-author

Author an Architecture Decision Record for a new pattern, exception, or boundary change. Use when the user asks to write an ADR or invokes /govkit-adr-author.

govkit-fix-record

Author a fix record for a defect that restores already-established behavior. Use when the user reports a bug, asks to fix a defect, or invokes /govkit-fix-record.

govkit-pr-author

Author and open a governed pull request that carries its governance evidence. Use when the user asks to open a PR, create a pull request, or invokes /govkit-pr-author.

atomic-commit

Create honest atomic Git commits by choosing one coherent work batch before editing, keeping the whole repository green, resolving every untracked file, staging the entire root with `git add .`, and pausing for human review before committing. Use when starting commit-sized work, completing a demonstrable implementation slice, running a series of refactorings, preparing or making a commit, or discussing atomic commits and trustworthy history. Do not use partial staging or retrospectively compose commits from an already mixed working tree.

code-object-naming

Diagnose and improve names for code objects — variables, functions, methods, classes, modules, and parameters — using Ottinger's naming guide. Use when asked to review, choose, or rename identifiers; when names are vague, lying, redundant, or noisy; when planning an incremental rename refactor; or when extraction moments arise from hard-to-name code. Use representation-refactor-review instead for a broad craft or knowledge- representation review in which naming is only one concern.

legacy-code-safety

Establish trustworthy feedback around poorly understood or weakly tested existing code before changing it. Use for characterization or approval tests, test-harness access, seams, sensing and separation, dependency breaking, and incremental replacement of risky live code. Once a fast trustworthy boundary exists, use unit-testing to drive the requested new behavior.

representation-refactor-review

Review code and propose evidence-based representation improvements using Tim Ottinger's Eight Code Virtues, SPOT, ZOM, and the improvement test. Use for broad craft, refactoring-readiness, clean-code, knowledge-representation critique, or discovering data clusters, data classes, and class-splitting boundaries. Do not use for bug/security-only review, implementing behavior test-first, or a focused identifier-naming task; those belong to the relevant specialist workflow.

story-splitting-for-delivery

Split oversized features, epics, and stories into thin, demonstrable, deployable slices through progressive admission: start with a closed end-to-end skeleton, then admit one case at a time. Use to choose or sequence delivery slices, including message, schema, import, API, form, path, rule, persona, or channel rollouts. Do not use merely to format an already-chosen split as user-visible outcomes; that belongs to user-pov-sliced-stories.

unit-testing

Implement or extend production behavior test-first, or diagnose focused unit-test quality and flakiness, using red-green-refactor, ZOMBIES, Tidy First?, FIRST microtests, and Save Your Game checkpoints. Use for TDD, microtests, test-first bug fixes, flaky tests, and refactoring within an active green cycle. Do not use to choose delivery slices, format user stories, conduct a broad representation review, or perform a focused identifier-naming analysis; those belong to the corresponding sibling skills.