awa-vibe

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.

Vibe: Idea to Implementation

Bootstrap

User Input

${input}

You MUST consider the user input before proceeding (if not empty).

Inputs

Action

Take an idea from concept to working implementation, flowing through the awa workflow in the standard direction.

Process

1. UNDERSTAND: Clarify idea, scope, constraints. Determine starting point.
2. Flow through stages, creating/updating specs as needed
3. Checkpoint at each transition: confirm direction with user
4. Implement code with traceability, write tests
5. Verify all acceptance criteria satisfied

Checkpoints

Pause at each stage transition unless user requests autonomous mode:

• "Architecture defined. Proceed to feature context?"
• "Feature context captured. Proceed to requirements?"
• "Requirements captured. Proceed to design?"
• "Design complete. Proceed to implementation?"
• "Implementation complete. Update documentation?"

Outputs

• Specs as needed (ARCHITECTURE, FEAT, REQ, DESIGN, TASK)
• Implemented code with traceability markers
• Tests covering acceptance criteria
• Updated documentation if user-facing behavior changed

Rules

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.