Project status

Project Status Dashboard

Cross-tool dashboard pulling Linear, Git, GitHub, and Vercel data into one view. Great for standups.

Project Configuration

Read project configuration from .claude/project.json:

• projectName
• linear.teamId, linear.teamName, linear.projectId
• github.owner, github.repo, github.defaultBranch
• vercel.teamId, vercel.projectId, vercel.projectName, vercel.teamSlug

If .claude/project.json doesn't exist, suggest running /setup-project first.

Instructions for Claude

Step 0: Load Configuration

PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || pwd)

Read $PROJECT_ROOT/.claude/project.json.

Step 1: Gather Linear Data

Use mcp__linear__list_issues for each status:

1. In Progress:
   - state: "In Progress"
   - project: [from config.linear.projectId]

2. In Review:
   - state: "In Review"
   - project: [from config.linear.projectId]

3. Todo (top priorities):
   - state: "Todo"
   - project: [from config.linear.projectId]
   - limit: 5
   - Sort by priority

4. Backlog count:
   - state: "Backlog"
   - project: [from config.linear.projectId]
   - Count only

Step 2: Get Git Status

git branch --show-current
git status --short
git log --oneline -5

Step 3: Check GitHub PRs

gh pr list --limit 10 --json number,title,state,author,url,createdAt

Step 4: Get Vercel Deployments

Use mcp__vercel__list_deployments:
- teamId: [from config.vercel.teamId]
- projectId: [from config.vercel.projectId]
- limit: 5

Get production deployment, recent previews, build status.

Step 5: Display Comprehensive Status

# [config.projectName] — Project Status

## In Progress (X)

### ABC-XX: [Issue Title]
**Assignee**: [name]
**Branch**: feature/ABC-XX-issue-title
**Progress**: X of Y sub-issues complete (Z%)
**Sub-issues**:
- [x] ABC-XX: [completed sub-issue]
- [ ] ABC-XX: [pending sub-issue] (In Progress)
- [ ] ABC-XX: [pending sub-issue] (Todo)

---

## In Review (X)

### ABC-XX: [Issue Title]
**Assignee**: [name]
**PR**: #N ([GitHub PR URL])
**Vercel Preview**: [preview URL]

---

## Next Up (Top 5 from Todo)

1. **ABC-XX**: [title] (Priority: High)
2. **ABC-XX**: [title] (Priority: Medium)

**Total in Todo**: X issues
**Total in Backlog**: Y ideas

---

## Recent Activity

### GitHub PRs
- #N: [title] (STATE, X days ago)

### Recent Commits (Current Branch)
- [hash] [message]

### Vercel Deployments
**Production** ([config.github.defaultBranch]):
- Deployed: [time ago]
- Status: READY/BUILDING/ERROR

**Previews**:
- [branch]: [status] ([time ago])

---

## Suggested Next Actions

1. [Most logical next action]
2. [Secondary action]
3. [Tertiary action]

Display Modes

Mode 1: Full Status (Default)

Show everything above.

Mode 2: Quick Status

If user asks for "quick status" or "summary":

# Quick Status

**Your Work**:
- X in progress
- Y in review

**Current Branch**: [branch-name]
**Next**: [suggested next action]

Run /project-status for full details.

Mode 3: Specific Issue Status

If user asks about a specific issue (e.g., "/project-status ABC-11"):

# ABC-XX: [Issue Title]

**Status**: [state]
**Assignee**: [name]
**Branch**: [branch-name]
**Priority**: [priority]
**Started**: [time ago]

## Progress: X of Y (Z%)
- [x] ABC-XX: [sub-issue] (Done [time ago])
- [ ] ABC-XX: [sub-issue] (In Progress)
- [ ] ABC-XX: [sub-issue] (Todo)

## Recent Activity:
- Last commit: [time ago]
- Vercel preview: [status]
- Next sub-issue: ABC-XX

Mode 4: Review Queue

If user asks for "review queue":

# Review Queue

## Waiting for Review:
1. **ABC-XX**: [title]
   - PR #N
   - Vercel: [preview URL]
   - Ready for: [duration]

Filters

• /project-status --mine — issues assigned to you
• /project-status --review — review queue
• /project-status ABC-11 — specific issue
• /project-status --quick — abbreviated view

Error Handling

If Linear API fails: show Git/GitHub status only.

If Vercel API fails: show Linear/Git data only.

If on default branch:

Current branch: [config.github.defaultBranch] (no active feature)

Run /new-feature to start working on something!

Best Practices

1. Run regularly — Check status at start of day
2. Use for standups — Cross-tool view in one place
3. Identify blockers — See what's stuck in review
4. Plan next work — Look at "Next Up" section

Performance Notes

• Uses parallel API calls where possible
• Lazy-loads detailed info on demand

Integration with Other Skills

• Start new work: /new-feature
• Create PR: /create-pr
• Specific feature: /new-feature (status mode)