Refine Pbi

2. Move to Refinement Status

backlog task edit <taskId> -s "Refinement"

3. Ensure Definition of Done

Verify DoD items exist (defaults from config.yml):

backlog task <taskId> --plain

If missing, add DoD items:

backlog task edit <taskId> --dod "Unit Tests written" --dod "Code reviewed"

4. Create Mockup (User Stories Only)

For user stories, create a UI mockup:

• See: create-mockup skill
• Captures screenshot of target page
• Saves to backlog/assets/<task-prefix>-<taskId>.jpg
• Provides visual reference for implementation

5. Create ATDD Feature File

Create Gherkin feature file for acceptance criteria:

• See: create-atdd skill
• Converts acceptance criteria to BDD scenarios
• Saves to backlog/assets/<task-prefix>-<taskId>.feature
• Enables test-driven development

6. Update PBI References

4. Add a row to the relevant EPIC table in the Product Requirements Document, referencing the PBI file. (backlog\docs\doc-004 - Product-Requirements-Document.md)

Validation Checklist

• Task viewed and understood
• Status changed to "Refinement"
• Definition of Done items present
• Mockup created (User Stories only)
• .feature file created with ATDD scenarios
• All artifacts linked to task via --ref

Notes

• Use backlog task edit CLI only (never edit task markdown files directly)
• User stories require mockups, all types require feature files
• Mockups provide visual context for developers
• Feature files enable automated acceptance testing
• Keep it simple, the markdown should fit on a DIN A4 page when printed
• You can find additional information at 'backlog\config.yml' for available preample property values and default DoD items.

PBI structure (Use the preambled markdown template for new PBIs)