qiniu-ai-sdk

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work. In this repository, package or lane branches must close through package-first evidence and integration handoff rather than the generic local merge or PR menu.

Use when executing repo-wide or lane-scoped SDK changes in this repository that must follow bounded change packages, qiniu-ai worktree/package commands, evidence bundles, review packets, promotion decisions, and integration-branch handoff. Trigger on requests to open a phase package, spawn or integrate a lane, prepare a review handoff, or land multi-subsystem SDK work without widening scope.

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

Use when starting feature work that needs isolation from the current workspace or before executing implementation plans. In this repository, prefer qiniu-ai worktree commands for lane or package-first delivery; fall back to generic git worktree flows only for non-package branches.

Run verification commands and confirm output before claiming success

Use when you have a spec or requirements for a multi-step task, before touching code. In this repository, multi-subsystem or lane-scoped work must create the package brief first and keep the plan aligned with the bounded package contract.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when debugging ConnectRPC Connect/gRPC-Web protocol issues — framing errors, 415 responses, streaming parse failures, or integrating with envd-style services. Covers envelope format, trailer frames, and diagnostic techniques.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

执行完成后对照原始 RFC/Plan 检查遗漏和偏差。 触发场景：(1) 用户说"gap analysis"、"对照方案检查"、"完成度评估"、"遗漏检查"； (2) TDD 执行完成后需要系统化验证覆盖度； (3) 发布前确认所有承诺的能力都已兑现。 不适用于：代码级 review（用 requesting-code-review）、测试验证（用 verification-before-completion）。

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

技术方案 RFC 的自审 + 请求审阅的完整闭环。融入 14 维度自审清单 + 结构化审阅请求模板。 触发场景：(1) 用户说"自审"、"RFC"、"设计方案"、"design review"、"方案审阅"； (2) 完成技术方案设计后需要系统化验证； (3) 需要向用户/团队提交方案请求审阅。 不适用于：业务需求分析（用 prd-deep-review）、代码级 review（用 requesting-code-review）、 架构决策记录（用 decision-capture）。

Use when executing implementation plans with independent tasks in the current session