codex-sdd-plugin

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

Refines ideas iteratively. Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

在需求已确认并进入执行阶段后，严格依据对应需求目录中的 `spec.md`、`tasks.md`、`log.md` 逐项实施任务、展示可验证证据并同步执行记录。当用户要求进入 apply 阶段、根据已确认 spec 开始编码、按 tasks 逐条落实实现、默认一次做一项后等待确认，或明确要求“全部完成”后顺序批量执行时使用。

在一个 change 已完成实现、修正和审查后，负责做归档收尾与知识沉淀。用于用户要求 archive、归档需求目录、从 `log.md` 提炼知识发现与踩坑记录、逐条确认是否沉淀到 `docs/knowledge/`，并将已完成的 change 目录移入 `docs/archives/` 时使用。

在 `spec-propose` 阶段为单个需求生成结构化 `spec.md`。用于把已澄清的目标、约束、接口、风险和验收条件落成 AI 可消费的 Markdown 规格，并与本插件内的 `spec-driven-development` 规范保持一致时使用。

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

在需求已经过 `spec-review`、进入修正迭代阶段后，根据 review 结论、缺陷清单或验证失败结果，对既有实现执行增量修正。用于用户要求 fix、根据 review findings 修问题、补齐遗漏的 spec 条目、修复回归或质量问题、继续迭代已完成实现，并且每次修正后都必须同步 `spec.md`、`tasks.md`、`log.md` 时使用。

在仓库根目录初始化项目规范文档骨架并生成最小 README 模板。用于用户要求创建 `docs/` 规范目录、搭建 `rules`/`knowledge`/`changes`/`archives` 工作区、初始化 spec 文档承载结构，或在已有 `docs/` 存在时按 `docs_v2`、`docs_v3` 等安全回退命名创建新文档骨架时。

在需求提案阶段以“人主导、AI 辅助”的方式梳理代码现状、逐轮澄清需求，并在 `docs/changes/templates/` 下为单个需求创建 `spec.md`、`tasks.md`、`log.md`。当用户要求先做方案设计、先写规格文档、先澄清再实现、进入 propose/spec 阶段，或明确要求在编码前完成设计审视与确认门控时使用。

在需求进入审查阶段后，对照已确认的 `spec.md`、`tasks.md`、`log.md` 与实际代码执行两阶段代码审查。用于用户要求做 review、核对实现是否符合 spec、进入 review 阶段、先查功能一致性再查代码质量、输出 Critical/Important/Minor 问题，或决定是否回退到 `spec-apply`/`spec-fix` 修正时使用。

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.