菜单
Use this when reviewing a completed feature for performance risks across API, database, and frontend paths. Typically run after implementation and verification, before finalization. Do not use for planning, implementation, debugging, or testing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | turtle-performance |
| description | Use this when reviewing a completed feature for performance risks across API, database, and frontend paths. Typically run after implementation and verification, before finalization. Do not use for planning, implementation, debugging, or testing. |
Evaluate for:
Performance Summary
Risks
No-action Notes
Recommendations
Use this to generate a concise, repo-aligned implementation plan for a selected backlog item, or the next unchecked backlog item when none is provided. Produces atomic, checkbox-based steps scoped to the current feature. Do NOT write code or modify backlog state.
Use this when generating a final, concise git commit message for a completed feature, based on plans, feature docs, backlog updates, and modified files. Typically used after implementation, verification, and documentation are complete. Do not use for planning, implementation, debugging, or modifying code.
Use this when diagnosing failures detected in VERIFY, TEST, ENGINEER CHECKPOINT, or runtime validation, and determining the minimal safe fix and correct routing (EXECUTE or TEST). Do not use for planning, feature implementation, or routine changes.
Use this to implement exactly the first unchecked step in the active plan file, or apply minimal fixes after VERIFY fails. Do not skip steps, expand scope, modify plan state, update backlog status, test, review, or perform multi-step changes.
Use this when creating or updating docs/features/<feature_slug>.md to document a completed feature, including summary, decisions, architecture impact, tests, and follow-ups. Typically used after implementation, verification, and backlog updates are complete. Do not use for planning, implementation, debugging, or testing.
Use this only after a feature has fully completed the Plan-Driven State System and needs to be marked done in docs/backlog.md. This skill updates one matching backlog item from unchecked to checked. Do not use for creating backlog items, planning, implementation, debugging, testing, or summarizing the backlog.
