Blueprint

Answer six questions.Get a blueprint.

Adams asks goal, user, scope, limits, success and risks, then writes the spec and plan and keeps them current as you build.

Pro
// the problem

What goes wrong

A project starts as a feelingYou know roughly what you want, but not the scope, the limits or how you will know it is done. Building from a feeling means rebuilding later.
Plans go staleA plan written once and forgotten stops matching the code. The next session builds against a picture that is no longer true.
// what adams does

What Adams does

Asks six fields in orderPro: goal, user, scope, limits, success and risks. At most four questions a round, each with a recommended answer.
Looks up facts itselfPro: it reads your README and code first. It asks only for decisions, taste, access and money.
Keeps a live page currentPro: the spec and plan are written into your project and updated while the work runs.
// worked example

An example

Settling a new project

Illustrative session.

~/project~/your-project · example
/adams:blueprint
Goal: freelancers send an invoice in under a minute
Scope: invoices and clients, no payments yet
Limits: one currency, no team accounts
Risk: tax rules differ by country
✓ Spec and plan written
// faq

Questions

Where is the blueprint stored?

In the .adams folder inside your project.

Can I answer in my own words?

Yes. Every question accepts your own answer, and a plain yes accepts the recommendation.

Is it free?

No. The blueprint is Pro.

// related

Keep reading