# Weekly Status

> Auto-generates a weekly accomplishment report by pulling completed work from Jira, GitHub, Confluence, Slack, and Obsidian meeting notes. Complements the weekly-action-scanner (which extracts future action items) by synthesizing what was actually accomplished. Triggers on: "weekly status", "status report", "what did I do this week", "week in review", "weekly recap", "generate status", "/weekly-status".

- Skill: `mshadmanrahman/weekly-status-2` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add mshadmanrahman/weekly-status-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mshadmanrahman/weekly-status-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: mshadmanrahman (https://skillmd.com/u/mshadmanrahman)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/mshadmanrahman/weekly-status-2

---


# Weekly Status Skill

Generates a comprehensive weekly status report by synthesizing accomplishments across all connected work systems. This is the **output counterpart** to the `weekly-action-scanner` tool (which extracts future action items from meeting notes).

```
weekly-action-scanner: "What was I told to do?" (future commitments)
weekly-status:         "What did I actually do?" (past accomplishments)
```

## When to Activate

- User says "weekly status", "status report", "what did I do this week"
- User says "week in review", "weekly recap"
- End of week (Friday) when user wants to summarize
- Before a standup, Big Room Planning, or manager 1:1

## Input

Optional parameters:
- **Week**: Defaults to current week (Mon-Fri). User can specify "last week" or a date range.
- **Output**: Defaults to conversation. User can request Confluence page, Slack post, or markdown file.
- **Audience**: Defaults to "manager/team". User can specify "self" (more detailed) or "leadership" (high-level).

## Execution

### Step 0: Determine Date Range

```bash
# Current week (Monday to today)
WEEK_START=$(date -v-monday -u +"%Y-%m-%d" 2>/dev/null || date -d "last monday" -u +"%Y-%m-%d")
WEEK_END=$(date -u +"%Y-%m-%d")
```

If user says "last week", shift back 7 days.

### Step 1: Parallel Data Gathering (Fan-Out)

Launch parallel searches across all connected sources:

| Source | Query | What to Extract |
|:-------|:------|:----------------|
| **Jira MCP** | `searchJiraIssuesUsingJql`: `assignee = currentUser() AND status changed DURING ("{start}", "{end}") ORDER BY updated DESC` | Issues completed, transitioned, commented on |
| **GitHub MCP** | `search_pull_requests`: authored this week | PRs created, merged, reviewed |
| **Confluence MCP** | `searchConfluenceUsingCql`: `contributor = currentUser() AND lastModified >= "{start}"` | Pages created or updated |
| **Slack MCP** | `slack_search_public_and_private`: messages from me this week | Key threads started, decisions communicated |
| **Obsidian vault** | Search notes from this week's date range | Meetings attended, decisions made, action items given |
| **Weekly action scanner** | Read `_work/actions/{week}-week-actions.md` if exists | Cross-reference: which assigned actions were completed? |

### Step 2: Classify and Organize

Group findings into categories:

1. **Shipped/Completed**: Jira issues moved to Done, PRs merged, specs published
2. **In Progress**: Issues actively worked on, open PRs, drafts
3. **Key Decisions**: From meeting notes and Slack threads
4. **Meetings**: Count + notable ones (from Obsidian/Granola)
5. **Blocked/At Risk**: Issues stuck, waiting on others

### Step 3: Action Item Reconciliation

If the weekly-action-scanner output exists for this week:
- Cross-reference assigned actions vs completed Jira/GitHub items
- Flag any assigned actions with no matching completion
- This becomes the "Carried Forward" section

## Output Format

Output directly in the conversation (default), or to a specified destination:

```markdown
# Week of {Mon date} to {Fri date}: Status Report

**Generated:** {timestamp}
**Sources:** Jira, GitHub, Confluence, Slack, Obsidian ({N} notes)

---

## Accomplished

### Shipped
- {Jira issue}: {title} ([link])
- {PR merged}: {title} ([link])
- {Confluence page published}: {title} ([link])

### Progressed
- {Jira issue}: {title} - moved from {status} to {status}
- {PR opened}: {title} - {state}

## Key Decisions
- **{Decision}**: {context} (source: {meeting/Slack/Confluence})
- **{Decision}**: {context}

## Meetings ({count} this week)
- Notable: {meeting 1}, {meeting 2}, {meeting 3}

## Blocked / At Risk
- {Issue}: blocked by {reason} since {date}
- {Issue}: waiting on {person} for {thing}

## Carried Forward
- [ ] {Action from weekly-scanner not yet completed}
- [ ] {Action from weekly-scanner not yet completed}

## Next Week Preview
- {Key meetings from Google Calendar}
- {Upcoming deadlines from Jira}

---
*Generated by /weekly-status*
```

## Output Destinations

When the user specifies where to publish:

### Slack
```
Post to specified channel using Slack MCP → slack_send_message
Format: Condensed version (Accomplished + Blocked only)
```

### Confluence
```
Create or update page using Confluence MCP → createConfluencePage
Space: User-specified or default to personal space
Parent: "Status Reports" page if exists
```

### File
```
Save to _work/status/{week-start}-status.md
```

## Rules

- **Data-driven**: Only report what's found in systems. No guessing or padding.
- **Attribution**: Always link to source (Jira ticket, PR, Confluence page).
- **Deduplication**: Same item in Jira + GitHub (e.g., PR linked to ticket) counts once.
- **Audience-appropriate**: "manager" level is 1-page scannable. "self" level includes all detail. "leadership" level is 3-5 bullet executive summary.
- **Honest**: If it was a light week, say so. Don't inflate.
- Configure your default Jira project. Expand search if you work across projects.

## Fallback

If some MCP tools are unavailable:
1. Note which sources were unreachable
2. Produce report with available data
3. Suggest running again when tools are available

## Relationship to Other Tools

```
Sunday:  weekly-action-scanner → "Here's what you committed to"
Mon-Fri: You work (Jira, GitHub, Slack, meetings)
Friday:  /weekly-status → "Here's what you accomplished"
                        → Cross-references action-scanner for accountability
```