## Workflow

### 1. Gather Time Context
- Default time window: **last 7 days** (one sprint = 1 week)
- If user specifies different window, use that
- Apply recency bias: weight most recent items highest

### 2. Scan Data Sources

#### Linear MCP

**Team**: “Your Team Name” (single team, do not use cycles)

**Step 1: Get Team & Verify States**
- Get team details: `mcp_Linear_get_team(query: “Your Team Name”)` to get team ID
- Optional: Get available states: `mcp_Linear_list_issue_statuses(team: “Your Team Name”)` to verify exact state names

**Step 2: List Issues for Team**
- List all issues for “Your Team Name” team: `mcp_Linear_list_issues(team: “Your Team Name”, includeArchived: false)`
- **Important**: After getting issues, filter out:
  - Issues with state “Cancelled” or “Canceled” (check `state.name`)
  - Issues with label “Duplicate” (check `labels` array for “Duplicate” label)
  - Issues with title containing “duplicate” (case-insensitive)
  - Archived issues (already filtered by `includeArchived: false`, but double-check)

**Step 3: Filter by State and Time Window**

- **In Progress**: 
  - List issues: `mcp_Linear_list_issues(team: “Your Team Name”, state: “In Progress”)`
  - Also get: `mcp_Linear_list_issues(team: “Your Team Name”, state: “To Test”)`
  - For each issue found:
    - Get full details: `mcp_Linear_get_issue(id: issue_id)` to get description, assignee, priority, labels
    - Check comments: `mcp_Linear_list_comments(issueId: issue_id)` for unanswered questions
    - Filter out: cancelled, duplicate, archived issues

- **Recently Done**: 
  - List completed issues: `mcp_Linear_list_issues(team: “Your Team Name”, state: “Done”, updatedAt: “-P7D”)`
  - For each issue:
    - Get full details: `mcp_Linear_get_issue(id: issue_id)` to get completion date, assignee, description
    - Filter out: cancelled, duplicate, archived issues

- **Needs Design**: 
  - List design issues: `mcp_Linear_list_issues(team: “Your Team Name”, state: “Needs Design”)`
  - For each issue:
    - Get full details: `mcp_Linear_get_issue(id: issue_id)` for problem, scope, dependencies, priority
    - Filter out: cancelled, duplicate, archived issues

**Step 4: Extract Information**
- Focus on: outcomes, customer-facing wins, blockers
- Extract: issue ID, title, description, assignee, state, priority, labels
- Check for unanswered comments on in-progress issues

**Important Notes**:
- **Do NOT use cycles**: Linear has cycles, but we don’t use them for this report
- **Always filter**: Cancelled, duplicate, and archived issues should never appear in the report
- **State names**: Verify exact state names match your Linear setup (e.g., “Done” vs “Completed”, “In Progress” vs “In Development”)

#### Granola MCP (Meetings)
- Search meetings from last 7 days in your folder: `mcp_Granola_search_meetings(query: “YourCompany”, date_range: last 7 days)`
- For each meeting found:
  - Get meeting details: `mcp_Granola_get_meeting_details(meeting_id)`
  - Get transcript: `mcp_Granola_get_meeting_transcript(meeting_id)` (if available)
- Extract from meetings:
  - **Decisions made**: Strategic pivots, trade-offs, priorities
  - **Blockers discussed**: Issues mentioned but not in Linear
  - **Metrics shared**: Numbers, percentages, counts mentioned
  - **Action items**: Tasks assigned (cross-reference with Linear)
  - **Strategic questions**: Open decisions, “should we...” discussions

### 3. Extract Key Facts

Prioritize explicit, recent, and quantified information:

- **Progress metrics**: Counts of completed issues, issues in progress
- **Design bottleneck**: Number of issues needing design, which are high-priority
- **Decisions from meetings**: Strategic choices that affect Linear priorities
- **Gaps**: Things discussed in meetings but not tracked in Linear
- **Blockers**: Technical or process issues blocking progress

**Critical**: Do NOT invent facts. If a number isn’t found, omit or use neutral phrasing.

### 4. Cross-Reference & Synthesize

- Link Linear issues mentioned in meetings
- Surface meeting decisions that affect Linear priorities
- Identify gaps: discussed in meeting, not in Linear (add to “Pending” section)
- Extract quantified metrics from both sources
- Weight recent items higher (recency bias)

### 5. Apply Filters

**Include**:
- Customer-facing wins and outcomes
- Strategic decisions and pivots
- Quantified progress (counts, percentages when available)
- Blockers that need escalation
- Design bottlenecks affecting core flows

**Exclude**:
- Implementation details (unless blocking)
- Framework choices
- Internal jargon without explanation
- Cancelled or deleted issues

### 6. Format Report

Use this exact format:

```markdown
## 📈 Summary
- **Progress**: [1-2 sentence summary with quantified metrics if available]
- **Design bottleneck**: [Number of issues, which are high-priority, impact]
- **Pending (comments, decisions, blockers)**: [Unanswered comments, meeting decisions not in Linear, blockers]
- **Top of mind**: [1-2 strategic questions or pivots from meetings]
- **Recommended next steps**: [Prioritized action items]

## 📊 In Progress ([N] issues)
[For each issue, include:]
- **ID** — Issue Name *(Assignee)*
  - Description
  - Highlights (if any - from Linear or meetings)
  - Remaining work (if any)
  - [If mentioned in meetings, add: “Discussed in [meeting date]: [key points]”]

## ✅ Recently Done ([N] issues in last 7d)
- **ID** — Issue Name *(Completed [date], by Assignee)*
  - Description
  - [If mentioned in meetings, add: “Noted in [meeting date]: [outcome/metric]”]

## 🎨 Needs Design ([N] issues)
- **ID** — Issue Name
  - **Problem**: [Clear problem statement]
  - **Scope**: [What needs to be designed]
  - **Dependencies**: [Related issues or workflows]
  - **Priority**: [High/Medium/Low if available]

## 💬 Meeting Insights (from last 7d)
[If meetings found, include:]
- **[Meeting Title]** ([Date])
  - **Decisions**: [Key decisions made]
  - **Action items**: [Tasks assigned, cross-reference with Linear]
  - **Strategic questions**: [Open decisions, “should we...” discussions]
  - **Metrics shared**: [Numbers, percentages mentioned]
  - **Gaps**: [Discussed but not in Linear - add to Pending if critical]

Style Principles

Do:

Don’t:

Constraints

Example

## 📈 Summary

- **Progress**: Strong momentum on infrastructure/DevOps; Another key progress;
- **Design bottleneck**: 2 issues need design, including 2 high-priority features (PROJ-12 multi-platform, PROJ-13 key feature 2).
- **Pending (comments, decisions, blockers)**: 3 unanswered comments on PROJ-5 (Platform A integration). Meeting on Nov 5: Decision to prioritize enterprise features pending Linear issue creation.
- **Top of mind**: Should we build CRM integration (high effort, unblocks deals) vs partner with integration platform (faster, less control)? Discussed in Nov 5 sprint review.
- **Recommended next steps**:
1. Prioritize design for PROJ-12 (multi platform) and PROJ-13 (key feature 2) as they unlock core features
2. Complete Platform A integration polish (PROJ-5) - address unanswered comments
3. Create Linear issue for enterprise feature prioritization decision from Nov 5 meeting

## 📊 In Progress (2 issues)

1. **PROJ-38** — Identify tech observability tooling *(Developer A)*
   - Monitoring and alerting for production issues

2. **PROJ-37** — Add code checks to CI *(Developer A)*
   - High priority
   - Technical improvements
   - ⚠️ 3 unanswered comments need attention
   

---

## ✅ Recently Completed (8 issues in last 7d)

1. **PROJ-36** — Finish prod CI *(completed Oct 29 by Colleague A)*
2. **PROJ-35** — Copy prod data DB to staging DB *(completed Oct 29 by Colleague A)*
3. **PROJ-20** — Create staging instance *(completed Oct 29 by Colleague A)*
4. **PROJ-9** — Deploy frontend on hosting platform *(completed Oct 29 by Colleague A)*

Progress Summary: Multiple infrastructure and DevOps tasks completed recently, particularly around staging environment and CI/CD.

---

## 🎨 Issues Needing Design (2 issues)

### 1. **PROJ-34** — Super wow feature
   - **Problem**: Problem description
   - **Scope**: Scope description
   - **Dependencies**: another issue ID and description

### 2. **PROJ-27** — Another ticket
   - **Problem**: Source material sometimes insufficient;
   - **Scope**: this or that
   - **Dependencies**: none

---

## 💬 Meeting Insights (from last 7d)

### Sprint Review - Nov 5, 2025
- **Decisions**: 
  - Selected monitoring tool for observability (affects PROJ-38)
  - Prioritize enterprise features over self-serve - needs Linear issue
- **Action items**: 
  - Developer A: Start monitoring tool implementation (PROJ-38)
  - [Missing]: Create Linear issue for enterprise prioritization decision
- **Strategic questions**: 
  - Build vs partner for CRM integration? (discussed, not in Linear)
- **Metrics shared**: 
  - 40% trial activation (up from 18%) - self-serve bet paying off
  - 3 deals closed this week ($47K MRR)
- **Gaps**: 
  - Enterprise feature prioritization decision not tracked in Linear
  - CRM integration build-vs-partner discussion needs follow-up issue