Přejít na obsah
Peak Atlas

Peak Docs / For product & engineering

The spec is written.The build follows the chat.

Requirements change in the thread while the spec stays put. In Peak Docs product and engineering write the spec together in real time, keep acceptance criteria as a checklist and turn each criterion into a task.

Put the goal into words. Add perspectives and timing right below.

Local draft · no product activation
Try the example

Try it on a local sample feature.

One spec. Clear criteria.

Problem / criteria / delivery

01The problem02The roles03The criteria
Working example / technical spec

What carries the delivery.

The problem
Which problem do we solve, for whom?
The roles
Who owns which part?
The criteria
How do we know it's done?
Editorial structure sketch · not the product interface

Your small spec

From three answers to a spec.

Fill in the example with a made-up feature and see how problem and criterion fit together. Everything stays in this preview.

Local working example · nothing is saved or sent. Please don't enter personal data.

Peak Docs / Start noteLOCAL DRAFT
01 / Your thoughts
02 / Your start noteLocal preview

Three questions. One spec.

Draft · not yet put together

The problem
Still open
The roles
Still open
The first criterion
Still open
Your input appears here right away. With “View the start note” you check the three details locally.

From idea to delivery

One spec. With criteria.

The order turns an idea into a spec the team can check the delivery against.

  1. 01Case

    Create the spec.

    The problem

    Which problem do we solve, for whom?

    You start with the specification document type. The outline shows problem, solution and open questions.

    Spec → problem and solution
  2. 02Action

    Set the criteria.

    The roles

    Who owns which part?

    Acceptance criteria sit as a checklist in the spec. Every item can become a task in Peak Work.

    Checklist → tasks
  3. 03Result

    Trace the changes.

    The criteria

    How do we know it's done?

    Versions show what changed in the spec. Branched spec versions are planned.

    Sample artifact → technical spec

The next proof is the product

Check it on your next feature.

In Peak Docs you write specs together in real time, offline too, keep criteria as a checklist and compare versions. Start for free with the spec for one feature.

Start Peak Docs for free

Peak Docs / Your next step

Done is what meets the criteria.

Try the example on a feature that's coming up. Then you know which criterion counts first.

Try the example
Local working example

Your spec. Your criteria.

How do we know it's done?

Frequently asked questions

Is Peak Docs an issue tracker?

No. Criteria and comments become tasks in Peak Work; Peak Docs is the place for the spec.

Can I import and export specs as Markdown?

Yes. Markdown and plain text can be imported; export is available as Markdown, HTML and PDF.

Are there branches for spec versions?

Not yet; branching is planned. Today versions with a diff show what changed and can be restored.

Are the examples on this page real customers?

No. All examples are made-up sample data. The exercises run only locally in your browser and save nothing.

More in Peak Docs