From autonomous-work
Use when the user invokes `/autonomous-work`, says "go autonomous", or asks to run the full spec → plan → execute pipeline without check-ins. Triggers structured flow: optional brainstorming, spec drafting with self-review + subagent review, plan drafting with subagent review, execution (subagent-driven if >10 tasks else inline), mandatory progress.md + handover.md tracking, optional feature doc, and ship (commit/push + branch merge for pre-release projects).
How this skill is triggered — by the user, by Claude, or both
Slash command
/autonomous-work:autonomous-workThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
an end-to-end workflow for taking an idea through to shipped code with minimal check-ins. Use AFTER brainstorming (or kick off brainstorming first — see Phase 0).
an end-to-end workflow for taking an idea through to shipped code with minimal check-ins. Use AFTER brainstorming (or kick off brainstorming first — see Phase 0).
/autonomous-work or says "go autonomous" / "run the full flow".Don't use for: single-edit fixes, quick reads, exploratory questions, or anything that doesn't need a plan.
Ask these in a single batched question round, BEFORE Phase 0:
progress.md and handover.md so the user can review them later.docs/<feature-name>.md as part of the work (per your global CLAUDE.md "Feature documentation in docs/" rule). Confirm the filename.CLAUDE.md first. If it doesn't state whether the project is pre-release, ask the user and write the answer into the repo's CLAUDE.md so future sessions don't need to ask again. Pre-release status governs Phase 6 (merge to main) and the Laravel migration rule.progress.md and handover.md live in this repo? Default to repo root; check for existing files first, and use the existing location if there is one.superpowers:brainstorming skill.progress.md and handover.md (this is non-negotiable — the user reviews decisions through these files).docs/superpowers/specs/<feature>.md.general-purpose subagent to review the spec for gaps, ambiguity, missing edge cases, and security/UX boundary issues. Pass the spec path and ask for a punch list under 200 words.docs/superpowers/plans/<feature>.md.superpowers:subagent-driven-development: one subagent per independent task, with code review between tasks.progress.md at the agreed location.docs/<feature-name>.md per the comprehensive template in your global CLAUDE.md (Overview / How it works / Architecture / Data model / API / Business rules / Security / Frontend behaviour / Operational notes / Cross-links).handover.md. Overwrite the previous one. It must cover:
progress.md, handover.md, and any feature doc in the commit.main after pushing. Skip for projects that aren't pre-release.If the project is Laravel and pre-release, and the task requires schema changes, edit the existing migration files directly instead of generating new migrations. The reset path is php artisan migrate:fresh --seed. Skip this rule for projects that aren't pre-release — there, always create new migration files.
progress.md rather than silently improvising.progress.md, handover.md, or the feature doc because "the session was small" → don't skip. They're cheap and they're the contract.CLAUDE.md (and ask the user if absent).| Phase | Output | Subagent? |
|---|---|---|
| 0. Brainstorm (if needed) | Decisions in progress.md + handover.md | No |
| 1. Spec | docs/superpowers/specs/<feature>.md | Yes — review |
| 2. Plan | docs/superpowers/plans/<feature>.md | Yes — quick review |
| 3a. Execute (>10 tasks) | Code + tests | Yes — one per task |
| 3b. Execute (≤10 tasks) | Code + tests | No — inline |
| 4. Progress log | progress.md (rolling, appended) | No |
| 5. Feature doc (if new feature) | docs/<feature-name>.md | No |
| 6. Handover | handover.md (overwritten) | No |
| 7. Ship | commit + push (+ merge if pre-release) | No |
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub mike-ab/catch-solutions-claude-skills --plugin autonomous-work