Backlog: INI to user stories with acceptance criteria

If you are building a company and feel lost about strategy backlog user stories, you are not alone. This phase exists so your Strategy Pack stays honest—not pretty.

What this phase is really about

Backlog turns strategy into buildable units without losing traceability. Initiatives link to epics, capabilities, and user stories with acceptance criteria. Startups get a credible MVP slice; enterprises get a defensible program backlog aligned to VP and impact thesis.

In Sculptor, BacklogAgent keeps the conversation anchored to Backlog so you do not mix this work with other phases. That separation is how consultants run engagements: one room, one decision set, one artefact pack.

Why teams skip this (and regret it later)

Leaders confuse a roadmap slide with a backlog. When US ids are missing, engineering estimates fiction and QA cannot verify strategy intent. Skipping backlog guarantees OKRs that nobody can map to shipped work.

Questions this phase must answer

• Which initiatives directly prove VP-001 in the next release?
• What is the smallest epic set that validates the wedge?
• Where do stories need explicit non-goals?
• Which dependencies block customer-visible value?
• How will acceptance criteria be tested in staging or pilot?
• What belongs in MVP vs phase two without dishonest labeling?
• Which items are compliance or ops enablers vs features?
• Who owns refinement for each epic?

Deliverables you should leave with

Backlog artefacts form an INI → epic → capability → feature → user story tree with acceptance criteria and trace references back to strategy ids.

• INI-001 initiative map traced to strategy artefacts
• EPC-001 epics with outcomes, not task lists
• US-001 stories with Given/When/Then acceptance criteria
• CAP-001 capability map for cross-team coordination

What to prepare before you start

• MSN, VP, and impact artefacts from /strategy
• Engineering capacity estimate or squad map
• Known regulatory or integration constraints

Who should own the answers

Product management owns structure; engineering leads validate feasibility markers; design flags experience-critical stories. Sponsors protect MVP scope when sales requests “just one more” enterprise feature.

How this connects to the rest of your pack

This phase sits in the Plan and commit group on the Strategy Pack journey.

Previous: Earlier phase

Next: Next phase

See the complete phase guide for all specialists.

Examples from the real world (names changed)

A fintech app trimmed backlog to onboarding and ledger sync stories traced to VP-001, avoiding a social feed epic that had no strategic id.

A B2B SaaS vendor linked US items to OBJ ids early, which made OKR scoring honest when two squads shipped overlapping admin tools.

Use this in Sculptor tomorrow

1. Open Sculptor and create or open a workspace project.
2. In Chat, type /backlog or pick Backlog from the command palette—the same rules apply as the slash.
3. For breadth, start an Agentic Strategy Pack run; the phase executes in journey order and saves library assets.
4. Read From specialist chat to a library-ready Strategy Pack for how chat and Agentic runs fit together.

Keyword focus: strategy backlog user stories, Strategy Pack coach, startup strategy planning, AI strategy specialist.