Audit Plan

Community

danielvm-git

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.

Overview

Publisher	danielvm-git
Repository	`bigpowers`
Skill name	`audit-plan`
Stars	206
Forks	18
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by danielvm-git on GitHub. Read the source before you install it.

Installation

Install the Audit Plan AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p .claude/skills
cp -r /tmp/bigpowers/skills/audit-plan .claude/skills/audit-plan

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Audit Plan in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Audit Plan on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Audit Plan is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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
Solo or team?	`release-branch` integration mode
Primary language + framework?	model routing + conventions
Greenfield or existing codebase?	determines whether to run `seed-conventions` or `migrate-spec` first

Process

Ingest the plan — accept a file path, pasted PRD text, or existing specs/ artifacts. Read CLAUDE.md and CONVENTIONS.md if present.
Score each lens — for every item above, mark:
- ✅ Present and adequate
- ⚠️ Present but incomplete — note what's missing
- ❌ Absent
Close gaps conversationally — for each ❌ or ⚠️, ask one question at a time. Record each answer before moving to the next.
Write specs/PLAN-AUDIT_LATEST.md:

markdown
# Plan Audit — <project>
**Date:** YYYY-MM-DD · **Verdict:** READY | NOT READY

## Principles Alignment
| Check | Status | Note |
| Vertical slices | ✅ | 4 stories, each shippable |
| Scope bounded | ⚠️ | in_scope present; out_of_scope missing |

## Conventions Completeness
| Check | Status | Note |

## Pre-flight Answers
| Command | Value |
| test | `npm test` |
| build | `npm run build` |

## Open Gaps
- [ ] Add out_of_scope to scope definition (run scope-work)
- [ ] Create CLAUDE.md (run seed-conventions)

## Verdict
READY — proceed with survey-context
NOT READY — N gaps remain; close before proceeding

Recommend next skill:
- READY → survey-context
- Needs bootstrapping → seed-conventions
- Needs spec elaboration → elaborate-spec
- Has foreign spec format → migrate-spec
- Plan assumptions need challenging → grill-me

Verify

→ verify: test -f specs/PLAN-AUDIT_LATEST.md && grep -q Verdict specs/PLAN-AUDIT_LATEST.md

Frequently asked questions

What does the Audit Plan AI skill do?

Why use Audit Plan on TypingMind?

Because you install it once and use it with any model. Audit Plan is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Audit Plan in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/danielvm-git/bigpowers/tree/main/skills/audit-plan. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Audit Plan?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Audit Plan?

As many as you like. As long as a model supports skills, you can use Audit Plan with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Audit Plan AI skill free?

Yes. It is published on GitHub by danielvm-git under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Using Superpowers

obra

CommunityPopular

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Writing Plans

Use when you have a spec or requirements for a multi-step task, before touching code

Ask Matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Audit Plan

Three lenses

1. Principles alignment

2. Conventions completeness

3. Bigpowers pre-flight (must all be answered before build)

Process

Verify

Frequently asked questions

Related AI Skills

Set up your own AI workspace now