메뉴
Use when implementing repository feature work such as new capabilities, API or schema changes, integrations, user-facing behavior changes, or mixed code-and-doc deliverables after requirements are clear enough to execute.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when handling local Git CLI daily operations such as checking status or diff, staging files, creating conventional commits, restoring local changes, reverting commits, or resolving merge/rebase/cherry-pick conflicts.
Use when explaining code, answering technical questions, comparing approaches, or providing repository-grounded analysis without entering an implementation or remediation workflow.
Use when evaluating system architecture, platform design, or high-level technical structure to identify production risks, evidence gaps, and prioritized remediation without directly redesigning or implementing the system.
Use when improving internal code structure without intentionally changing externally observable behavior, such as module splits, simplification, dependency cleanup, or maintainability and performance-oriented restructuring.
Use when feature ideas, issues, stakeholder notes, or partial specs need to be reviewed and turned into a concise, testable PRD with clear scope, user stories, acceptance criteria, and explicit open decisions.
Use when a PRD, feature spec, or acceptance criteria already exist and need to be turned into a concise test plan and traceable test cases with clear priorities, coverage, and execution focus.
| name | develop-feature |
| description | Use when implementing repository feature work such as new capabilities, API or schema changes, integrations, user-facing behavior changes, or mixed code-and-doc deliverables after requirements are clear enough to execute. |
develop-feature 是功能交付的执行 lane，不负责替代需求澄清、设计收敛或最终验证门禁。
它的职责是：在目标、范围与验收已足够明确后，以最小必要改动完成 feature 交付，并把完成结论绑定到可验证证据。
适用于：
以下情况不要直接进入本 skill：
XY 风险遇到这些情况时，优先转交：
superpowers:brainstormingsuperpowers:writing-plansskills/fix-bug/SKILL.mdskills/refactor/SKILL.md目标 / 范围 / 不做 / 关键假设 / 验收。superpowers:brainstorming，不得在本 skill 内绕过。superpowers:writing-plans，再回来执行。superpowers:test-driven-development 的约束；不得先写生产实现再补验证。Align
目标 / 范围 / 不做 / 假设 / 验收Classify
code / docs / mixedsmall / standard / high-riskstandardGate
superpowers:brainstormingsuperpowers:writing-planssuperpowers:test-driven-developmentImplement
Verify
superpowers:verification-before-completion 执行验证Report
Done / Partial / Skipped按需读取配套参考文件：
references/feature-delivery-playbook.md
references/verification-checklist.md
N/A 规则、交付证据门槛时读取不要把所有参考内容一次性压进上下文。
出现以下信号时，说明流程正在退化：
对用户的交付至少应包含：
Done / Partial / Skipped若当前路径没有更优替代方案，应明确写出：当前路径合理，暂无更优替代建议。
brainstorming / writing-plans / TDD / verification-before-completion 冲突rules/output-style.md 与 rules/deliverable-quality-gate.md