autopilot-charter

Featured

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.

AI & Automation 1,356 stars 240 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Autopilot Charter Skill Inventory the reports, briefings, and reviews you produce on a rhythm, and decide — deliberately — which ones an AI should run on a schedule, which it should only draft, and which stay human. ## What This Skill Produces - A **ritual inventory**: every recurring artifact, its cadence, audience, and inputs - An **automate / assist / keep-manual** call per ritual, with the reason - **Guardrails** for each automated ritual (review gate, failure behaviour, escalation) - A **rollout order** — which ritual to automate first and why ## Required Inputs Ask for (if not already provided): - **The recurring outputs** the user or team produces (weekly updates, monthly reviews, monitors, digests) - **Who consumes each one** and what they do with it - **Where the inputs live** (git, analytics, CRM, inbox, notes) and whether an agent can reach them - **Tolerance for error** per artifact — what happens if a run is wrong or missing? ## Classification Framework Score each ritual on four questions, then classify: | Question | Points toward automating | |---|---| | **Inputs reachable?** Can an agent read the sources without a human fetching them? | Yes | | **Structure stable?** Does the output look the same every cycle? | Yes | | **Cost of a bad run?** Would a wrong or stale edition mislead a decision? | Low cost | | **Delta-shaped?** Is the value "what changed since last time" rather than fresh judgement? | Yes | - **Automate** — all four favourable. Schedule i...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
7 months ago
Last Updated
yesterday
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

autopilot

Full autonomous execution from idea to working code

6 Updated today
mazenyassergithub
AI & Automation Listed

autopilot

Run the idea-to-ship pipeline AUTONOMOUSLY, in character as a grounded founder-persona — composing ideate → deep-dive → prompt-pack → build-loop to take a real, grounded niche to a near-finish-line-AIMED first-draft product plus an honest ledger of what only a human or the market can finish. ALWAYS invoke when the user says any of "run autopilot", "build this idea→ship autonomously", "spin up a grounded founder and build it", "fly the whole pipeline end to end", or "autonomous first-draft from a concept". It composes the existing skills, never reimplementing them, and states its honest bounds — a near-finish-line first draft, NOT a finished or market-validated product (~80% craft ceiling; grounding firewall; its go/kill calls are a signal). Do NOT use to drive each phase by hand (use the skills directly), when there's no real grounding (you'd be inventing demand), or when you need market validation (the human handoff).

83 Updated 1 months ago
nelsonwerd
AI & Automation Featured

routine-from-chat

Turn a plain-language "do this automatically" request into a routine — either event-triggered ("text me when I get an email from my landlord") or scheduled ("remind me every Friday at 9am"). For third-party events (Gmail, GitHub, Slack…) it confirms with the guardian and then subscribes to the connector trigger so the event actually fires, even one that has never fired before. Ask for any missing detail, then confirm with a card. Reach for this first whenever the guardian wants something to happen automatically; do not explore the codebase or hand-build a trigger.

488 Updated today
rome-os