Documentation
How REEZN works
What each piece of REEZN does, and the thinking behind it. Start with the overview, or jump to a section.
Start here
What is REEZN?
Agree first, build once. The idea behind structured, AI-assisted feature planning.
Read the overview
Concepts
The blueprint (REASONS canvas)The implementation-ready plan for how a feature gets built, per service.The analysis documentThe full picture of a feature, confirmed before any blueprint is drawn.Norms & patternsYour team’s ways of working, woven into every plan automatically.SafeguardsHard limits every plan must respect.The knowledge baseAn AI-managed map of your concepts, fed back into every plan. (Business plan.)PersonasThe user archetypes your product serves.TemplatesReusable starting points for common feature types.Roles, teams & project accessRoles say what you can do; teams say where.
Workflow
The feature lifecycleFrom a one-line idea to an approved blueprint, in eight states.Poke holes in a draftHave AI interrogate your definition before anyone else reads it.Reviewing & approvingTwo gates, two questions, the right people answering each.The AI red team passA second AI that attacks the first one’s work, before a human reads it. (Business plan.)Implementation & verificationLet REEZN build the approved plan, open a PR, and verify it. (Business plan.)
Hand-off & history
Set up your org
Creating your organizationWhere your projects, people, and standards live.Roles & permissionsThe four roles and exactly what each one can do.Inviting people & granting accessInvite by email, assign a role, grant project access with teams.Configuring the AI provider keyChoose a provider, add a key, pick a model per task.Setting up & managing projectsProjects map to business domains and contain services.GitHub integrationConnect a repo per service for live code context.