bart-plan-review

Validate plan.md outputs against bart parser rules and traceability requirements.

8|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/leandrostoroli/bart-loop --skill bart-plan-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bart-plan-review
Source: https://github.com/leandrostoroli/bart-loop/tree/main/skills/bart-plan-review
Command: npx skills add https://github.com/leandrostoroli/bart-loop --skill bart-plan-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bart Plan Review provides a formal quality gate for plan.md outputs produced by bart-plan, ensuring parsing integrity and traceable task mapping before execution.

Core Features & Use Cases

  • Format validation: checks plan.md against bart parser rules to catch structural issues early.
  • Coverage & traceability: validates requirements-to-tasks mapping and detects orphan or unreferenced requirements.
  • Decision-ready reports: surfaces findings and next steps for user approval to proceed.

Quick Start

Invoke bart-plan-review on the latest plan.md to validate format, coverage, and readiness.

Frequently Asked Questions about bart-plan-review

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

FAQPage Schema
How do I validate a plan.md file for parser compatibility?

Plan review validates plan.md outputs against parser rules to catch structural issues early, ensuring parsing integrity and traceable task mapping before execution begins.

What is plan review quality assurance for structured markdown plans?

Plan review quality assurance audits structured markdown plans to verify format compliance, validate requirements-to-tasks mapping, and detect orphan requirements across workstreams and dependencies.

How do I detect orphan requirements in my project workstreams?

To detect orphan requirements in project workstreams, run a coverage and traceability validation on your plan output to identify unreferenced requirements and surface actionable findings for approval.

Does plan quality validation work with dependencies across multiple workstreams?

Plan quality validation works across multiple workstreams and dependencies by enforcing format rules and verifying that all requirements are traceable to specific tasks.

Why does my structured plan fail format validation rules?

A structured plan fails format validation when it violates parser compatibility rules, contains orphan requirements, or lacks traceable task mapping across workstreams and dependencies.

Can I generate a decision-ready report after auditing a plan.md file?

You can generate a decision-ready report after auditing a plan.md file by running a quality gate review that surfaces findings and actionable next steps for user approval to proceed.