Software Design Requirements

Goal

Turn vague requests into a small working slice with clear behavior and room to learn.

Discovery Questions

Ask or infer:

• Who is the user and what job are they trying to finish?
• What observable behavior proves the change worked?
• What examples define the normal case, edge cases, and failure cases?
• What constraints matter: performance, security, accessibility, data loss, compatibility, or operations?
• What can be deferred without blocking learning?
• What would make this solution good enough for now?

Tracer Bullet Workflow