菜单
The team's bug-fix procedure: reproduce with a FAILING TEST first, then fix, then prove the test passes. Use whenever a bug is reported. Do not start by patching — start by reproducing. For deep root-cause hunts, invoke the debugger agent from inside this procedure.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | diagnose |
| description | The team's bug-fix procedure: reproduce with a FAILING TEST first, then fix, then prove the test passes. Use whenever a bug is reported. Do not start by patching — start by reproducing. For deep root-cause hunts, invoke the debugger agent from inside this procedure. |
| allowed-tools | ["Read","Grep","Glob","Bash","Edit","Write"] |
A fix isn't done when the code changes — it's done when a test that failed because of the bug now passes. This procedure is mandatory for bug fixes; it makes the fix provable, not asserted.
