bb-create-verif-plan

Generate a six-section verification plan markdown from a MAS seed.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill bb-create-verif-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-create-verif-plan
Source: https://github.com/amoslee2026/Babel/tree/main/.claude/skills/bb-create-verif-plan
Command: npx skills add https://github.com/amoslee2026/Babel --skill bb-create-verif-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The design verification process often starts with an incomplete or partial plan seed. This skill expands mas/verif_plan_seed.md into a complete verification plan markdown that explicitly documents functional coverage checkpoints, target coverage, boundary cases, random constraints, and test case lists.

Core Features & Use Cases

  • Auto-generates a full verification plan (verification_plan.md) from a MAS seed, ensuring six required sections are present.
  • Integrates with the overall Babel verification flow (bb-guru-verification) and outputs a companion generation script path for TB creation.
  • Enforces a consistent, audit-friendly structure and provides a ready-to-run contract for downstream tools like bb-generate-tb.

Quick Start

In Claude Code, invoke the seed file to produce the full verification plan.

Frequently Asked Questions about bb-create-verif-plan

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

FAQPage Schema
How do I auto-generate a verification plan from a MAS seed file?

You can auto-generate a verification plan by reading a MAS seed and related MAS spec to produce a full document, consuming inputs like verif_plan_seed.md, mas_path, and design_name to output a complete verification_plan.md with artifact and generation script paths.

What is a verification plan seed and why do I need to expand it?

A verification plan seed is an incomplete or partial starting document. Expanding it ensures you explicitly document functional coverage checkpoints, target coverage, boundary cases, random constraints, and test case lists for a complete audit-friendly structure.

How do I create a verification plan that enforces a six-section structure for hardware design?

To create a six-section verification plan, the skill processes your MAS seed and enforces required sections, providing a ready-to-run contract that explicitly documents functional coverage, boundary cases, random constraints, and test case lists.

Can I use this verification plan generation workflow for downstream testbench creation?

Yes, this workflow integrates with the overall Babel verification flow and outputs a companion generator script path, serving as a ready-to-run contract for downstream testbench generation tools like bb-generate-tb.

What inputs do I need to provide for automated verification plan generation?

You need to provide the verif_plan_seed.md file, the mas_path, and the design_name. The skill reads these inputs to produce the full verification plan document and return a structured status with potential error details.

What happens if the verification plan generation encounters an error with my MAS spec?

If generation encounters an error, the skill returns a structured status containing potential error details, allowing you to audit the specific issues encountered while reading the MAS seed and related MAS spec inputs.