Skip to content
Is2Be

Technical stories

Technical or non-functional requirements from architecture, testing or DevOps, tracked as stories — never approved by Business.

Command: /sf:technical-stories · Methodology: Is2Be Software · Phase: Phase 2 · Design

When to use it

Section titled “When to use it”

After ADR-001, after the test plan and after the CD pipeline — one invocation per each, on the same document.

It’s working if

Section titled “It’s working if”
  • Each story has a clear Origin and an approver who is not Business.
  • No pending rule from the test plan is left without becoming a story.
  • No technical story duplicates an existing business User Story.

Where it fits

Section titled “Where it fits”

Requirements

Section titled “Requirements”

  • Your AI connected to the service with your licence key (how to connect).

  • The project set up once with /sf:setup.

  • The outputs of the previous steps (see Where it fits).