| 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. |
Create or Update Plan(s)
Bootstrap
User Input
${input}
You MUST consider the user input before proceeding (if not empty).
Inputs
Action
Update or create the ad-hoc plan document(s) as specified in the instruction above, following awa conventions.
Outputs
Rules
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.
