Story Writer

When to Use

Final position of a story-creation chain. Activated only after autoplan (position 2) wrote 2-eng-plan.md. The reframe + strategic verdict + plan have all converged; now we formalize.

Skip if the chain ended early at position 1 (LATER/NEVER verdict) — no story to write.

Rules

1. Read all three prior artifacts. The story is the consolidation, not a fourth opinion.
2. Connextra header: As a <persona>, I want <capability>, so that <outcome>. Filled with the reframed objective, not the literal request.
3. Background section quotes the strategic fit verdict from position 1 in two sentences max.
4. 3-7 Gherkin acceptance criteria in the form Given <state> When <action> Then <outcome>. No And chains longer than 3 lines per criterion.
5. Definition of Done section copied from 2-eng-plan.md. Do not re-derive — that risks drift.
6. Sections in order: ## Story, ## Background, ## Acceptance criteria, ## Definition of Done, ## Out of scope, ## Refs.
7. ## Refs MUST link to all three prior artifacts by relative path: [reframe](./0-office-hours.md), etc.
8. After saving the artifact, call:
   • aria_artifact_complete with final_artifact: 3-story.md
   • aria_save with type: story, scope: project, content = the Connextra header + acceptance criteria. (Saving the full body pollutes memory; the header is enough for retrieval.)
9. Word count target: 200–800.

Verification

• Connextra header present, all three slots filled
• Background ≤ 2 sentences quoting position 1 verdict
• 3-7 Gherkin criteria, each Given/When/Then
• DoD copied verbatim from 2-eng-plan.md
• Refs section links all three prior artifacts
• aria_artifact_complete called
• aria_save type=story scope=project called
• Word count in [200, 800]