weekly-plan

Included with Lifetime

$97 forever

Review the past week's activity and suggest a prioritised plan for the coming week

Code Review

What this skill does

# Weekly Plan

Review what happened last week and suggest priorities for the coming week.

## Accounts

Read `bot_account`, `owner_account` from the org's CLAUDE.md `## Automation config` table.

## Helper script

A pre-built script at `~/.claude/scripts/weekly-plan.sh` gathers all planning context in one pass.
Run it first to avoid spending tokens on individual `gh` and `git` calls.

```bash
~/.claude/scripts/weekly-plan.sh > /tmp/weekly-plan.json
```

If the script is missing or not executable, flag this to the user and stop.

The script outputs a JSON object with:
- `today`, `week_start`: date range
- `daily_logs`: list of available daily log dates from `~/code/claude-log/`
- `open_prs`: all open PRs by the owner and bot accounts across orgs
- `assigned_issues`: all issues assigned to the owner across orgs
- `recent_commits`: commit counts per repo for the past week
- `prs_merged_this_week`, `issues_closed_this_week`: totals

## Phase 1: Enrich context

1. Read any daily log files listed in `daily_logs` for narrative context
2. Check grant repos for deadline-related files or comments
3. Check issues with milestone dates

## Phase 2: Categorise

Group work into:
- **Blocked**: PRs waiting on review, CI failures needing upstream fixes
- **In progress**: open PRs, active worktrees, partially done issues
- **Ready to do**: assigned issues, bot task requests, release preparation
- **Maintenance**: stale worktrees to prune, dependency updates, CI fixes

## Phase 3: Prioritise

Score each item:
- Blocking other work (+3)
- Quick win, under 30 minutes (+2)
- External deadline (+3)
- Requested by someone else (+1)
- Maintenance / nice to have (+0)

## Phase 4: Present plan

Write to `~/code/claude-log/weekly-plan-YYYY-MM-DD.md`:

```markdown
# Weekly plan: YYYY-MM-DD

## Last week summary
- [2-3 sentences on what was accomplished]
- PRs merged: N
- Issues closed: N
- New PRs opened: N

## Blockers
- [ ] item (reason blocked)

## This week's priorities

### Must do
1. item (reason)

### Should do
1. item (reason)

### Could do
1. item (reason)

## Maintenance backlog
- item
```

Also present the plan in the terminal.

## Auto-Exit When Standalone

**IMPORTANT**: If this command is being run as a standalone request, automatically exit after completing all phases successfully.

Files: 1

Size: 2.4 KB

Complexity: 5/100

Category: Code Review

Source: https://github.com/seabbs/skills/tree/main/plugins/productivity/skills/weekly-plan

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts