Solo developer baseline

Verified

I use this set when I am the only reviewer. The Superpowers skills keep the agent from jumping to code. The Sentry skills keep the git history readable when I am tired and the agent is eager.

Who it is for

One developer, any stack. You have a real repo, you want an agent in the loop, and you do not have a team process to lean on.

What this combination solves

Brainstorm and write a plan before the first file changes. Execute the plan one task at a time. Debug from the root cause. Refuse “done” without evidence. Write the failing test first. Then commit and open a PR with a message a future you can read.

Skills

  • Brainstorming: talk through the design before anyone writes code.
  • Writing plans: turn that design into steps the agent cannot skip.
  • Executing plans: run the plan instead of improvising a rewrite.
  • Systematic debugging: find the cause, then patch.
  • Verification before completion: show the test or the build, not a summary.
  • Test-driven development: red, green, then the real change.
  • Commit: one change, one message, no mystery dumps.
  • Create PR: the context a reviewer (even future you) needs.

AGENTS.md starter

# AGENTS.md

Entry point. Read this first. Follow links for depth.

## Repo

- App code: `src/`
- Docs: `docs/`
- Scripts: `scripts/`

## Commands

| Task | Command |
|------|---------|
| Install | `npm ci` |
| Build | `npm run build` |
| Test | `npm test` |

## Hard rules

1. Do not write code until the design is written down.
2. Follow `writing-plans` then `executing-plans`. No drive-by features.
3. Every claim of done needs a command you ran and its output.
4. Write the failing test first when the change is behavioral.
5. Use `commit` and `create-pr`. Do not invent a commit style.

## Skills

Use brainstorming, writing-plans, executing-plans, systematic-debugging,
verification-before-completion, test-driven-development, commit, create-pr.

Verification hook

Add a stop hook that fails the session if npm run build fails. How to wire it: Verification loops.

Install

One npx skills add per upstream repo. --skill picks names from that repo. -a claude-code, -a cursor, or -a codex targets one agent. Flags checked against the skills CLI README.

npx skills add obra/superpowers --skill brainstorming --skill writing-plans --skill executing-plans --skill systematic-debugging --skill verification-before-completion --skill test-driven-development

Requires Node.js 18+.

npx skills add getsentry/skills --skill commit --skill create-pr

Requires Node.js 18+.

Skills in this kit

  • Brainstorming : Guides agents through collaborative brainstorming to refine ideas into concrete designs and specifications.
  • Writing Plans : Helps outline implementation details for features and tasks by generating actionable, step-by-step plans.
  • Executing Plans : For when you have a detailed implementation plan and need to execute it methodically.
  • Systematic Debugging : Enforces a structured approach to debugging that prioritizes root cause identification over quick fixes.
  • Verification Before Completion : Ensures every claim of completion or success is backed by concrete evidence.
  • Test-Driven Development : Guides development using TDD methodology: write a failing test first, implement just enough code to make it pass, then refactor.
  • Commit : Create commits with best practices
  • Create Pr : Create pull requests