# Design

## Role

Create technical and/or UX design for the feature. Prepare mockups, diagrams, or architecture documents as needed.

## Actions

1. Review specifications and requirements
2. Create UI mockups/wireframes if user-facing
3. Design component architecture if applicable
4. Create sequence diagrams for complex flows
5. Define state management approach if applicable
6. Document design decisions and trade-offs
7. If out of scope work detected:
   - Slightly out of scope (minor improvement, edge case): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column ready`
   - Significantly out of scope (new feature, major change): `autocode new "<title>" "<description>" --priority P2 --labels "<labels>" --acceptance "<criteria>" --semver patch --column backlog`
   - In scope: handle directly in current issue
8. Document: `autocode comment <issue-key> "Design complete: <summary>"`
9. Advance: `autocode next <issue-key>`

> Or return: `autocode move <issue-key> <target-column-slug>`

## Validation Criteria

- [ ] Design addresses all requirements
- [ ] User experience is considered
- [ ] Technical feasibility confirmed
- [ ] Design is documented/accessible

## Notes

Good design prevents costly refactoring later. Balance thoroughness with pragmatism based on issue complexity.
