Slash Command

Plan Week

Plan the week with priorities, risks, and success criteria

Type: Slash Command
Repository: jeremylongshore/tons-of-skills-marketplace
GitHub stars: 2.8k
License: MIT
Repo last updated: Sep 27, 2026
Source file: plugins/productivity/pm-ai-partner/commands/pm/plan-week.md

What Plan Week is

Plan Week is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Plan Week gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Plan Week

Claude Code

Download plan-week.md from the repository.
Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
Run it by typing / followed by its name.

Claude Cowork

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
In Customize → Skills, click +, then upload the ZIP.
Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/productivity/pm-ai-partner/commands/pm/plan-week.md, shared under the repository's MIT license. Read the full file on GitHub.

Help me plan my week as a Product Manager.

Context Gathering

Before generating a plan, pull context from all available sources:

From the workspace

Review CLAUDE.md, sandbox/, and product-catalog/ for current priorities and in-flight work
Check recent git history (git log --oneline -20) for what shipped recently

From MCP servers (if configured)

GitHub: Pull open PRs and issues assigned to the user — gh pr list --author @me, gh issue list --assignee @me
Linear: Check current sprint items, upcoming deadlines, and blocked issues
Slack: Scan recent DMs or channels for pending requests or decisions
Google Drive: Check for documents shared with the user in the past week that may need review
Memory: Recall last week's plan (if stored) and check what was completed vs. carried over

If MCP servers aren't configured, skip those sources and work from workspace context + user input.

Process

Assess current state — What's in progress? What shipped last week? What's blocked?
Pull external context — Open PRs, sprint items, pending requests, unread docs
Identify priorities — Based on all context, what are the top 3-5 things that need attention this week?
Schedule key activities — Map priorities to concrete actions (meetings to schedule, docs to write, decisions to make, people to talk to)
Flag risks — What could go sideways this week? What needs proactive attention?
Set success criteria — What does a good week look like?

Output Format

## Week of [Date] — Planning

### Last Week Recap
- [What shipped/completed]
- [What slipped and why]
- [Carryover items]

### Open Items (from tools)
| Source | Item | Status | Action Needed |
|--------|------|--------|---------------|
| GitHub PR | [title] | [review/merge/blocked] | [what to do] |
| Linear | [issue] | [in progress/blocked] | [what to do] |
| Slack | [thread/request] | [pending] | [respond/decide] |
| Google Doc | [doc title] | [shared/needs review] | [review by when] |

### This Week's Priorities
1. **[Priority 1]** — [Why it matters] → [Concrete action]
2. **[Priority 2]** — [Why it matters] → [Concrete action]
…

If you have MCP context available, pre-populate the plan as much as possible — the user should refine, not start from scratch. If no MCP context is available, ask me about current priorities and last week before generating.

Before you install

Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
Try it in a test project or a copy of your files before pointing it at real work.
Pin the version you tested, and review changes before updating.
Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Plan Week?

Plan Week is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Plan the week with priorities, risks, and success criteria

How do I install Plan Week in Claude Code?

Download plan-week.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Plan Week in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Plan Week safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.