Getting started
Six steps from a plain-language idea to a spec your team builds from, with the progress of every requirement in one place.
1. Create a project
Describe what you want to build: the goal, who uses it and the main features. Write it in the chat or fill in the form. If you already have a spec, start from it instead: an Entalpa export, or a repository your developers keep in OpenSpec or Spec Kit.
The description is where a project starts. Entalpa reads it once, to draft the first stakeholders and stories. From then on the stories and requirements are the spec, and you change them, not the description.
2. Check the stories
Entalpa drafts the stakeholders, everyone with a stake in the system, and the user stories each of them needs. Read them first: every requirement that follows is drafted from a story, so a missing or wrong story costs more later.
- Edit, delete or add stories, and give each a priority: Must, Should, Could or Won't.
- Ask for more stories with a focus, such as "payments" or "what an admin needs".
3. Generate and check the requirements
Entalpa drafts the system requirements from your stories. Each one says what the system shall do, how to tell it does it (the acceptance criteria), and which stories it serves. See Requirements and their lifecycle.
Then check them. Analyze reviews requirements you pick and proposes rewrites. Assess, on the Overview, gives the whole spec a Spec score and lists what to fix first.
4. Hand the spec to whoever builds it
People read the spec in the app, or through a shared link or an export. A coding agent, such as Claude Code, Codex or Cursor, connects to the project over MCP, a standard way for AI tools to read and update data. Setting one up takes a single command or config entry: Connect an agent has the steps for each tool.
5. Follow the build
As the work moves, so does each requirement's status: in progress, implemented, verified. A connected agent records it as it works; people set it in the requirements table. The bar above the table sums up where the whole project stands.
Why it matters
The spec stays the record of what was asked for and what was built. Anyone on the team can see what is done and what is still open, without asking the people building it.
6. Add stories as the product grows
New feature, new story. Entalpa drafts the requirements for it, traced to it like the rest, and you review them as in step 3. Stories and requirements stay linked, so a requirement whose story changed is flagged for a second look.