Loading…
Loading…
Every generated ZIP includes ADRs in MADR v4, a traceability matrix linking every requirement to code, Mermaid architecture diagrams, populated compliance docs (GDPR DPIA, HIPAA risk assessment, PCI-DSS scope, SOX §404), cost estimate, security posture, and performance notes. The things you usually produce by hand after three weeks — shipped next to the code the day you generate it.
Three weeks of implementation, then someone scrambles for ADRs, compliance mapping, traceability between requirements and code. The docs are always behind and always partly fiction.
Cursor, Copilot, Lovable, v0 — all optimise for 'writing code faster'. None of them answer 'why is the database Postgres?' or 'where is the GDPR DPIA?' or 'which file implements FR-03.2?' when the compliance officer asks.
Board review Monday. The slides need a real architecture diagram, a real decision log, a real risk register. The team has none of that. You build it by hand because it is your reputation on the line.
The docs/ tree that sits next to the generated code, versioned in your Git repo.
Why Postgres. Why JWT in httpOnly cookies. Why SQLAlchemy. One ADR per material decision, including alternatives considered and why each was rejected. Shipped as `docs/decisions/ADR-*.md` in the ZIP.
C4 context, C4 containers, entity-relationship, request-flow sequence diagrams, state machines per stateful entity. Renders natively on GitHub. Every generated app's root README embeds the context + container diagrams inline.
Every user story → functional requirement → screen → entity → generated file path. Orphan-FR detection built in. Available as both `docs/traceability.md` and `docs/traceability.csv` for audit tooling.
GDPR DPIA, HIPAA risk assessment, PCI-DSS scope statement, SOX §404 control matrix — populated from your actual data model, integrations, and compliance flags. Human-judgement fields marked TBD explicitly; no hallucinated assurance.
Monthly cost estimate per stack and per integration with growth projections to 1M MAU. Security posture covers attack surface + pre-launch checklist. Performance notes describe scaling ceilings and observability recommendations.
Indexes the whole `docs/` tree: why each decision was made, how every requirement maps to code, what the architecture looks like, what legal needs, what the intended UI is. Drop it in your team Slack; everyone is oriented in twenty minutes.
So you can calibrate before you sign up:
Free trial. No credit card. Generate a real app — not a marketing demo — and look at the docs/ tree it ships. If that pack would have saved you three weeks on any project this year, you have your answer.