Skill(compass-rose:gh-api-scripts)

{
  "success": true,
  "data": {
    "issues": [
      {
        "number": 42,
        "title": "Fix login timeout",
        "body": "Description...",
        "url": "https://github.com/...",
        "state": "OPEN",
        "labels": ["bug", "priority-high"],
        "status": "Ready",
        "priority": "P0",
        "size": "S"
      }
    ],
    "count": 15
  }
}

{
  "success": false,
  "error": {
    "code": "CONFIG_MISSING",
    "message": "Configuration file not found",
    "details": "Create .compass-rose/config.json with..."
  }
}

No active items found in the project.

All items appear to be marked as "Done" or the project is empty.

Would you like to create a new item? (/compass-rose:add-item skill)

{
  "number": 42,
  "title": "Fix login timeout",
  "body": "Description with details...",
  "url": "https://github.com/org/repo/issues/42",
  "state": "OPEN",
  "labels": ["bug", "priority-high"],
  "status": "Ready",
  "priority": "P1",
  "size": "M"
}

Analyze these project items and recommend the top 2-3 to work on next:

[Paste the formatted JSON array from step 4]

Focus on:
- Definition quality (clarity, completeness, acceptance criteria)
- Priority distribution (if Priority field exists)
- Size balance (prefer mix of quick wins and substantial work)
- Overall backlog health

Return your analysis with detailed rationale for each recommendation.

# Backlog Analysis Results

**Items Analyzed**: [N total]
**Well-Defined Items**: [X items with score 8-10]
**Items Needing Clarification**: [Y items with score <5]

## Top Recommendations

### Recommendation 1: [Title] (#[number])

**Priority**: [P0/P1/P2/P3] | **Size**: [S/M/L/XL] | **Definition Quality**: [Well-Defined/Defined/Vague/Poorly Defined] ([score]/10)

**Rationale**:
- [Why this is recommended - link priority, size, definition quality]
- [What makes it ready to work on]
- [Any specific strengths]

**Definition Assessment**:
- **Clarity** ([0-3]/3): [Brief assessment]
- **Completeness** ([0-3]/3): [Brief assessment]
- **Acceptance Criteria** ([0-4]/4): [Brief assessment]

**Link**: [URL to issue]

---

### Recommendation 2: [Title] (#[number])
[Same structure as Recommendation 1]

---

### Recommendation 3: [Title] (#[number]) [OPTIONAL]
[Same structure as Recommendation 1]

---

## Backlog Health Summary

**Priority Distribution**: [X P0, Y P1, Z P2, W P3]
**Size Distribution**: [A S, B M, C L, D XL]
**Definition Quality**:
- Well-Defined (8-10): [X items]
- Defined (5-7): [Y items]
- Vague (2-4): [Z items]
- Poorly Defined (0-1): [W items]

**Observations**:
- [Notable patterns]
- [Quality trends]
- [Recommendations for backlog improvement]

## Items Needing Clarification

1. **[Title]** (#[number]) - Score: [X]/10
   - Missing: [What needs to be added]
   - Suggest: [How to improve definition]

Would you like to:
1. Start work on one of these recommendations? (/compass-rose:start-work)
2. Review the next item specifically? (/compass-rose:next-item)
3. Add a new item to the backlog? (/compass-rose:add-item)
4. Clarify one of the poorly-defined items?

No active items found in the project.

All items are marked as "Done" or the project is empty.

Would you like to create a new item? (/compass-rose:add-item skill)

Warning: Priority field not found in project.

Recommendations will be based on:
- Definition quality (clarity, completeness, acceptance criteria)
- Size (prefer smaller items for quick wins)
- Creation date (older items first)

To enable priority-based recommendations, add a "Priority" field to your project.

Error: GitHub CLI is not authenticated.

Run the following command to authenticate:
  gh auth login

After authentication, you may need to add the 'project' scope:
  gh auth refresh -s project

Error: Project not found.

Verify that:
1. Project owner is correct: <owner>
2. Project number is correct: <number>
3. You have access to the project
4. You are authenticated: gh auth status

Warning: Most backlog items lack sufficient detail.

The recommendations below are based on priority/size only, but each item needs
clarification before implementation can begin. Consider adding:
- Clear problem/feature descriptions
- Reproduction steps (for bugs) or use cases (for features)
- Explicit acceptance criteria

Recommended next step: Clarify the highest-priority items before starting work.

Loading project configuration...
Config loaded: my-org/project-123

Discovering custom fields...
Found fields: Status, Priority, Size, Iteration

Querying active items...
Found 15 non-Done items

Analyzing backlog quality with backlog-analyzer agent...

---

# Backlog Analysis Results

**Items Analyzed**: 15 total
**Well-Defined Items**: 4 items with score 8-10
**Items Needing Clarification**: 6 items with score <5

## Top Recommendations

### Recommendation 1: Fix login timeout on Chrome (#42)

**Priority**: P0 | **Size**: S | **Definition Quality**: Well-Defined (9/10)

**Rationale**:
- Highest priority (P0) issue affecting 15% of users
- Small scope (S) makes it achievable in single session
- Excellent definition with clear repro steps, acceptance criteria, and impact data
- Can be completed quickly to unblock users

**Definition Assessment**:
- **Clarity** (3/3): Clear problem description with specific browser versions and reproduction steps
- **Completeness** (3/3): Includes repro steps, environment details, server log insights, and user impact percentage
- **Acceptance Criteria** (3/4): Explicit success conditions but could include performance target (e.g., p95 < 5s)

**Link**: https://github.com/my-org/my-repo/issues/42

---

### Recommendation 2: Add user preferences panel (#58)

**Priority**: P1 | **Size**: M | **Definition Quality**: Defined (7/10)

**Rationale**:
- High priority (P1) feature request from multiple users
- Medium scope (M) - more involved but still manageable
- Good definition with use cases and most details present
- Complements login fix (both improve user experience)

**Definition Assessment**:
- **Clarity** (3/3): Clear use cases and user needs described
- **Completeness** (2/3): Core requirements present but missing edge cases
- **Acceptance Criteria** (2/4): Basic success conditions but not fully testable

**Link**: https://github.com/my-org/my-repo/issues/58

---

## Backlog Health Summary

**Priority Distribution**: 3 P0, 7 P1, 4 P2, 1 P3
**Size Distribution**: 5 S, 6 M, 3 L, 1 XL
**Definition Quality**:
- Well-Defined (8-10): 4 items
- Defined (5-7): 5 items
- Vague (2-4): 4 items
- Poorly Defined (0-1): 2 items

**Observations**:
- P0 items are generally well-defined (good crisis management)
- Many P1 features lack explicit acceptance criteria (common pattern)
- XL item (#72: "Implement notification system") should be broken down or escalated to Lore Development spec

## Items Needing Clarification

1. **Improve error messages** (#51) - Score: 3/10
   - Missing: Which errors? What makes them bad currently? What should they say instead?
   - Suggest: List specific error scenarios, current messages, and desired improvements

2. **Refactor auth module** (#73) - Score: 2/10
   - Missing: What problems exist? What's the goal of refactoring? Success criteria?
   - Suggest: Describe technical debt, refactoring objectives, and measurable improvements

---

Would you like to:
1. Start work on one of these recommendations? (/compass-rose:start-work)
2. Review the next item specifically? (/compass-rose:next-item)
3. Add a new item to the backlog? (/compass-rose:add-item)
4. Clarify one of the poorly-defined items?