claudity-assurance

claudity-assurance

A self-learning QA plugin for Claude Code that gives solo developers an independent verification layer for their work.

It operates as a black-box tester — it never sees your source code. Instead, it builds its own knowledge about your system through interviews, exploration, and testing, then verifies behavioral specifications (BDDs) against the running system. Over time, it accumulates institutional QA knowledge that gets better with every session.

The Problem

When you're a solo developer, you're writing code and testing it yourself. That means your tests are biased by your knowledge of the implementation — you test what you built, not what the system should do. Bugs hide in the gap between those two things.

Claudity-assurance fills that gap by creating a QA session that:

• Doesn't know how your code works (by design)
• Tests behavior, not implementation
• Remembers what it's verified before and watches for regressions
• Learns how to interact with your system and never asks the same question twice

How It Works

Claudity-assurance operates across two Claude Code sessions:

Session 1 (Dev)                          Session 2 (QA)
─────────────────                        ────────────────
Your normal dev work                     Isolated QA directory
  │                                        │
  ├─ Brainstorm features                   ├─ Onboard: interview about the system
  ├─ Write specs & plans                   ├─ Build interaction surface (browser, API, etc.)
  ├─ Implement code                        ├─ Verify BDDs against running system
  ├─ Generate BDDs ──── qa/bdds/ ─────────>├─ Produce verification reports
  │                                        ├─ Run regression checks
  │                                        ├─ Update knowledge graph
  │               ◄── results/ ────────────├─ Evidence (screenshots, logs, notes)
  └─ Fix failures                          └─ Get smarter every session

Session 1 (Dev) — Your normal development session. After brainstorming or implementing a feature, generate BDD scenarios that describe what the system should do in plain behavioral terms. These get dropped into a shared qa/bdds/ directory.

Session 2 (QA) — A separate Claude session running in an isolated QA directory. It picks up BDD scenarios, tests them against the running system as a black box, and builds a growing knowledge base about how to interact with and verify the system.

The Boundary

The two sessions are deliberately isolated:

• Session 1 can only write to qa/bdds/ — it cannot read QA results or docs
• Session 2 lives entirely inside qa/ — it cannot read source code, specs, or implementation files
• The BDD dropbox (qa/bdds/) is the only shared artifact

This separation ensures the QA session tests behavior, not implementation.

Installation

/plugin marketplace add https://github.com/look-itsaxiom/claudity-assurance.git
/plugin install claudity-assurance

Or for local development:

claude --plugin-dir /path/to/claudity-assurance

Quick Start

Scenario A: Existing Project

You have a project and want to add QA verification.

1. Create the QA environment

cd your-project
mkdir qa
cd qa
claude

/claudity-assurance:onboard

Claude will interview you about the system — what it is, how to access it, what tools to use for testing. It then scaffolds the QA directory and writes its initial knowledge docs.

2. Generate BDDs from your dev session

In a separate Claude session in your project root:

/claudity-assurance:generate-bdds

This reads your most recent spec or plan and produces behavioral scenarios in Gherkin format, dropping them in qa/bdds/.

3. Verify in the QA session

Back in the QA session:

/claudity-assurance:verify

Claude picks up the BDDs, tests each scenario against the running system, collects evidence, checks for regressions, and produces a verification report.

Scenario B: New Project

Starting fresh with no code yet.

1. Create the QA directory and onboard

mkdir my-project/qa
cd my-project/qa
claude

/claudity-assurance:onboard

During onboarding, Claude will help you define initial BDD scenarios and test them — building its knowledge base from scratch.

2. Brainstorm with BDDs

In your dev session, use the combined workflow:

/claudity-assurance:brainstorm-with-bdds

This runs the full brainstorming process and automatically generates BDDs from the approved spec.

3. Iterate

Implement features in Session 1, generate BDDs, verify in Session 2. The QA session gets smarter each cycle.

Commands

Session 1 (Dev)

Command	Purpose
/c-a:generate-bdds	Generate BDD scenarios from a spec or plan document
/c-a:brainstorm-with-bdds	Brainstorm a feature, then generate BDDs from the result

Session 2 (QA)