一键导入
planning-change-inventory
Enumerate concrete files/components and intended edits tied to AC; not broad cross-system impact analysis
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Enumerate concrete files/components and intended edits tied to AC; not broad cross-system impact analysis
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Mandatory baseline rules for any agent. Must be loaded before any work
Frontend design system practices: tokens, typography, color, layout, and component consistency.
Frontend UI/UX practices: flows, interaction states, accessibility-first UX, forms, and perceived performance.
Clean code execution rules for coding agents with verifiable quality gates.
Debugging requirements protocol from reproducible issue to verified fix and regression protection.
Requirement quality rules for coding tasks with traceable MUST/SHOULD and verifiable acceptance criteria.
| name | planning-change-inventory |
| description | Enumerate concrete files/components and intended edits tied to AC; not broad cross-system impact analysis |
<output_format>
<quality_rules> The list is finite and specific (not "change a couple of files") Every change is tied to the goal or AC </quality_rules>