菜单
Create or update usage examples for a feature. Use this when asked to provide detailed code examples, CLI demonstrations, or configuration samples.
用 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-examples |
| description | Create or update usage examples for a feature. Use this when asked to provide detailed code examples, CLI demonstrations, or configuration samples. |
${input}
You MUST consider the user input before proceeding (if not empty).
Create or update concrete usage examples for a feature as specified in the instruction above, following awa conventions.
If deriving from existing code (reverse workflow), extract representative usage patterns, CLI invocations, and configuration samples.
You SHALL provide concrete, detailed, reproducible examples (code, CLI, config). You SHALL include context for each example explaining when to use it and what it demonstrates. You SHALL use the same {CODE} as the corresponding FEAT/REQ for the feature. You SHALL mark the document as INFORMATIVE (not normative). You SHALL split into multiple files (-001, -002, ...) if a single file would exceed the line-limit. You SHALL NOT use normative language (SHALL/SHOULD/MAY) — that belongs in REQ documents. You SHALL NOT define acceptance criteria or traceability IDs — that belongs in REQ documents. You SHALL NOT describe design decisions or implementation details — that belongs in DESIGN documents. You SHALL support reverse workflow: extracting examples from existing code when requested. You SHALL clarify open points with user. You MAY include prerequisites, expected output, and notes for each example. You MAY create examples proactively when detailed demonstrations would aid understanding. You MAY use todos and tools as needed.