メニュー
Write tests that encode WHY behavior matters, mapped to a spec's acceptance checks. Use when adding tests for a feature or reproducing a bug. For bug fixes, write the failing test FIRST. Targets the team's coverage bar on new code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SDLC orchestration plugin for Claude Code. Drives projects through a 9-phase software development lifecycle with company-configurable profiles, compliance gates, and quality enforcement. Triggers: "start sdlc", "sdlc setup", "initialize project lifecycle", "run phase gate", "advance phase", "sdlc status", "compliance check", "project setup wizard", "lifecycle management".
Add a new endpoint / route / use case / service the way this Node + TypeScript codebase already does it. Use when building an API surface, a request handler, a validator, a port/adapter, or a container registration in a Node/TypeScript repo. Finds the one canonical example and mirrors its layering, validation, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The Node realization of the core api-pattern skill.
Add a new module / CLI command / service function / loader the way this Python codebase already does it. Use when building a public surface, a command entry point, a data loader, a validator, or a new package module in a Python / uv repo. Finds the one canonical example and mirrors its layering, typing, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The Python realization of the core api-pattern skill.
Build a golden set for an agentic (LLM-powered) spec — the acceptance criteria for probabilistic behavior. Use when a spec's deliverable is an agent/prompt/tool and needs evals before build, or when adding cases from a production failure. Produces a versioned golden-set.yaml under eval-datasets/specs/<feature>/, referencing the spec file.
Add a new endpoint / MediatR command or query / handler / service the way this .NET codebase already does it. Use when building an API surface, a CQRS handler, a controller, a validator, or a DI registration in a .NET / Clean Architecture repo. Finds the one canonical example and mirrors its layering, validation, error model, and test shape — so agents extend the codebase instead of inventing a second way to do something it already does. The .NET realization of the core api-pattern skill.
Add a new endpoint / handler / service the way this codebase already does it. Use when building an API surface, a CQRS handler, a controller, or a service registration. Finds the one canonical example and follows it exactly — so agents reuse the established pattern instead of inventing a new one each run.
SOC 職業分類に基づく
| name | test-writer |
| description | Write tests that encode WHY behavior matters, mapped to a spec's acceptance checks. Use when adding tests for a feature or reproducing a bug. For bug fixes, write the failing test FIRST. Targets the team's coverage bar on new code. |
| allowed-tools | ["Read","Grep","Glob","Write","Edit","Bash"] |
A test that can't fail when the underlying business logic changes is wrong. Each test encodes why a behavior matters, not just what it does, and ties back to a spec acceptance check.
specs/NNNN-name.md; each acceptance check should map to at least
one test. Name tests so the mapping is legible (MethodName_Scenario_ExpectedResult).{{TEST_CMD}}) and confirm green before you consider it done. The Stop hook
will block the turn anyway if it's red — beat it to the check.