Review committed and working-tree changes since a fixed point against repository standards, the originating spec, and correctness or risk. Use when the user asks to review a branch, pull request, work in progress, current changes, or changes since a commit, branch, tag, or merge base.
Relentlessly clarify a fuzzy engineering or product plan one decision at a time while maintaining durable domain language and architectural decisions. Use when the user wants to grill, stress-test, think through, or sharpen a plan, design, feature, trade-off, or architecture choice before writing a spec or code.
Implement the user's current engineering task with minimal, verified changes, test-driven discipline, and a final code review. Use when the user asks Codex to build, fix, implement, modify code, execute a concrete task, or complete work from specs/slug/issues.md.
Break a product spec, technical spec, design note, or current plan into one or more dependency-aware, agent-executable issue briefs under specs/slug/issues.md. Use when the user asks to split work into issues, implementation tasks, tickets, milestones, TODOs, or independently verifiable slices.
Convert current context, repo findings, or an existing thinking note into durable product and technical specification markdown under specs/slug/. Use when the user asks to write, generate, update, revise, or turn a plan or discussion into a spec, PRD, product requirements document, or technical proposal.
发布前对应用程序进行全面审计，检查安全性、数据泄露、可靠性、并发状态完整性、可访问性和 UI 一致性。适用于上线、发布或交付前的安全检查。
Convert a finished spec or design document into a right-sized execution plan and /goal starter for Codex. Use when the user has a completed spec/design and wants phases, a phased plan, an execution checklist or JSON ledger, a progress file, hard acceptance criteria, batch-processing lists, or a /goal prompt. Triggers include "基于这个 spec 写 /goal plan", "把设计文档拆成可执行 phase", "生成 phased plan 和 progress 文件", "逆向清单做成 checklist 分批处理". Routes small tasks to a lighter ledger instead of full phases. Not for brainstorming, writing the original spec, or implementing the plan.
Detect software architecture bad smells, algorithmic complexity hotspots, and anti-patterns in a codebase. Produces a detailed markdown report identifying violations of architectural principles, design patterns, code quality, and performance complexity. Triggers on: smell, code smell, architecture smell, find anti-patterns, detect bad smells, complexity analysis, 代码坏味道, 架构坏味道, 反模式, 找出坏味道, 复杂度分析.