القائمة
一个专业的项目规划助手，能够通过多轮对话与你协作，从需求理解到方案设计，最终输出完整的项目计划文档
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Extremely strict maintainability review focused on structural simplification, abstraction quality, and spaghetti-condition growth. Not a general correctness review -- this is a deep code quality audit that pushes for "code judo" moves that delete complexity. Use when asked to "code review", "maintainability review", "code quality audit", "/code-review", or "/review-quality".
Spawns a verifier subagent to audit your work: traces what was done, reviews the diff, runs builds/tests, and delivers a PASS/FAIL verdict. Auto-retries fixes up to 3 rounds. Use when asked to "check work", "verify changes", "self-verify", "/self-verify", "/check", or "/verify".
轻量需求头脑风暴 — 先扫代码库确认前置条件，再用 2-3 轮聚焦讨论锁定范围和方案。Use when user says "brainstorm this feature", "需求讨论", "sdd brainstorm", or wants to explore a feature idea before writing specs. Replaces heavyweight brainstorming workflows that burn tokens.
按规格文档的 Ticket 逐个实现代码，每个 Ticket 独立上下文避免幻觉。内置 todo 进度追踪，支持 LSP 诊断、worktree 隔离、子智能体委派等按需升级。Use when user says "implement ticket", "实现这个任务", "sdd implement", "开始实现", or wants to execute tasks from a spec. Reads .plan/spec.md for task breakdown.
将头脑风暴结论转化为结构化规格文档，包含需求、技术设计、任务拆解和决策记录。Use when user says "write spec", "写规格", "sdd spec", or wants to formalize a brainstormed idea into an implementable specification. Reads .plan/brainstorm.md if available.
Comprehensive quality analysis tool for Claude Skills. Evaluates skills from GitHub URLs, marketplace links, ZIP files, or local directories across five dimensions (structure, security, UX, code quality, integration) using balanced scoring and three output modes (comprehensive report, interactive review, pass/fail certification). Triggers on "analyze skill quality", "review this skill", "evaluate skill", or "skill quality check".
| name | designer |
| description | 一个专业的项目规划助手，能够通过多轮对话与你协作，从需求理解到方案设计，最终输出完整的项目计划文档 |
基于需求分析，提供 2-3 个可行的技术方案，每个方案包括：
.plan/plan.md 文件.plan/plan.md 文档结构# 项目计划文档
## 1. 项目概述
- 项目名称
- 业务背景
- 核心目标
- 成功标准
## 2. 需求分析
### 2.1 功能需求
- [ ] 核心功能 1
- [ ] 核心功能 2
- [ ] ...
### 2.2 非功能性需求
- 性能要求
- 安全性要求
- 可扩展性要求
- 其他约束
## 3. 技术方案
### 3.1 方案对比
| 方案 | 技术栈 | 复杂度 | 开发周期 | 适用性 |
|------|--------|--------|----------|--------|
| 方案A | ... | ... | ... | ... |
| 方案B | ... | ... | ... | ... |
### 3.2 最终方案
- 选择的方案
- 选择理由
- 技术架构图（文字描述）