| name | zero-assumptions |
| description | Rigorous requirements interrogation methodology that refuses to proceed with vague specifications. Demands precise constraints before implementation. Applies conditional depth based on scope. Use when told "zero assumptions", "don't assume", or "you assumed wrong"; before implementing any non-trivial request that lacks constraints, load, or failure behavior; or when about to guess a requirement instead of asking. For full feature/system design, prefer your set's architecture/design skill if it embeds this interrogation. |
Zero Assumptions Methodology
Core directive
Assumptions cause systemic failures. Absolute clarity must precede implementation. Do not provide solutions if the task is vaguely defined, lacks constraints, or misses operational context. Stop and demand precise specifications.
Conditional depth
Assess scope and apply proportional rigor:
System-level (architecture, data storage, distributed systems)
Demand explicit answers to:
- Load parameters — concurrent users, request rates, data volume
- Performance targets — normal response time, worst-case latency
- Data model — structural relationships, access patterns, storage type
- Distribution strategy — replication vs. partitioning
- Failure modes — component failure behavior, acceptable recovery time
Feature-level (new capabilities, integrations)
Clarify:
- Scope boundaries — included vs. explicitly excluded
- User personas — who uses this and in what context
- Edge cases — boundaries, invalid input, failure states
- Success criteria — how will we know this works
Localized (UI components, bug fixes, simple scripts)
Skip interrogation. Proceed directly to implementation.
Resilience requirements
Mandate these layers in system-level designs:
- Sensibility checks — validate inputs for logical reasonableness at boundaries, not just type safety
- Forcing functions — design types so invalid states are unrepresentable
- Defense in depth — multiple independent layers of error mitigation, no silent failures
Interrogation style
- Ask targeted, analytical questions. Not open-ended brainstorming.
- Persistently clarify until the picture is completely unambiguous.
- Provide 2-3 concrete options when asking for decisions.
- Never proceed with implementation until constraints are locked down.
