Help

How to use Speclr

What changed and what it may affect

For anyone finishing a draft of version 2 or later. How to read the change plan, decide which later elements need a review, and commit, including what to do when the assessment fails.

Updated

When you finish a draft of version 2 or later, Speclr first shows its change plan: what the draft changed, and which elements of later phases or other stories build on those changes. Nothing is committed or marked until you commit; "Cancel" leaves the draft as it was.

What the change plan does

  • Looks downstream onlyA change reaches later phases and the stories that use it, never the phases before it.
  • You decide each elementSpeclr suggests and explains. It never changes a later element itself.
  • Later versions stayA marked element keeps its version and status. It only gets a marker to review.
  1. See what changed

    While the draft is open, choose "Changes" in the side bar; its badge counts the changes. The view "Changes in version N" lists "What changed since version N-1". In the finish step, the same list is the tab "1 · What changed".

    Each change is "Added", "Changed", "Removed" or "Replaced", with "Before" and "After". The arrow beside it shows the whole text.

  2. Check what it may affect

    Under "May be affected downstream", or the tab "2 · What it may affect", each element shows where it lives, why it is listed and how it was found:

    • "Linked": it links a domain entry the draft removed or replaced, or its story was added to or removed from the story map.
    • "AI assessment": Speclr judged it affected and says why. A "Recommendation" is text for you; nothing is applied.
    • "Not yet assessed": nobody has judged it yet.

    The assessment starts when a session in the draft ends, and when you open Changes or the finish step. Meanwhile one line says "Assessing N elements that build on these changes…". Elements it judged not affected are collapsed at the end, each with its reason; "Mark for review" takes one back into the plan if you disagree.

  3. Decide each element

    • "Mark for review": the element gets a marker when you commit.
    • "Not relevant": recorded on the version. For an element "Not yet assessed", Speclr asks "Why is it not relevant?" and saves only with a reason.

    Choose the same button again to undo. "Mark all undecided for review" decides the rest at once. Any member of the project team can decide, and everyone sees the same decisions.

    Reason
    up to 1,000 characters
  4. Commit with the plan

    The tab "3 · Commit" sums up the changes committed, the elements marked for review and those recorded as not relevant. Write your comment and commit. The button stays unavailable while "N elements still need a decision." or while the assessment runs.

    The version and its markers are created together. To work through the markers, see Resolve items marked for review.

When decisions are reset

A decision holds while the change it was made on stays the same. Change that element in the draft again and the elements it reaches are undecided once more.

If a team member changes the draft while you commit, Speclr refuses: "The change plan changed since you looked at it. Review it again before you commit."

When the assessment fails

Speclr says "The impact assessment could not assess every element. Those it missed stay “not yet assessed”." and offers "Retry assessment". A failure never counts as "not affected": decide those elements yourself, or mark them and retry later from their marker.

When nothing is affected

"No element of a later phase or another story builds on these changes." means there is nothing to decide. A draft that changed nothing says "Nothing changed since the last version." and is finished as usual. See Versions and drafts.