ai-development-team-agent-pack/.ai/templates/user-story.md

User Story Template

Story

As a [user], I want [capability], so that [benefit].

Acceptance Criteria

• Criteria 1
• Criteria 2

Contract

• Preconditions:
• Inputs:
• Outputs:
• Postconditions:
• Invariants:
• Failure modes:
• Side effects:

Status

Proposed | Ready | In Progress | Done (Sprint N) | Deferred

Vocabulary:

• Proposed — idea not yet approved by the Product Owner for planning.
• Ready — meets the Definition of Ready; approved for a sprint.
• In Progress — actively being worked in the current sprint.
• Done (Sprint N) — accepted by the Product Owner; record the sprint number for traceability.
• Deferred — intentionally postponed; record the reason in Notes.

Notes

Test Ideas

Example

As a user, I want to export a territory, so that I can download the generated files.

Contract example:

• Preconditions: The territory exists and the user is authorized.
• Inputs: Territory ID.
• Outputs: A downloadable ZIP file.
• Postconditions: The ZIP contains the generated XLSX and PDFs.
• Invariants: The exported files are named consistently.
• Failure modes: Missing territory, file write failure, or export timeout.
• Side effects: Temporary export files may be created and cleaned up after download.

---

Self-Evolution Protocol

This file is allowed to improve over time, but only through a controlled change process.

When to propose an update

An agent may propose an update when it learns:

• A recurring mistake should be prevented.
• A better workflow has been proven useful.
• A project-specific convention has become stable.
• A prompt pattern produced better results.
• A tool, framework, library, or deployment rule changed.
• The Product Owner approved a new standard.

How to update this file

Agents must not silently rewrite this file. They must create an improvement proposal using:

./.ai/evolution/improvement-proposal-template.md

Every proposal must include:

• File to update
• Current problem
• Proposed change
• Reason
• Risk
• Rollback plan
• Product Owner approval status

Learning Log

Add durable lessons here only after they are proven useful.

Date	Lesson Learned	Change Made	Approved By
YYYY-MM-DD	Initial baseline created.	Created file.	Product Owner