Source
HN beta feedback from jfim during v1.0-beta launch.
Problem
The 4-question minimum interview produces shallow first-pass
requirements for complex projects. jfim: "The prompting by the
model was very shallow, it didn't ask enough questions so the
requirements were off."
Proposed change
After the 4 minimum questions, ask 2-3 project-type-specific
follow-ups based on what was described:
- API project → ask about authentication, rate limiting, error formats
- Frontend → ask about user roles, device targets, offline support
- Data pipeline → ask about volume, latency, failure handling
- Greenfield → ask about scale expectations and known constraints
Impact
Better first-pass requirements.md with fewer post-generation corrections.
Labels
v1.1, beta-friction
Source
HN beta feedback from jfim during v1.0-beta launch.
Problem
The 4-question minimum interview produces shallow first-pass
requirements for complex projects. jfim: "The prompting by the
model was very shallow, it didn't ask enough questions so the
requirements were off."
Proposed change
After the 4 minimum questions, ask 2-3 project-type-specific
follow-ups based on what was described:
Impact
Better first-pass requirements.md with fewer post-generation corrections.
Labels
v1.1, beta-friction