Please provide the Initiative to assess:

- Confluence Intent page URL, OR
- Jira Epic key (e.g., PROJ-123)

I'll fetch all related artifacts and generate a progress report.

Detected phase: [Implementation]
Artifacts found: Intent, 3 Units, 8 Tasks, Design docs, Jira Epic with 3 Sub-epics, 5 linked MRs

You are assessing AI-DLC documentation quality for a progress report.

## Initiative Context

**Intent Document:**
<intent content>

**Units (if present):**
<unit pages content>

**Tasks (if present):**
<task pages content>

**Design Documents (if present):**
<design doc content>

## Scoring Dimensions

Rate each dimension 0-100:

1. **Documentation Completeness** — All required sections present for the current phase
2. **Content Quality** — Clear, specific, actionable; no vague language (see Part 2.2 of review-criteria)
3. **NFR Measurability** — Performance/security/availability targets are specific and measurable
4. **Ambiguity Level** — Lower ambiguity = higher score; boundaries and terms clear

## Return Format

Return as JSON:

{
  "phase_detected": "<planning|elaboration|design|verification|implementation>",
  "scores": {
    "documentation_completeness": <0-100>,
    "content_quality": <0-100>,
    "nfr_measurability": <0-100>,
    "ambiguity_level": <0-100>
  },
  "gaps": [
    {
      "severity": "<high|medium|low>",
      "area": "<section or document>",
      "issue": "<description>",
      "suggestion": "<remediation>"
    }
  ],
  "open_questions": [
    "<question from the documentation>"
  ],
  "strengths": [
    "<well-documented aspect>"
  ],
  "overall_confidence": <0-100>
}

You are assessing Jira issue health for an Initiative progress report.

## Jira Artifacts

**Epic/Sub-epics:**
<jira epic and sub-epic details>

**Stories (Bolts):**
<story details with status, assignee, points>

**Sub-tasks (Tasks):**
<sub-task details with status, assignee>

## Scoring Dimensions

Rate each dimension 0-100:

1. **Progress (Task Completion)** — Done issues / Total issues as percentage
2. **Progress (Story Points)** — Completed points / Total points as percentage
3. **Team Readiness** — Issues assigned, no blockers, dependencies mapped
4. **Blocker Count** — Fewer blockers = higher score (100 = no blockers)

## Return Format

Return as JSON:

{
  "progress": {
    "task_completion": {
      "done": <count>,
      "total": <count>,
      "percentage": <0-100>
    },
    "story_points": {
      "completed": <points>,
      "total": <points>,
      "percentage": <0-100>
    }
  },
  "team_readiness": {
    "score": <0-100>,
    "unassigned_count": <count>,
    "blocker_count": <count>,
    "blocked_issues": ["<issue keys>"]
  },
  "status_breakdown": {
    "to_do": <count>,
    "in_progress": <count>,
    "done": <count>,
    "blocked": <count>
  },
  "unit_progress": [
    {
      "unit": "<sub-epic name>",
      "tasks_done": <count>,
      "tasks_total": <count>,
      "points_done": <points>,
      "points_total": <points>,
      "status": "<not_started|in_progress|done>"
    }
  ],
  "risks": [
    {
      "severity": "<high|medium|low>",
      "issue": "<description>",
      "suggestion": "<remediation>"
    }
  ]
}

You are assessing code health for an Initiative progress report.

## Linked Merge Requests

<list of MRs with status, file changes>

## MR Diffs (summarised)

<key changes from each MR>

## Project Context

<CLAUDE.md, linter configs, test directory structure>

## Scoring Dimensions

Rate each dimension 0-100:

1. **Test Coverage Estimate** — Based on test files present, test-to-code ratio
2. **Code Complexity** — Large files, deep nesting, high method counts = lower score
3. **MR Health** — Merged vs open, CI status, review status

## Return Format

Return as JSON:

{
  "mr_summary": {
    "total": <count>,
    "merged": <count>,
    "open": <count>,
    "ci_passing": <count>,
    "ci_failing": <count>
  },
  "scores": {
    "test_coverage_estimate": <0-100>,
    "code_complexity": <0-100>,
    "mr_health": <0-100>
  },
  "risk_factors": [
    {
      "severity": "<high|medium|low>",
      "area": "<file or component>",
      "issue": "<description>",
      "suggestion": "<remediation>"
    }
  ],
  "strengths": [
    "<positive code health aspect>"
  ]
}

## Initiative Progress Report

### [Initiative Name]

**Phase:** [Implementation] | **Assessed:** [YYYY-MM-DD HH:MM]

---

### Summary

| Metric | Score | Interpretation |
|--------|-------|----------------|
| **Confidence** | XX% | [High/Medium/Low] — [one-line summary] |
| **Risk** | XX% | [High/Medium/Low] — [one-line summary] |
| **Progress** | XX% | [ahead/on track/behind] — [one-line summary] |

---

### Confidence Breakdown

| Dimension | Score | Notes |
|-----------|-------|-------|
| Documentation Completeness | XX% | [brief note] |
| Content Quality | XX% | [brief note] |
| Team Readiness | XX% | [brief note or N/A] |
| Execution Evidence | XX% | [brief note or N/A] |
| Ambiguity Level | XX% | [brief note] |

---

### Risk Breakdown

| Dimension | Score | Notes |
|-----------|-------|-------|
| Test Coverage | XX% | [brief note or N/A] |
| Code Complexity | XX% | [brief note or N/A] |
| Active Blockers | XX% | [count or N/A] |
| Dependency Issues | XX% | [brief note] |

---

### Progress by Unit

| Unit | Tasks | Points | Status |
|------|-------|--------|--------|
| Unit 1: [Name] | X/Y (XX%) | X/Y (XX%) | [status emoji] [In Progress] |
| Unit 2: [Name] | X/Y (XX%) | X/Y (XX%) | [status emoji] [Not Started] |
| Unit 3: [Name] | X/Y (XX%) | X/Y (XX%) | [status emoji] [Done] |
| **Total** | **X/Y (XX%)** | **X/Y (XX%)** | — |

Status indicators: ✅ Done | 🔄 In Progress | ⏳ Not Started | ❌ Blocked

---

### Recommendations

**High Priority:**
1. [Action] — [why it matters]

**Medium Priority:**
2. [Action] — [why it matters]

**Low Priority:**
3. [Action] — [why it matters]

---

### Open Questions

1. [Question from Intent or docs]
2. [Question identified during assessment]

---

### Strengths

- [Positive aspect 1]
- [Positive aspect 2]

| Test Coverage | N/A | No code artifacts linked yet |