By Mike-Ab
Turn raw project inputs (briefs, transcripts, screenshots, voice notes, loose prompts) into a complete, staged scoping package — scope.md, screens.md, phased task cards, and API docs.
A small collection of custom Claude Code skills, packaged as a plugin marketplace so you can install them with a couple of slash commands.
| Skill | What it does |
|---|---|
| scoping | Turns raw project inputs (briefs, meeting transcripts, screenshots, voice notes, loose prompts) into a complete, staged scoping package — scope.md, screens.md, phased task cards, and API docs. |
| prompt-engineer | Builds production-grade prompts from a short brief: a quick discovery interview, then a fully-scaffolded prompt (role, context, task, inputs, instructions, output spec, examples, optional self-verification). |
| autonomous-work | Runs a full spec → plan → execute pipeline with minimal check-ins. Requires the superpowers plugin — see Requirements below. |
In Claude Code, add this marketplace once:
/plugin marketplace add Mike-Ab/claude-skills
Then install whichever skills you want (à la carte):
/plugin install scoping@claude-skills
/plugin install prompt-engineer@claude-skills
/plugin install autonomous-work@claude-skills
That's it — the skills are now available. They activate automatically when your request matches the skill, or you can describe the task directly (e.g. "scope this project", "write me a prompt for…", "go autonomous").
To update later:
/plugin marketplace update claude-skills
autonomous-workautonomous-work is the most opinionated skill and has two dependencies:
The superpowers plugin. It orchestrates superpowers skills (brainstorming, writing-plans, subagent-driven-development, requesting-code-review, etc.). Without superpowers installed, the pipeline's review and planning phases won't have skills to call. Install superpowers first.
Session-continuity conventions. The skill writes and reads two files to make long, multi-session work resumable:
progress.md — an append-only log; one ## Session N — YYYY-MM-DD entry per session.handover.md — a snapshot, fully rewritten at session end, that lets a fresh agent resume cold.It also expects an optional docs/<feature>.md convention for feature documentation. These conventions live in the author's global CLAUDE.md. If you want the same behaviour, add equivalent rules to your own CLAUDE.md, or just let the skill create the files as it goes — it will.
scoping and prompt-engineer have no dependencies and work standalone.
If you'd rather not use the plugin system, copy any skill folder straight into your skills directory:
git clone https://github.com/Mike-Ab/claude-skills.git
cp -R claude-skills/plugins/scoping/skills/scoping ~/.claude/skills/
Restart Claude Code and the skill will be picked up.
MIT © Mike Ab
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub mike-ab/catch-solutions-claude-skills --plugin scopingBuild production-grade prompts from a short brief — discovery interview, then a fully-scaffolded prompt with role, context, task, inputs, instructions, output spec, examples, and an optional self-verification block.
Run a full spec→plan→execute pipeline with minimal check-ins. Requires the superpowers plugin and assumes progress.md / handover.md session-continuity conventions (see README).
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Build and maintain an LLM-curated personal knowledge base in your project — Andrej Karpathy's LLM Wiki pattern, designed to scale to thousands of pages without becoming a context bottleneck. Now with an optional compiled graph layer for typed, provenance-backed relationships.
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
AI-powered wiki generator for code repositories. Generates comprehensive, Mermaid-rich documentation with dark-mode VitePress sites, onboarding guides, deep research, and source citations. Inspired by OpenDeepWiki and deepwiki-open.
20 modular skills for idiomatic Go — each under 225 lines, backed by 48 reference files, 8 automation scripts (all with --json, --limit, --force), and 4 asset templates. Covers error handling, naming, testing, concurrency, interfaces, generics, documentation, logging, performance, and more. Activates automatically with progressive disclosure and conditional cross-references.
Claude + Obsidian knowledge companion. Sets up a persistent, compounding wiki vault (Karpathy's LLM Wiki pattern). v1.7 "Compound Vault" + v1.8 methodology modes close 5 of 5 priority gaps from the May 2026 compass artifact. Ships: substrate alignment with kepano/obsidian-skills, default Obsidian CLI transport, hybrid retrieval (contextual prefix + BM25 + cosine rerank per Anthropic's Sept 2024 research), per-file advisory locking for multi-writer safety, pre-commit verifier agent, AND methodology modes (LYT / PARA / Zettelkasten / Generic) for first-class organizational support no other Claude+Obsidian competitor offers. v1.7.x audit closure: every BLOCKER + HIGH + MEDIUM + LOW finding from the v1.7.0 audit is CLOSED or DEFERRED-with-rationale. Optional DragonScale Memory extension (log folds, deterministic addresses, semantic tiling lint, boundary-first autoresearch).