paad

PAAD — Slaying the Four Horsemen of the AIpocalypse

Good developers don't ship code without tests, reviews, CI/CD, QA, and incident response. Layer after layer of defense-in-depth, because no one gets it right the first time.

AI coding assistants don't have any of that. They get it wrong and ship it anyway. PAAD adds the defense-in-depth.

---

Most AI coding assistants have the same four problems. PAAD addresses each one. See also, this horrendously long explanation.

Problem	What goes wrong	Status
Pushback	AI is a smarmy little git. Push back? No. Push to production? Absolutely. Push problems to Future You? Every time.	Largely solved
Alignment	AI hears "add a button" and delivers a button, a modal, a notification system, and a config page. The button doesn't work.	Largely solved
Architecture	Your architecture is a house of cards. AI's solution? More cards. Taller.	Partially solved
Discipline	PAA works — when you actually use it. Skip pushback, ignore alignment, defer the review, and every problem comes back worse. The process requires discipline to deliver results.	It's on you

PAAD is a system of AI agent skills that gives your coding assistant the tools to catch these problems before they compound. It supports Claude Code natively, with experimental support for Cursor, Kiro, and Antigravity.

WARNING: PAAD is brutally honest. It will tell you when your spec is flawed, your plan is misaligned, your architecture has problems, or your code has bugs. If you don't want to hear that, don't install PAAD.

Also, while this methodology has served me well, it eats tokens like popcorn at a horror movie. I'm not aiming for quantity, I'm aiming for quality.

Workflow

First, you might forget commands. That's OK. Just run /paad:help to see all available skills and their usage.

Before I start working in any repo, I run /paad:makefile to set up a standard Makefile with targets for building, testing, linting, and formatting. This gives me a consistent interface for common tasks and encourages good habits. More importantly, the code coverage, linting, and formatting tools are critical to help PAAD generate production-quality code and catch issues early.

Then I follow this general workflow:

1. Create your spec, design doc, or implementation plan as usual.
2. Before you start building, run /paad:pushback to get a critical review of your spec.
3. As you build, run /paad:alignment to check that your implementation plan matches your requirements and design.
4. When you have a working branch, run /paad:agentic-review to catch bugs, security holes, and integration problems before merging.

I often run /paad:pushback and /paad:alignment more than once to catch issues the first run (or introduced).

Also ...

1. Periodically run /paad:agentic-architecture to catch structural problems before they compound.
2. For UI changes, run /paad:agentic-a11y to catch accessibility barriers before they go live.
3. For small fixes and quick changes, use /paad:vibe to get TDD guardrails and contextual suggestions.

Installation

Claude Code

Add the marketplace

/plugin marketplace add Ovid/paad

Install the plugin

/plugin install paad@paad

Team setup (optional)

Add to your project's .claude/settings.json so teammates are automatically prompted:

{
  "extraKnownMarketplaces": {
    "paad": {
      "source": {
        "source": "github",
        "repo": "Ovid/paad"
      }
    }
  }
}

Invoking skills

You can invoke skills explicitly with /paad:pushback, /paad:alignment, etc. But Claude Code also recognizes skill names in natural language — saying "I want you to pushback on this design" or "run an architecture review" will trigger the corresponding skill. The /paad: slash command forces invocation when you want to be certain the skill runs.

Cursor (experimental)

PAAD skills use the same SKILL.md format that Cursor skills expect.

All skills (bash/zsh):

cp -r kiro_and_antigravity/skills/.kiro/skills/* .cursor/skills/

All skills (Windows):

xcopy kiro_and_antigravity\skills\.kiro\skills\* .cursor\skills\ /E /I

One skill (e.g., pushback):

cp -r kiro_and_antigravity/skills/.kiro/skills/pushback .cursor/skills/

Kiro (experimental)

All skills (bash/zsh):

cp -r kiro_and_antigravity/skills/.kiro/skills/* .kiro/skills/

All skills (Windows):

xcopy kiro_and_antigravity\skills\.kiro\skills\* .kiro\skills\ /E /I