karen

Audit project artifacts and commit histories against claimed work in sprint reviews, issue closures, and PR audits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill karen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: karen
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/karen
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill karen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completion reality check -- validates what was actually built vs claimed. Use before committing or closing issues.

Core Features & Use Cases

  • Verifies alignment between claimed work and actual implementation across sessions, commits, issues, and PRs.
  • Detects gaps in scope, requirements, and delivered artifacts, enabling faster remediation.
  • Supports governance workflows by providing structured citations for each gap.

Quick Start

Run the karen agent to audit current session claims against actual work.

Frequently Asked Questions about karen

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify if claimed work matches actual code implementation before closing a sprint?

To verify claimed work against actual implementation, audit project artifacts and commit histories to identify gaps between scope requirements and delivered artifacts. This validates alignment across sessions, commits, issues, and PRs for sprint reviews and issue closures.

What is a project artifact audit and when do I need it for issue closures?

A project artifact audit detects gaps between claimed work and actual implementation across code, docs, and tests. You need it during sprint reviews, issue closures, and PR audits to ensure delivery claims match actual built work before committing.

How do I audit GitHub Issues and PRs against my implementation plan?

Audit GitHub Issues and PRs by validating them against IMPLEMENTATION_PLAN.md, spec files, and MASTER_ROADMAP.md. This checks alignment between claimed work and actual implementation, providing structured citations for each detected gap.

Does this validation tool work with Supabase and GitHub project management workflows?

Yes, it validates claimed work against actual implementation by auditing GitHub Issues, commit histories, and the intel.decisions store in Supabase. It supports governance workflows by providing structured citations for gaps across code and docs.

What's the best way to detect scope gaps in delivered project artifacts?

Detect scope gaps in delivered artifacts by auditing project artifacts and commit histories against implementation plans and spec files. This validates alignment between claimed work and actual implementation, enabling faster remediation of gaps.

When should I run a completion reality check on my project deliverables?

Run a completion reality check before committing or closing issues to validate what was actually built versus claimed. This applies to sprint reviews, issue closures, and PR audits across code, docs, tests, and other deliverables.