Docs / Getting started

What is REEZN?

REEZN turns a feature idea into a clear, reviewed plan that product signs off on and engineering trusts, all before any code is written.

You describe what you need in plain language. AI drafts the details, risks, and a build blueprint. The right people review and approve. What gets built is what everyone agreed to, with a full record of who agreed to what.

REEZN leans on AI to first map the concepts that already exist in your codebase and business logic. Grounded in that understanding, it then proposes the right plan to extend them, so new work fits what you’ve already built instead of cutting against it.

Why work this way

Software built from a one-line prompt gives you slop. Software built from a blueprint gives you quality. Documented standards, reviewed plans, and enforced guardrails used to be a luxury reserved for teams with time and headcount to spare. AI changes that. REEZN puts those practices within reach of every team, so AI makes your software better rather than sloppier.

The method behind it is SPDD, or Structured Prompt-Driven Development. Instead of prompting an AI tool once and hoping, you move an idea through defined stages, and a human reviews each one before it advances. A misunderstanding costs less the earlier you catch it, and SPDD front-loads that catching into cheap, focused reviews.

How it works in practice

From your seat, every feature follows the same four moves. AI drafts, and you and your team approve:

Describe the idea. In plain language, capture the goal, the business value, what’s in and out of scope, any constraints, and acceptance criteria. This is the author’s input, and the richer it is, the sharper everything downstream.
See the full picture. AI drafts an analysis document covering the concepts involved, the approach, and the risks and edge cases. Whoever owns the requirements (usually product) confirms it captures what was actually meant. That is the first gate.
Shape the blueprint. Once the analysis is approved, AI generates a REASONS canvas for each service the feature touches. A technical reviewer confirms the plan is the right way to build. That is the second gate.
Build with confidence. With every canvas approved, the generation preview unlocks, where you copy or download each approved canvas as clean markdown to hand to your engineers or your AI coding tools.

Organizations on the Business plan can go a step further: REEZN can implement the approved plan, open pull requests, and verify its own work behind a third human sign-off, and it maintains a knowledge base that grounds every plan in what you’ve already built. Both are covered in their own pages.

The shape of REEZN

Everything in REEZN lives inside a four-level hierarchy. You work day to day from your organization’s home and each project’s home, where features are listed and tracked.

Organization: The top-level home for everything: your projects, members, teams, templates, norms, and safeguards. AI generation is configured once here, for the whole org.
Project: A business domain (Billing, Identity, Catalog). It contains services and is where features are created and tracked.
Service: A deployable unit, usually a codebase, optionally connected to a GitHub repo for live code context. A feature can span several services, and each gets its own build blueprint.
Feature: A unit of work that moves through the workflow: you describe it, AI drafts an analysis document and a REASONS canvas per service, and the team approves each in turn.

Two human sign-offs sit in the path: one on the analysis, one on the canvases. AI does the drafting, but nothing advances on the AI’s say-so alone.

What you get out

An analysis document that confirms everyone understood the same ask.
A REASONS canvas per service: an implementation-ready blueprint grounded in your existing code, norms, and safeguards.
Two human sign-offs, so the plan is both correct and the right way to build.
A copy-and-paste export to hand to your engineers or your AI coding tools, plus a versioned history of every decision.