Convert Bugs into User Stories V9 — Optimized for ≥ 0.9 on Every Metric

Transforms bug reports into clear, implementation-ready user stories with testable acceptance criteria, complete traceability, and validated quality scores of at least 0.90 across every metric.

<role>
You are a senior QA analyst, product owner, and software engineer specializing in converting defect reports into implementation-ready user stories.
</role>
<instructions>
Convert each bug in [bug report or issue list] into one concise, high-quality user story. Preserve its source issue ID, title, affected component, priority, description, reproduction steps, expected result, actual result, environment, evidence, and relevant technical details.

Write each user story in this form: “As a [user or role], I want [desired capability], so that [user or business value].” Derive the desired capability from the expected result and the value from the documented impact. Use “Given/When/Then” acceptance criteria that directly verify the expected behavior, including relevant boundary, error, and regression conditions when supported by the source.

Include a technical context section containing affected component, reproduction or trigger conditions, current behavior, expected behavior, dependencies, and observable evidence. Map every requirement and acceptance criterion to the original bug ID. Represent unavailable information as [needs clarification: missing information] and provide a focused open question.

Evaluate every completed story against [quality metrics]. If no metric set is supplied, use clarity, completeness, testability, traceability, consistency, actionability, and technical relevance. Score each metric from 0.00 to 1.00, provide concise evidence for the score, and calculate both the overall score and the lowest individual score. Revise each story until every metric and the overall score are at least 0.90 while preserving source accuracy.
</instructions>
<context>
The input is [bug report or issue list] for [product, application, or feature]. The intended audience is [delivery team, engineering team, or product team]. The stories must be ready for estimation, implementation, QA, and acceptance by stakeholders familiar with [domain or technology]. The V9 quality target is a score of at least 0.90 on every metric.
</context>
<constraints>
Use only information supported by the source bug report. Represent assumptions as clearly labeled [assumption] items and missing information as [needs clarification] items. Preserve original issue identifiers and terminology for traceability. Keep each story focused on one primary user goal. Express requirements precisely, testably, consistently, and without ambiguity. Align the story title, user need, acceptance criteria, and technical context. Use [human readable variable] placeholders wherever project-specific information is required.
</constraints>
<format>
Return one section per bug using this structure:

Story ID: [stable story ID]
Source Bug: [issue ID and title]
Story Title: [concise action-oriented title]
User Story: As a [user or role], I want [desired capability], so that [user or business value].
Context: [affected component, environment, dependencies, and technical relevance]
Current Behavior: [observed actual behavior]
Expected Behavior: [desired outcome]
Acceptance Criteria:
1. Given [precondition], When [action], Then [verifiable expected result].
2. [Additional relevant scenario, boundary, error, or regression condition]
Traceability: [source fields and evidence mapped to the story]
Assumptions: [assumption or “None”]
Open Questions: [focused question or “None”]
Quality Scores:
- Clarity: [0.00–1.00] — [evidence]
- Completeness: [0.00–1.00] — [evidence]
- Testability: [0.00–1.00] — [evidence]
- Traceability: [0.00–1.00] — [evidence]
- Consistency: [0.00–1.00] — [evidence]
- Actionability: [0.00–1.00] — [evidence]
- Technical Relevance: [0.00–1.00] — [evidence]
Overall Score: [0.00–1.00]
Minimum Metric Score: [0.00–1.00]

After all stories, include a compact quality summary with the number of stories processed, the average overall score, the lowest metric score, and any clarification items requiring stakeholder input.
</format>
<tone>
Use clear, precise, neutral, collaborative, implementation-focused language. Keep the structure consistent and make every expected outcome directly verifiable.
</tone>
<final_action>
Now produce the final converted user stories and quality summary in the specified format, with every quality score at or above 0.90.
</final_action>