auditing-upstream-drift

name	auditing-upstream-drift
description	Use when checking if beads-superpowers is outdated, before a plugin release, or when auditing for missing capabilities — covers upstream drift, test execution, documentation, plugin health, and content integrity

Auditing Upstream Drift

This is the quality gate for the beads-superpowers plugin. It verifies everything — upstream staleness, test pass rates, documentation accuracy, plugin manifest validity, hook functionality, content integrity, and beads integration completeness.

Iron Law: NO PLUGIN RELEASE WITHOUT A FULL AUDIT FIRST.

When to Use

• Before any plugin version bump or release
• Monthly (or after upstream releases of superpowers or beads)
• When a user reports a skill behaves differently than expected
• When beads adds new CLI features that skills should leverage
• After any bulk refactoring of skills or tests
• After merging upstream changes

Upstream Sources

Source	Repository	Our Baseline	What We Track
Superpowers	obra/superpowers	v5.0.7	Skills content, new skills, hook structure, plugin manifest
Beads	gastownhall/beads	v1.0.0	CLI commands, new features, bd prime format, deprecations

The Audit Process

You MUST create an audit bead and complete ALL 7 phases in order:

bd create "Audit: full plugin health check" -t chore -p 1
bd update <audit-id> --claim

---

Phase 1: Plugin Infrastructure Health

Verify the plugin itself is structurally sound before checking content.

Check 1.1 — Plugin manifest validation:

claude plugin validate .claude-plugin/plugin.json
# MUST show: ✔ Validation passed

If validation fails, the plugin CANNOT be installed. Fix before proceeding.

Check 1.2 — Version consistency across 3 files:

grep '"version"' .claude-plugin/plugin.json .claude-plugin/marketplace.json package.json
# ALL THREE must show the same version string

If versions drift, run: ./scripts/bump-version.sh <version>

Check 1.3 — Hook is executable and produces valid JSON:

# Executable?
test -x hooks/session-start && echo "PASS" || echo "FAIL: chmod +x hooks/session-start"

# Valid JSON output?
bash hooks/session-start 2>&1 | python3 -m json.tool > /dev/null && echo "PASS" || echo "FAIL: hook output is not valid JSON"

Check 1.4 — Hook injects both skills AND bd prime:

output=$(bash hooks/session-start 2>&1)
echo "$output" | grep -q "using-superpowers" && echo "PASS: skills injected" || echo "FAIL: skills not injected"
echo "$output" | grep -q "beads-context\|bd prime\|Beads Workflow" && echo "PASS: bd prime injected" || echo "FAIL: bd prime not injected"

Check 1.5 — .claude/settings.json points to plugin hook (not bare bd prime):

cat .claude/settings.json | grep -q "hooks/session-start" && echo "PASS" || echo "FAIL: settings.json still uses bare bd prime, not plugin hook"

Check 1.6 — Duplicate hook detection:

cat .claude/settings.json | grep -q '"bd prime"' && echo "WARNING: bd setup claude hooks still installed — run bd setup claude --remove" || echo "PASS: no duplicate hooks"

Check 1.7 — Skills count:

count=$(ls -d skills/*/ | wc -l)
echo "Skills: $count (expected: 15)"
[ "$count" -eq 15 ] && echo "PASS" || echo "FAIL: expected 15 skills"

Check 1.8 — LICENSE attribution:

grep -q "Dillon Frawley" LICENSE && echo "PASS" || echo "FAIL: LICENSE does not have correct attribution"
grep -q "Jesse Vincent" LICENSE && echo "FAIL: LICENSE still has upstream author" || echo "PASS"

---

Phase 2: Test Execution

Run ALL runnable tests. Tests are the ground truth — if they fail, nothing else matters.

Check 2.1 — Brainstorm server tests (25 tests):

cd tests/brainstorm-server
npm install --silent 2>/dev/null
npm test 2>&1 | tail -1
# MUST show: --- Results: 25 passed, 0 failed ---

Check 2.2 — WebSocket protocol tests (31 tests):

cd tests/brainstorm-server
node ws-protocol.test.js 2>&1 | tail -1
# MUST show: --- Results: 31 passed, 0 failed ---

Check 2.3 — Claude Code fast skill tests (9 subtests):

cd <repo-root>
bash tests/claude-code/run-skill-tests.sh --timeout 600 2>&1 | tail -5
# MUST show: STATUS: PASSED

This runs real Claude API calls (~$0.10, ~165s). Tests verify:

• Skill is recognised and loaded
• Workflow ordering (spec compliance before code quality)
• Self-review requirement documented
• Plan reading efficiency documented
• Spec reviewer scepticism documented
• Review loops documented
• Full task text provided directly (not file reference)
• Worktree requirement mentioned
• Main branch warning present

Check 2.4 — Integration test (OPTIONAL, ~$4-5, 10-30 min):

bash tests/claude-code/run-skill-tests.sh --integration --timeout 2400 2>&1
# Full end-to-end: creates project, executes plan via subagents, verifies output

Only run this before a release or after major workflow changes. It validates:

• Real subagent dispatching
• Beads (bd create/close) used for task tracking
• Implementation files created and tests pass
• Git commits made
• Correct skill namespace (beads-superpowers:subagent-driven-development)

If any test fails: STOP. Fix the test failure before proceeding with the audit.

---

Phase 3: Content Integrity

Verify the beads integration is complete and no stale references remain.

Check 3.1 — Zero active TodoWrite references:

results=$(grep -rn "TodoWrite" skills/ | grep -v "Do NOT use TodoWrite" | grep -v "replaces TodoWrite" | grep -v "auditing-upstream-drift")
[ -z "$results" ] && echo "PASS: zero active TodoWrite" || echo "FAIL: $results"

The only allowed TodoWrite references are prohibitions ("Do NOT use TodoWrite") and this audit skill's own grep patterns.

Check 3.2 — Zero stale docs/superpowers/ paths:

results=$(grep -rn "docs/superpowers" skills/ tests/ | grep -v "auditing-upstream-drift")
[ -z "$results" ] && echo "PASS" || echo "FAIL: stale paths found: $results"

All paths should use .internal/.

Check 3.3 — Zero stale skill namespace references:

results=$(grep -rn '"superpowers:' skills/ tests/ | grep -v "beads-superpowers:")
[ -z "$results" ] && echo "PASS" || echo "FAIL: stale namespaces: $results"

Check 3.4 — Zero stale plugin-dir paths:

results=$(grep -rn "/path/to/superpowers" tests/)
[ -z "$results" ] && echo "PASS" || echo "FAIL: stale plugin paths: $results"

Check 3.5 — Zero TodoWrite in tests:

results=$(grep -rn "TodoWrite" tests/)
[ -z "$results" ] && echo "PASS" || echo "FAIL: TodoWrite in tests: $results"

Check 3.6 — Beads command density (must be 30+):

count=$(grep -rn "bd create\|bd close\|bd ready\|bd update\|bd dep\|bd dolt" skills/ | wc -l)
echo "Beads command references in skills: $count (minimum: 30)"
[ "$count" -ge 30 ] && echo "PASS" || echo "FAIL: insufficient beads integration"

Check 3.7 — Subagent prompts must NOT reference beads:

# Orchestrator-only design: subagents don't touch beads
for f in skills/subagent-driven-development/implementer-prompt.md skills/subagent-driven-development/spec-reviewer-prompt.md skills/subagent-driven-development/code-quality-reviewer-prompt.md; do
    count=$(grep -c "bd create\|bd close\|bd update\|bd ready" "$f" 2>/dev/null || echo 0)
    [ "$count" -eq 0 ] && echo "PASS: $(basename $f) clean" || echo "FAIL: $(basename $f) has $count bd references"
done

---

Phase 4: Progressive Skill Chain Integrity

The skills form a pipeline. Every link must be intact.

echo "=== Progressive Skill Chain ==="

# brainstorming → writing-plans (terminal state)
grep -q "writing-plans" skills/brainstorming/SKILL.md && echo "PASS: brainstorming → writing-plans" || echo "FAIL"

# writing-plans → subagent-driven-development OR executing-plans
grep -q "subagent-driven-development" skills/writing-plans/SKILL.md && echo "PASS: writing-plans → subagent-driven-dev" || echo "FAIL"
grep -q "executing-plans" skills/writing-plans/SKILL.md && echo "PASS: writing-plans → executing-plans" || echo "FAIL"

# subagent-driven-development → finishing-a-development-branch
grep -q "finishing-a-development-branch" skills/subagent-driven-development/SKILL.md && echo "PASS: subagent-driven-dev → finishing" || echo "FAIL"

# executing-plans → finishing-a-development-branch
grep -q "finishing-a-development-branch" skills/executing-plans/SKILL.md && echo "PASS: executing-plans → finishing" || echo "FAIL"

# finishing-a-development-branch has Land the Plane
grep -q "Land the Plane" skills/finishing-a-development-branch/SKILL.md && echo "PASS: finishing has Land the Plane" || echo "FAIL"

# using-superpowers has Beads Issue Tracking section
grep -q "Beads Issue Tracking" skills/using-superpowers/SKILL.md && echo "PASS: bootstrap has beads awareness" ||  


grep -q  skills/verification-before-completion/SKILL.md &&   ||  

---

Phase 5: Upstream Superpowers Drift

Clone upstream and compare.

git clone --depth 1 https://github.com/obra/superpowers.git /tmp/superpowers-upstream

Check 5.1 — Version gap:

upstream_ver=$(grep '"version"' /tmp/superpowers-upstream/package.json | grep -o '[0-9.]*')
echo "Upstream: v$upstream_ver | Our baseline: v5.0.7"

Check 5.2 — New skills in upstream:

diff <(ls /tmp/superpowers-upstream/skills/) <(ls skills/) | grep "^<"
# Lines starting with < are skills upstream has that we don't

For each new skill: assess if relevant (skip platform-specific ones).

Check 5.3 — Content changes in shared skills:

for skill in /tmp/superpowers-upstream/skills/*/SKILL.md; do
    name=$(basename $(dirname "$skill"))
    if [ -f "skills/$name/SKILL.md" ]; then
        changes=$(diff "$skill" "skills/$name/SKILL.md" | wc -l)
        [ "$changes" -gt 0 ] && echo "CHANGED: $name ($changes diff lines)"
    fi
done

For changed skills, categorise each:

• Safe merge: Change doesn't touch our beads-integrated sections
• Conflict: Change touches our modified sections → manual review
• New content: New sections added → assess and add with beads awareness

Check 5.4 — New companion files:

for dir in /tmp/superpowers-upstream/skills/*/; do
    name=$(basename "$dir")
    if [ -d "skills/$name" ]; then
        new_files=$(diff <(ls "$dir" 2>/dev/null | sort) <(ls "skills/$name" 2>/dev/null | sort) | grep "^<" | sed 's/^< //')
        [ -n "$new_files" ] && echo "NEW FILES in $name: $new_files"
    fi
done

Check 5.5 — Hook and manifest changes:

diff /tmp/superpowers-upstream/hooks/hooks.json hooks/hooks.json | head -20
diff /tmp/superpowers-upstream/.claude-plugin/plugin.json .claude-plugin/plugin.json | head -20

Our hook is intentionally different (adds bd prime). Check for structural changes, new hook types, or new manifest fields.

rm -rf /tmp/superpowers-upstream

---

Phase 6: Upstream Beads Drift

Check if beads has new capabilities our skills should use.

Check 6.1 — Beads version:

bd version
# Compare against our baseline (v1.0.0)

Check 6.2 — New or changed bd commands:

bd --help 2>&1 | head -60
# Look for new commands not in our skills' Quick Reference tables

Check 6.3 — bd prime format:

bd prime 2>&1 | head -20
# Compare structure against what hooks/session-start expects

Check 6.4 — New beads features to watch:

• New dependency types → update bd dep add references
• New issue types → update bd create -t references
• New status codes → update lifecycle references
• New CLI flags → update quick reference tables
• Changes to gate/molecule/formula system → assess skill impact

---

Phase 7: Documentation Accuracy

Verify all documentation reflects the current state.

Check 7.1 — README skills count matches actual:

actual=$(ls -d skills/*/ | wc -l)
readme_count=$(grep -o "[0-9]* skills" README.md | head -1 | grep -o "[0-9]*")
echo "Actual: $actual | README: $readme_count"
[ "$actual" = "$readme_count" ] && echo "PASS" || echo "FAIL: README skills count is stale"

Check 7.2 — README skills table has all skills:

for dir in skills/*/; do
    name=$(basename "$dir")
    grep -q "$name" README.md && echo "PASS: $name in README" || echo "FAIL: $name missing from README"
done

Check 7.3 — CHANGELOG has current version:

version=$(grep '"version"' package.json | grep -o '[0-9.]*')
grep -q "\[$version\]" CHANGELOG.md && echo "PASS: v$version in CHANGELOG" || echo "FAIL: v$version missing from CHANGELOG"

Check 7.4 — CLAUDE.md skills table matches actual:

for dir in skills/*/; do
    name=$(basename "$dir")
    grep -q "$name" CLAUDE.md && echo "PASS: $name in CLAUDE.md" || echo "FAIL: $name missing from CLAUDE.md"
done

Check 7.5 — SETUP-GUIDE install commands use correct names:

grep -q "DollarDill/beads-superpowers" .internal/SETUP-GUIDE.md && echo "PASS: correct marketplace repo" || echo "FAIL"
grep -q "beads-superpowers@beads-superpowers-marketplace" .internal/SETUP-GUIDE.md && echo "PASS: correct install command" || echo "FAIL"

Check 7.6 — Copied upstream docs don't have stale references:

# These docs were adapted from superpowers — verify no stale refs
for f in .internal/testing.md .internal/windows/polyglot-hooks.md tests/claude-code/README.md; do
    stale=$(grep -c "superpowers" "$f" | head -1)
    allowed=$(grep -c "beads-superpowers\|obra/superpowers\|upstream" "$f" | head -1)
    raw=$((stale - allowed))
    [ "$raw" -le 0 ] && echo "PASS: $f clean" || echo "WARNING: $f may have $raw stale superpowers refs"
done

---

Phase 8: Generate Audit Report

Create beads for each finding and write the report.

# Create child beads for each finding
bd create "Drift: [description]" -t chore -p 3 --parent <audit-id>
bd create "CRITICAL: [description]" -t bug -p 0 --parent <audit-id>

Write the report to .internal/audits/YYYY-MM-DD-upstream-drift.md:

# Plugin Audit — YYYY-MM-DD

## Infrastructure
- Plugin manifest: PASS/FAIL
- Version consistency: PASS/FAIL (version)
- Hook functional: PASS/FAIL
- Settings.json: PASS/FAIL
- Skills count: N
- LICENSE: PASS/FAIL

## Tests
- Brainstorm server: N/25 passed
- WS protocol: N/31 passed
- Fast skill tests: PASS/FAIL (N subtests)
- Integration test: RAN/SKIPPED

## Content Integrity
- TodoWrite residue: PASS/FAIL
- Stale paths: PASS/FAIL
- Stale namespaces: PASS/FAIL
- Beads density: N references (min 30)
- Subagent isolation: PASS/FAIL
- Skill chain: PASS/FAIL

## Upstream Drift
- Superpowers: vX.Y.Z (baseline v5.0.7) — N changes
- Beads: vX.Y.Z (baseline v1.0.0) — N new features
- New skills: N (action: copy/skip for each)
- Changed skills: N (action: merge/conflict/skip for each)

## Documentation
- README: PASS/FAIL
- CHANGELOG: PASS/FAIL
- CLAUDE.md: PASS/FAIL
- SETUP-GUIDE: PASS/FAIL
- Copied docs: PASS/FAIL

## Findings: N total (C critical, I important, M minor)

## Actions Required
- [List with bead IDs]

Close the audit bead:

bd close <audit-id> --reason "Audit complete: N findings (C critical, I important, M minor)"

---

Quick Audit (Phases 1-4 Only)

For fast checks without upstream comparison:

# Run this single block for a quick health check
echo "=== Quick Audit ===" && \
claude plugin validate .claude-plugin/plugin.json 2>&1 | tail -1 && \
test -x hooks/session-start && echo "Hook: executable" && \
bash hooks/session-start 2>&1 | python3 -m json.tool > /dev/null && echo "Hook: valid JSON" && \
echo "Skills: $(ls -d skills/*/ | wc -l)" && \
echo "TodoWrite residue: $(grep -rn 'TodoWrite' skills/ | grep -v 'Do NOT use' | grep -v 'replaces' | grep -v 'auditing-upstream-drift' | wc -l)" && \
echo "Stale paths: $(grep -rn 'docs/superpowers' skills/ tests/ | grep -v 'auditing-upstream-drift' | wc -l)" && \
echo "Stale namespace: $(grep -rn '"superpowers:' skills/ tests/ | grep -v 'beads-superpowers:' | wc -l)" && \
echo "Beads density: $(grep -rn 'bd create\|bd close\|bd ready\|bd update\|bd dep\|bd dolt' skills/ | wc -l)" && \
echo "Version: $(grep '"version"' package.json | grep -o '[0-9.]*')" && \
cd tests/brainstorm-server && npm test 2>&1 | tail -1 && node ws-protocol.test.js 2>&1 | tail -1 && cd ../.. && \
echo "=== Quick Audit Complete ==="

Audit Frequency

Trigger	Action
Before any plugin release	Full audit (all 8 phases) — MANDATORY
Monthly	Phases 1-4 (infrastructure + tests + content + chain)
After upstream superpowers release	Add Phase 5
After upstream beads release	Add Phase 6
After bulk skill edits	Phases 2-4 (tests + content + chain)
After test refactoring	Phase 2 only (run all tests)
User reports mismatch	Phase 3 check 3.x for the specific issue + Phase 5 check 5.3 for the skill
Quick sanity check	Quick Audit block above

Cleanup

rm -rf /tmp/superpowers-upstream

If you discovered something reusable, capture it before closing:

# Only if worth preserving for future sessions:
bd remember "upstream: <drift finding or new capability>"

Integration

Invoked by: No other skill invokes this directly. Standalone audit skill — run before releases or on-demand.

Invokes: None. References other skills as audit targets but does not invoke them.