AI Development Lifecycle — Claude Code Skills

A curated, opinionated set of Claude Code skills that cover the whole software lifecycle — from a vague idea all the way to a deployed, tested product.

These are among the best Claude Code skills I found online. I combined them into a single workflow for my own day-to-day building, and I'm sharing it in case it's useful to you. All credit goes to the original authors — see CREDITS.md. Everything here is MIT-licensed.

Built from the work of Jesse Vincent (obra/superpowers), Addy Osmani (addyosmani/agent-skills), Matt Pocock (mattpocock/skills), Garry Tan (garrytan/gstack), and Affaan Mustafa (affaan-m/ECC), plus a few custom skills of my own.

The lifecycle

Bold = the must-do spine. Indented = optional, for when the situation calls for it.

| # | Stage | Skill | From | |---|---|---|---| | 0 | Project setup (once) | /setup | Custom | | 1 | Discover what you actually want | /product-thought | Custom | | 1b | (opt) Is it worth building? | /product-lens | Affaan Mustafa | | 1c | (opt) Research first | /deep-research | Affaan Mustafa | | 1d | (opt) Visual / UX question | /prototype-screen | Custom | | 2 | Lock the design | /design-with-docs · /design-me | Matt Pocock | | 3 | Write the PRD | /prd-me | Matt Pocock | | 4 | Break into tasks | /issue-me | Matt Pocock | | 4b | (opt) Order & label | /triage | Matt Pocock | | 5 | Build each task (TDD) | /test-driven-dev | Matt Pocock | | 5b | When something breaks | /diagnose-me | Matt Pocock | | 6 | Verify the change | /qa-me | Custom | | 6b | Does it match the PRD? | /compare-me | Custom | | 6c | Clean up + secure | /kill-dead | Custom | | 7 | Deploy | /deploy-me | Custom | | 7b | (once) Automate the gate | /ci-cd-me | Addy Osmani | | 8 | End-to-end tests | /e2e-test-me | Affaan Mustafa | | 8b | Click-through QA | /browser-qa-me | Affaan Mustafa | | 8c | Launch readiness gate | /audit-me | Affaan Mustafa | | 8d | Security pass | /security-review | Affaan Mustafa | | 8e | (opt) Watch production | /canary-watch | Affaan Mustafa |

The daily inner loop (small changes): /test-driven-dev → /qa-me → /compare-me → /kill-dead → /deploy-me.

Install

Claude Code loads skills from ~/.claude/skills/ (global) or <project>/.claude/skills/ (per-project). Each skill is a folder with a SKILL.md.

The easy way (npm):

npx @harsh-mvp/adlc            # installs all skills into ~/.claude/skills/
npx @harsh-mvp/adlc --project  # installs into ./.claude/skills/ (this project only)
npx @harsh-mvp/adlc --force    # overwrite skills that already exist

Existing skills of the same name are skipped unless you pass --force. No bash required — works on macOS, Linux, and Windows.

From source (git):

git clone https://github.com/Harsh-launchpad/claude-dev-lifecycle.git
cd claude-dev-lifecycle
./install.sh           # copies the skills into ~/.claude/skills/ (won't overwrite existing)

Or copy individual skills/<name>/ folders into ~/.claude/skills/ by hand.

How to use

Type /<skill-name> to run a skill, or just describe what you want in plain words — Claude fires the matching skill on its own. Start a new project with /setup, then /product-thought. Full step-by-step is the table above.

License & credits

MIT. The custom skills and this collection are © 2026 Harsh (LICENSE). Redistributed skills retain their original authors' MIT licenses — see CREDITS.md and licenses/. If you're an author and want anything changed, open an issue.