一键导入
awa-vibe
Implement an idea from start to finish using the full awa workflow. Use this when asked to take an idea through the complete development cycle.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Implement an idea from start to finish using the full awa workflow. Use this when asked to take an idea through the complete development cycle.
用 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-vibe |
| description | Implement an idea from start to finish using the full awa workflow. Use this when asked to take an idea through the complete development cycle. |
${input}
You MUST consider the user input before proceeding (if not empty).
Take an idea from concept to working implementation, flowing through the awa workflow in the standard direction.
Pause at each stage transition unless user requests autonomous mode:
You SHALL flow through stages in order, skipping only what exists or isn't needed. You SHALL pause at checkpoints unless user requests autonomous mode. You SHALL maintain traceability throughout. You SHOULD keep each stage minimal; avoid overengineering. You SHOULD ask clarifying questions early, not mid-implementation. You MAY collapse stages for trivial changes. You SHALL update user-facing documentation when implementation changes user-facing behavior, CLI, API, or configuration. You MAY use todos and tools as needed.