Entalpa

Entalpa docs

What Entalpa's ideas mean and how to do the main tasks, from the first description of a product to a spec your team builds from and keeps up to date.

How Entalpa works

A project is one spec. Its stakeholders have needs; the user stories say what each of them wants; the requirements say what the system shall do to serve those stories; the design says how. Every link is kept: a requirement traces to the stories it serves, a story to the stakeholders who want it. Whoever builds the product, people or a coding agent, works from that spec, and each requirement shows how far its work has got.

Six steps, from an idea to delivery

  1. 01Create a project
  2. 02Check the stories
  3. 03Generate and check the requirements
  4. 04Hand the spec to whoever builds it
  5. 05Follow the build
  6. 06Add stories as the product grows

All docs

Start here

Elicitation

  • Why stories come firstsoon
  • Stakeholderssoon
  • How a story is structuredsoon
  • Open questionssoon
  • Suggesting extra featuressoon

Account and billing

  • Credits and planssoon
  • Privacy and cookiessoon

These docs describe Entalpa 0.16.1.