Help

How to use Speclr

How Speclr works

An overview of the four phases a Speclr project goes through, from a first idea to sprint-ready stories, how versions work and where your project's knowledge lives.

Updated

A Speclr project moves through four phases. In each one you talk to Speclr in the chat while the phase's result, the artifact, grows beside it. Every phase builds on the ones before it.

  1. Discovery: shape the Vision Statement

    Speclr interviews you about your idea and turns your answers into a structured Product Vision Statement. It is the foundation every later phase builds on. More about Discovery.

    Result
    Product Vision Statement
  2. Exploration: build the story map backbone

    Together with Speclr you lay out the backbone of the User Story Map: the full scope of the product as epics and user stories, before you commit to a roadmap. More about Exploration.

    Result
    User Story Map backbone
  3. Planning: milestones and story order

    You slice the story map into milestones and decide what comes first. Speclr helps you propose an MVP slice. More about Planning.

    Result
    Milestones on the story map
  4. Refinement: one Story Artifact per story

    Speclr interviews you story by story. Each story gets its own Story Artifact, meant to be ready for developers or coding agents without follow-up questions. It has these sections:

    • "Business Rules"
    • "Scenarios / Gherkin"
    • "Actors"
    • "Non-Functional Requirements"
    • "Data Fields"
    • "Boundaries" (in scope and out of scope)

    Refinement explains the interview.

    Result
    One Story Artifact per story

One phase after another

A phase opens once the phases before it are finished. Until then its tab is locked. Finishing a phase commits its first version and opens the next one. In Refinement you finish each story on its own. Finish a phase walks you through it.

On the Professional and Business plans, the team can vote on readiness before a phase or a story is finished. See Team alignment.

Versions in short

A finished phase is read-only. To change it, you start its next version, for example "Start version 2…". That opens a draft; finishing the draft commits version 2. Every committed version stays in the version history.

When an earlier phase gets a new version, the later phases say so in their tab, for example "Based on an older version of Discovery". Versions and drafts covers the details.

Where your project's knowledge lives

Besides the artifacts, a project collects knowledge that every phase reads. You open it from the side bar next to the artifact:

  • Context: the domain knowledge your conversations establish, as rules, actors, data fields and glossary terms. See Context.
  • Files: what the team has added, such as notes, interviews, specs and photos. Speclr reads them from Discovery on. See Add files.
  • Memory: general facts Speclr picked up along the way, such as people, timing and ways of working.
  • Constitution: what your organisation and this project require of everything they build. Every phase observes it.
  • Risks: what could go wrong in the project, found by Speclr and tracked by your team. See Risks.

Ready to begin? Create a project, then take the tour of the workspace.