Instruction file imported from tre-dnv/ado-backlog-author (
.github/instructions/backlog-refinement.instructions.md). Copyright stays with the author.
Azure DevOps Backlog refinement and Authoring Standards
Apply these rules whenever creating or editing Azure DevOps items in this project.
Scope
- Work item types: Improvement, Dev Story
- Process context: Scrum team planning, implementation, and review
- Primary target field: Azure DevOps Description
- Output style: clear markdown that can be pasted directly into Azure DevOps Description without rework
Required Structure
Dev Stories
The output should be produced in markdown format with the following sections.
# <Story Title>
_<summary>_
## Acceptance Criteria
> For acceptance-criteria drafting, review, or rewrite, apply the `backlog-acceptance-criteria` skill workflow first.
### Out of Scope
- <out of scope item 1>
## Dependencies
- <dependency 1>
- <dependency 2>
## Implementation
- <implementation note 1>
- <implementation note 2>
## Testing
- <test note 1>
- <test note 2>Improvements
The output should be produced in markdown format with the following sections.
# <Improvement Title>
_<summary>_
## Acceptance Criteria
> For acceptance-criteria drafting, review, or rewrite, apply the `backlog-acceptance-criteria` skill workflow first.
### Out of scope
- <out of scope item 1>
- <out of scope item 2>
## Risks and Assumptions
1. <risk or assumption 1>
2. <risk or assumption 2>
## Success Metrics
1. <metric 1>
2. <metric 2>
## Rollout and Adoption
- <rollout note 1>
- <adoption note 1>
## Dependencies
- <dependency 1>
- <dependency 2>Local folder structure
When authoring new or refining existing work items, create the work item content in markdown files in the /.work-items/ folder.
If authoring/refining an Improvement, place the Improvement definition file in:
/.work-items/improvements/<improvement-short-name>/<improvement-short-name>.md.
When dev stories are authored/refined for a named improvement, place them under the same folder with the convention:
/.work-items/improvements/<improvement-short-name>/stories/<order-number>_<dev-story-short-name>.md
If authoring/refining a Dev Story not associated to a named improvement, place the file in:
/.work-items/stories/<dev-story-short-name>.md.
Skills
Acceptance Criteria Quality
When authoring or refining work items, apply the backlog-acceptance-criteria skill workflow to draft, review, or rewrite acceptance criteria that are atomic, testable, unambiguous, and aligned with the item type (Improvement or Dev Story).
Item-Specific Requirements
Improvements
-
Include measurable success metrics; how will the team know the improvement is completed and successful (time, quality, cost, reliability, user impact, user adoption).
-
Add rollout and adoption notes when change management is required.
Dev Stories
-
Summary: Include a user-story style statement with the following markdown formatting at the top of the description, after the title:
**As a <role>**, **I want** <capability>, **so that** <benefit>. -
Include implementation notes constrained to delivery-relevant details only.
-
Include testability notes linked to acceptance criteria.
Planning and Estimation
- Do not add planning or estimation fields such as Story Points, sprint assignment, or owner placeholders.
Definition of Ready Checks
Do not mark the item as ready unless all are true:
- Scope is explicit and bounded.
- Dependencies are identified.
- Acceptance criteria are testable.
- Risks and assumptions are documented.
- Open questions are resolved or explicitly tracked.
Azure DevOps
When work items need to be retrieved from Azure DevOps for review, refinement, or reuse, expect an MCP server to be available.
Use the following properties when interacting with Azure DevOps work items:
- Organization:
dnvdsrenewables - Project:
Bladed