metrics.update-stories
Type: commands | Track: Enterprise
Add, update, or transition user stories in docs/static/data/stories.csv. Delegates to product-owner.
Quick Start
Invoke via ADLC command interface: /metrics:update-stories add --id US-008 --title "New feature" --status backlog
Or ask: "Transition US-001 to completed"
Actions
| Action | Example | Description |
|---|---|---|
add | add --id US-008 --title "..." --status backlog | Add a new INVEST story |
update | update --id US-001 --status in-progress | Update a field on an existing story |
transition | transition US-001 completed | Move story through workflow states |
list | list --status backlog | Display stories filtered by status |
Story States
backlog → in-progress → review → completed
↘ blocked
INVEST Validation
All stories added via this command are validated against INVEST criteria:
- Independent: No circular dependency
- Negotiable: Story, not specification
- Valuable: Business value score > 0
- Estimable: Story points assigned
- Small: Fits within one sprint
- Testable: Acceptance criteria defined
When to Use
| Attribute | Detail |
|---|---|
| Persona | Product Owner (PO) |
| Trigger | Story management — adding new stories from sprint planning, transitioning stories mid-sprint as work completes, or updating story metadata (assignee, points, status) |
| Business Value | Structured story management in CSV SSOT — ensures all stories meet INVEST criteria before entering the sprint, and keeps the sprint board accurate for DORA metrics and ceremony outputs |
| Frequency | Sprint |
Example: As a Product Owner, I need to add the new COS1-06 story and transition COS1-01 to completed because the sprint review requires an up-to-date stories.csv that reflects actual sprint progress. I run /metrics:update-stories which validates the new story against INVEST criteria, appends it to stories.csv, and transitions COS1-01 to completed with the completion timestamp.
Delegates to product-owner agent for INVEST validation.