TSO — {STORY-ID}: {STORY-TITLE}

Story: {STORY-ID}

Date: {YYYY-MM-DD}

Description: {STORY-DESCRIPTION-AS-USER-STORY}

1. Scope

{What is being changed and why. What is NOT being changed.}

Fields / Data to Migrate (if applicable):

#Field#Field#Field
1{field_1}2{field_2}3{field_3}

2. Context — Where This Change Fits

{Where this change fits in the broader system/flow. Relationship to prior and subsequent steps. References to related stories.}

3. Functional Expectations (from Acceptance Criteria)

  1. {Functional expectation derived from AC-1}
  2. {Functional expectation derived from AC-2}

4. Approach A — {Approach A Name}

Concept: {High-level description of what this approach does and why.}

Required Changes (in flow order):

Change A1: {filename_or_component}

{Description of what needs to change and why.}

{Code snippet showing the change, if applicable}

Change A2: {filename_or_component}

{Description of what needs to change and why.}

Pros / Cons

5. Approach B — {Approach B Name}

Concept: {High-level description of alternative approach.}

Required Changes (in flow order):

Change B1: {filename_or_component}

{Description of what needs to change and why.}

Pros / Cons

6. Performance Consideration

{Analysis of performance impact. Query complexity, data volume, indexing. State if performance is not a concern and why.}

7. Recommendation

{Recommendation with conditions for choosing each approach.}

8. End-to-End Flow Diagram

{ASCII art or structured text showing the end-to-end flow with the current story's step highlighted}

9. Assumptions

  1. {Assumption 1 — what is assumed and why}
  2. {Assumption 2}

10. Risks

  1. {Risk title} — {Risk description and potential impact.}

11. Dependencies

DependencyStoryDescription
{dependency_name}{STORY-ID}{what and why}

12. Impacted Components

ComponentRepositoryImpact
{filename_or_procedure}{repository_name}{what changes}