القائمة
Create or update ad-hoc plan documents. Use this when asked to create plans, break down work, or organize tasks, but not when specifically asked to create tasks from requirements and design documents.
التثبيت باستخدام 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-plan |
| description | Create or update ad-hoc plan documents. Use this when asked to create plans, break down work, or organize tasks, but not when specifically asked to create tasks from requirements and design documents. |
${input}
You MUST consider the user input before proceeding (if not empty).
Update or create the ad-hoc plan document(s) as specified in the instruction above, following awa conventions.
You SHALL create and maintain ad-hoc plans for features, improvements, refactors, or other user requests. You SHALL break down work into detailed, actionable steps You SHALL identify risks, dependencies, and completion criteria You SHALL ensure the 3-number {nnn} used in the filename follows the previous plans within the project. You SHOULD NOT write significant code in the plan documents. Code can be used to define data structures and for explanation. You SHOULD consider edge cases, user experience, technical constraints, and success criteria. You SHOULD suggest specific areas where the plan might need clarification or expansion. You SHALL clarify open points with user. You MAY use todos and tools as needed.