/design-feature

Design a new feature "$ARGUMENTS" for the OpenUsage TUI dashboard.

Read and follow the full skill specification in docs/skills/design-feature/SKILL.md.

Follow all phases in order:

1. **Phase 0 — Quiz**: Ask me all 8 questions from the skill doc before doing any design work. If I provided the feature name as "$ARGUMENTS", use that as the starting point but still confirm details. Research the codebase yourself if I don't know an answer.

2. **Phase 1 — Explore**: Read the subsystem map in docs/skills/design-feature/references/subsystem-map.md, then read the primary files for every affected subsystem. Read any overlapping design docs in docs/. Summarize what you learned that affects the design.

3. **Phase 2 — Design**: Write the design doc to docs/<FEATURE_NAME>_DESIGN.md following the template in docs/skills/design-feature/references/design-template.md. Keep it simple — no unnecessary abstractions.

4. **Phase 3 — Tasks**: Break the design into concrete, ordered implementation tasks with specific files and tests. Append to the design doc.

Complete the full checklist at the end of the skill doc before finishing.