skills.rest
quantfiction
quantfictionCOMMUNITY
Explore all skills by this author →
GitHub

bead-review

Audit bead decomposition against a Technical Design Document using parallel sub-agents.

Updated Aug 27, 2026
Search Tags:#workflow#tdd#qa#audit#parallel#sub-agents#bead-review
One-click install
npx skills add https://github.com/quantfiction/dotfiles --skill bead-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bead-review
Source: https://github.com/quantfiction/dotfiles/tree/main/claude/plugins/global-skills/skills/bead-review
Command: npx skills add https://github.com/quantfiction/dotfiles --skill bead-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bead decomposition is error-prone and hard to validate. This workflow orchestrates a formal QA audit that uses multiple sub-agents to verify coverage, atomicity, dependencies, context, and metadata of bead definitions against a Technical Design Document (TDD).

Core Features & Use Cases

  • Parallel sub-agents (Coverage Checker, Atomicity Checker, Dependency Validator, Context Auditor, Metadata Checker) validate mappings, sizing, graph integrity, contracts, and testability.
  • Central synthesizer aggregates findings into a coherent verdict and maintains a ledger for traceability.
  • Iteration guardrails ensure stability before approval and guide remediation when issues are found.
  • Use Case: before implementing bead-based workflows, run bead-review to confirm all TDD requirements are covered by beads and that each bead has a single responsibility and clear dependencies.

Quick Start

Run bead-review to validate bead decompositions against the TDD and generate a consolidated verdict.

Frequently Asked Questions about bead-review

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

FAQPage Schema
How do I audit bead decomposition against a technical design document?▼

Audit bead decomposition by running parallel sub-agents that validate coverage, atomicity, dependencies, context, and metadata against a polished TDD to generate a consolidated verdict.

What is the best way to validate beads for autonomous agent execution?▼

Validate beads for autonomous agent execution by applying strict bead-level metadata checks and parallel sub-agent verification of coverage and graph integrity before synthesis.

How do I verify TDD requirements are covered by beads before implementation?▼

Verify TDD coverage by deploying a Coverage Checker sub-agent to audit mappings and confirm all technical design requirements are fully covered by individual beads.

Can I use parallel sub-agents to check bead atomicity and dependencies?▼

Yes, you can use parallel sub-agents like the Atomicity Checker and Dependency Validator to verify single responsibility and graph integrity during bead decomposition.

What do I need to run a formal QA audit on bead definitions?▼

You need a polished Technical Design Document and beads from prior stages to run a formal QA audit that enforces strict bead-level metadata and generates a traceable ledger.

How does the synthesizer aggregate bead audit findings?▼

The central synthesizer aggregates findings from parallel sub-agents into a coherent verdict and maintains a ledger for traceability, providing iteration guardrails to guide remediation.

Related Skills

Explore More Software Engineering Skills→
Obsidian-OwlObsidian-Owl
1

dev.tasks

Convert feature design artifacts into a dependency-ordered tasks.md file.

Official
Advanced
mslshaomslshao
1

autopilot

Automate planning and feature delivery into a converged plan or draft pull request.

Community
Advanced
maruakshaymaruakshay
4

agentic-trust-boundaries

Enforce typed handoff contracts and per-edge authorization checks in multi-agent workflows.

Community
Advanced
flonatflonat
127

literature

Search academic databases to find, verify, and organize research papers.

Community
Advanced