一键导入
awa-upgrade
Upgrade specs to match current schemas. Use this when asked to upgrade, migrate, or update specification documents to conform to schema changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Upgrade specs to match current schemas. Use this when asked to upgrade, migrate, or update specification documents to conform to schema changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Double-check the last work, whether it be a plan, design, or implementation, ensuring all aspects have been fully considered. Use when user wants to check work, or mentions "double check".
Align source with target. Use this when asked to align, check, or verify alignment between artifacts.
Create or update ARCHITECTURE.md. Use this when asked to create, update or modify the project architecture.
Brainstorm ideas, explore solutions, and evaluate options. Use this when asked to brainstorm, explore ideas, or analyze trade-offs.
Run traceability and schema checks, then fix any errors. Use this when asked to check, validate, or fix traceability and schema issues.
Implement code and tests based on architecture, requirements, and design (or a set of tasks). Use this when asked to implement features, write code, or create tests.
| name | awa-upgrade |
| description | Upgrade specs to match current schemas. Use this when asked to upgrade, migrate, or update specification documents to conform to schema changes. |
${input}
You MUST consider the user input before proceeding (if not empty).
Upgrade the specified specs to conform to their schemas and traceability rules.
awa check in the terminal to identify schema violations and traceability errors across all target files. Parse the output to build a list of findings to fix.awa check again to verify all errors are resolved. Repeat FIX → RECHECK until the check passes cleanly (warnings and info findings are acceptable).You SHALL avoid destructive edits; propose clarifications when unsure. You SHALL follow schema structure strictly (section order, nesting). You SHALL obey schema render expectations (omit optional empty sections, avoid prohibited patterns). You SHALL upgrade existing trace IDs if necessary. You SHALL upgrade existing filenames if necessary. You SHALL respect the file line-limits; split logically if needed. You MAY use todos and tools as needed.