ProblemFirst
Pre-architecture checklist and review tool that forces engineering teams to write down the actual user problem, constraints, and failure modes before approving microservices, queues, or new abstractions.
Tech leads and staff engineers about to start or review a system design
- Template-driven PRD for systems with prompts like 'what problem does this solve?'
- Red-flag detector that flags likely over-engineering patterns (prem microservices, premature queues)
- Auto-generated ADRs tied to the original problem statement for traceability
- Team review workflow with sign-off and rollback-to-PRD links
The essay's framing - that over-engineering is a requirements failure - is currently trending on HN with 98 points, indicating broad team-level appetite for guardrails.
The 'over-engineering is a requirements failure' essay is real and was syndicated to daily.dev, AICrier, and upstract, but HN items in this genre recur every few months and rarely translate into sustained product demand; 'pre-architecture checklist' as a search query is essentially empty.Perfection is not over-engineering - var0.xyz ↗Perfection Is Not Over-Engineering | Hacker News ↗
An established ADR ecosystem already exists (ADR GitHub org, Structurizr, Decispher's ADR roundup, plus AWS and Microsoft publishing ADR playbooks), and 'force teams to fill a checklist before approving abstractions' is trivially replicable as a Notion template, GitHub Action, or PR template.Architecture decision record (ADR) - GitHub ↗Best ADR Tools for Engineering Teams (2026) - decispher.com ↗Master architecture decision records (ADRs) - AWS ↗
Target buyers are tech leads and staff engineers — typically ICs without budget authority; a search for paid pre-architecture checklist SaaS returned no results, suggesting buyers don't actively look for paid tooling in this niche and would default to free templates.Perfection is not over-engineering - var0.xyz ↗Best ADR Tools for Engineering Teams (2026) - decispher.com ↗
Over-engineering debates recur every framework cycle; the underlying need is structural.
Conceptually a form/checklist tool with optional workflow gating — buildable as a Notion/Linear plugin or thin SaaS in days; the article itself lays out the exact checklist items (constraints, failure modes, users, needs) so no novel research is required.