菜单
Use when the goal is to drive the repo toward production readiness instead of just passing one local slice. Enforces cross-component release gates, rollout prerequisites, and evidence for a real ship decision.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | dr-production-readiness |
| version | 2026-03-26.1 |
| description | Use when the goal is to drive the repo toward production readiness instead of just passing one local slice. Enforces cross-component release gates, rollout prerequisites, and evidence for a real ship decision. |
Use this skill when the real goal is:
This skill sits above per-slice completion. Passing one feature or test cluster is not enough.
dr-repo-referencedocs/BASE_SPEC.mddocs/PRODUCTION_CHECKLIST.mddocs/RUNBOOKS.mddocs/ON-CALL.mddocs/AGENT-ROLLOUT.mdSTATUS.mdROADMAP.mdDo not use "production-ready" loosely.
For this repo, it means:
Produce a readiness block:
## Production Readiness
- Portal:
- Agent:
- Gateway:
- Installer:
- Migrations:
- Deployment:
- Runbooks / On-call:
- Security:
- Remaining blockers:
- Recommended next slice:
unknown rather than pretending it is greenOnly call the repo production-ready when docs/PRODUCTION_CHECKLIST.md is satisfied or every remaining unchecked item is explicitly marked as an out-of-scope operational decision.
Use when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.