メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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.
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.
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.
Validate architecture boundaries, standards alignment, and ADR need before planning a feature. Use when starting a new feature or invoking /govkit-architecture-preflight.
| name | govkit-implementation-plan |
| description | 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. |
You are writing an evaluation-driven implementation plan for a feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding.
Read these artifacts before planning:
features/<feature_name>/nfrs.mdfeatures/<feature_name>/acceptance.featurefeatures/<feature_name>/eval_criteria.yamlfeatures/<feature_name>/architecture_preflight.mddocs/{{docs_area}}/evaluation/eval_criteria.mddocs/{{docs_area}}/architecture/ (all files)The plan must:
Identify inbound ports, domain services, outbound ports, adapters, and API routes. Explicitly confirm no boundary violations.
List all implementation steps in order. Each step must:
eval_criteria.yaml and CI gate expectationsPredict before implementation begins:
eval_criteria.yaml thresholds are satisfied by designIf predicted averages are below required thresholds, adjust the plan before proceeding.
List conditions under which refactoring must occur:
Missing constraints, integration risks, performance concerns, security implications.
Do not generate implementation code. Plan must be executable as-is.