LSS Functional Story Spec FAQs

Question 1

What is a 'story-sized epic' in lss-story?

Accepted Answer

It is a single deliverable unit of work that contains the same level of detail—such as data contracts and test conditions—as a full epic, but is scoped to a single focused capability.

Question 2

When should I escalate a story to a full epic?

Accepted Answer

If your story exceeds 15 acceptance criteria, 3 distinct user flows, or multiple user profiles, it likely needs a full epic pipeline (ls-epic) rather than this story-scale treatment.

Question 3

Why are test conditions (TC) nested inside acceptance criteria (AC)?

Accepted Answer

Nesting eliminates cross-referencing overhead, ensuring that developers and testers can see exactly how to verify a requirement immediately after reading it.

Question 4

How does this differ from standard user stories?

Accepted Answer

Standard stories are often too vague. lss-story enforces rigor by requiring explicit scope boundaries, error paths, and nested test conditions for every requirement.

Question 5

Does this skill include technical implementation details?

Accepted Answer

No, it focuses on the functional perspective (what the system does). Technical details like specific logic or internal architecture are added in the subsequent technical enrichment phase.

LSS Functional Story Spec

Key Features

Use Cases

LSS Functional Story Spec

Key Features

Use Cases