Audit Plan

Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins. Use when a new project arrives, when adapting a foreign plan, or before running seed-conventions on an unfamiliar codebase.

292 stars 23 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add danielvm-git/bigpowers --skill audit-plan
Manual install
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p ~/.claude/skills
cp -r /tmp/bigpowers/.cline/skills/audit-plan ~/.claude/skills/audit-plan

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Audit Plan

> **HARD GATE** — Do NOT start build skills (kickoff-branch, develop-tdd) until audit-plan returns a READY verdict. A plan missing test commands, scope boundaries, or success criteria will produce drift and rework downstream.

Assess an incoming project plan for alignment with bigpowers principles, identify what's missing, and produce a structured readiness report before any skill execution begins.

## Three lenses

### 1. Principles alignment
- Are stories vertical slices (not horizontal layers)?
- Is scope bounded — explicit in_scope + out_of_scope?
- Are success criteria defined (how do we know we're done)?
- Are HARD GATE candidates identifiable (critical decision points)?
- Is there a domain language / ubiquitous terminology?

### 2. Conventions completeness
- Does `CLAUDE.md` or `AGENTS.md` exist?
- Does `CONVENTIONS.md` exist?
- Is the `specs/` directory layout in place?
- Are commit conventions documented (Conventional Commits)?
- Is the git workflow mode identified (`solo-git` | `team-pr`)?

### 3. Bigpowers pre-flight (must all be answered before build)
| Question | Why |
|----------|-----|
| What is the **test command**? | `develop-tdd` verify steps require it |
| What is the **build command**? | `verify-work` mechanical gate |
| What is the **lint command**? | `audit-code` lint gate |
| What is the **typecheck command**? | `verify-work` typecheck gate |
| What **CI platform** is in use? | `wire-ci` configuration |
Read the full skill on GitHub

Details

Skill name
audit-plan
Path
.cline/skills/audit-plan/SKILL.md
License
MIT
Repo updated
9 November 2026

FAQ

What does the Audit Plan skill do?

Evaluate an incoming project plan against bigpowers principles and conventions, surface gaps, and produce a READY/NOT READY verdict before engagement begins. Use when a new project arrives, when adapting a foreign plan, or before running seed-conventions on an unfamiliar codebase.

How do I install the Audit Plan skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add danielvm-git/bigpowers --skill audit-plan. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Audit Plan popular?

It lives in danielvm-git/bigpowers, which has 292 GitHub stars and 23 forks.

Related skills

Align Grid

292

danielvm-git/bigpowers

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style) — not a decorative one. Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the hard-won front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay that lives in the SAME content box as the content, subgrid "bands" so every element snaps to a column line, an 8px baseline lock, and runtime OPTICAL ALIGNMENT that puts display type's i

Writing & Content23

Assess Impact

292

danielvm-git/bigpowers

Analyze the blast radius of a proposed change before any code is written. Maps dependents, affected stories, and test coverage. Produces specs/IMPACT_LATEST.md. Use before plan-work on any non-trivial change, when touching a shared module, or when the user asks "what does this break?".

Testing & QA23

Audit Code

292

danielvm-git/bigpowers

Self-review checklist for the coding agent to run before dispatching a reviewer. Checks CONVENTIONS.md compliance, Boy Scout Rule, test coverage, types, and SOLID. Produces a pass/fail checklist. Use before request-review, before committing, or when user asks for a code quality check.

Software Development23

Deepen Architecture

292

danielvm-git/bigpowers

Find deepening opportunities in a codebase, informed by the domain language in specs/tech-architecture/tech-stack.md and the decisions in specs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Software Development23

Design Interface

292

danielvm-git/bigpowers

Generate multiple radically different interface designs for a module using parallel sub-agents, then compare trade-offs. Based on "Design It Twice" from A Philosophy of Software Design. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

Software Development23

Xint Rs

223

NeverSight/learn-skills.dev

Fast X Intelligence CLI (Rust) — search, analyze, and engage on X/Twitter from the terminal. Use when: (1) user says "x research", "search x for", "search twitter for", "what are people saying about", "what's twitter saying", "check x for", "x search", "search x", (2) user wants real-time monitoring with "watch", (3) user needs AI-powered analysis with Grok ("analyze", "sentiment"), (4) user needs intelligence reports ("report"), (5) user wants to track followers ("diff"), (6) user needs trending topics ("trends"). Also supports: bookmarks, likes, following (OAuth), x-search, collections, CSV/

Software Development42

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.