pm-autopilot
v1.0.0Put recurring rituals on autopilot: charter what to automate, schedule it on any runner (Claude Code routines, cron, n8n, GitHub Actions), and make every run delta-aware so it reports what changed, not what it already said. Ships with the recurring skills worth scheduling.
By Mohit AggarwalLicense: MIT1.4k GitHub starsUpdated yesterday
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 7 skill or MCP entries
- Source updated
- Oct 4, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install pm-autopilot for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install pm-autopilot@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mohitagw15856/pm-claude-skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/pm-autopilot/.
Plugin files
├── .claude-plugin/plugin.json├── skills/autopilot-charter/SKILL.md├── skills/competitive-intelligence-monitor/SKILL.md├── skills/delta-briefing/SKILL.md├── skills/morning-intelligence/SKILL.md├── skills/outcome-tracker/SKILL.md├── skills/pm-weekly-review/SKILL.md└── skills/schedule-recipe/SKILL.md
Included Skills7
Decide which of your recurring rituals to put on autopilot — and which to keep manual. Use when asked what to automate, how to set up recurring AI runs, which reports or briefings could run on a schedule, or to design an automation charter for a team. Produces a ritual inventory with automate/assist/keep-manual calls, guardrails per ritual, and a rollout order.
Monitor competitor signals and surface strategic implications for your roadmap. Use when asked to monitor competitors, track the competitive landscape, produce a competitive briefing, or understand what has changed in the market this week or month. Produces a structured intelligence brief with high/medium/low priority signals, roadmap implications, and a strategic landscape summary. For a single competitor announcement use competitor-signal-tracker; for a one-off deep dive use competitor-teardown.
Make a recurring brief report what changed since the last edition instead of restating everything. Use when a weekly or monthly report keeps repeating itself, when setting up a scheduled monitor or digest, or when asked to make a recurring update delta-aware. Produces a changes-first brief plus the state record the next run will diff against.
Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or create an automated intelligence briefing. Produces a confirmed summary of your preferences, a ready-to-paste master prompt, and setup instructions for both Cowork Scheduled Tasks and Claude Code Routines.
Record the testable predictions inside a decision, then score them against reality later — so frameworks earn trust from outcomes, not vibes. Use when committing to a prioritisation, forecast, or plan (to log what it predicts), when asked to review what actually happened, or to compute how well-calibrated past RICE scores, forecasts, or bets have been. Produces a prediction record at decision time, and a calibration report with per-framework hit rates at review time.
Structure a PM's weekly review and planning session. Use when doing a weekly PM review, writing a weekly update, preparing for Monday planning, or reviewing sprint health. Produces a shareable weekly update covering metrics movement, shipping progress, blockers, insights, and next week's top 3 priorities.
Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the prompt to run, failure alerting, and a first-run test plan.
Plugin manifests1
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "pm-autopilot",
"version": "1.0.0",
"description": "Put recurring rituals on autopilot: charter what to automate, schedule it on any runner (Claude Code routines, cron, n8n, GitHub Actions), and make every run delta-aware so it reports what changed, not what it already said. Ships with the recurring skills worth scheduling.",
"author": {
"name": "Mohit Aggarwal",
"email": "[email protected]"
},
"homepage": "https://github.com/mohitagw15856/pm-claude-skills",
"license": "MIT",
"keywords": [
"automation",
"scheduling",
"recurring",
"routines",
"autopilot"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[pm-autopilot on Agent Plugins Marketplace](https://pluginsmp.com/plugins/pm-autopilot)