checklist-runner

Validates work against Markdown checklists with pass, fail, and partial verdicts.

Updated May 13, 2026
One-click install
npx skills add https://github.com/MarcoBolsa/motor-cotacoes --skill checklist-runner-marcobolsa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checklist-runner
Source: https://github.com/MarcoBolsa/motor-cotacoes/tree/main/.claude/skills/checklist-runner
Command: npx skills add https://github.com/MarcoBolsa/motor-cotacoes --skill checklist-runner-marcobolsa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams need a consistent way to verify that completed work meets quality standards, but manually reviewing Definition of Done, pre-push, and release checklists is slow and inconsistent across agents. This Skill automates checklist execution with uniform verdicts and structured reports. ## Core Features & Use Cases - Generic Checklist Execution: Resolves any .md checklist by name or fuzzy match and processes every item with PASS, FAIL, PARTIAL, or N/A verdicts. - Dual Execution Modes: Runs autonomously in YOLO mode for a final report, or interactively with section-by-section user confirmation. - Scored Reports with Decisions: Calculates per-section pass rates and issues an APPROVED, NEEDS_WORK, or FAIL decision based on configurable thresholds. - Use Case: A developer finishing a story runs the story-dod-checklist to confirm all Definition of Done criteria are met before handing off, receiving a report listing failed items with recommendations. ## Quick Start Ask the agent to run the story-dod-checklist in yolo mode to validate your current work and produce a pass/fail report.

Frequently Asked Questions about checklist-runner

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

FAQPage Schema
How do I run a Definition of Done checklist automatically?▼

Invoke the checklist-runner with the checklist name, such as story-dod-checklist, and it processes every item autonomously in YOLO mode. It returns a report with per-item verdicts, section pass rates, and an overall APPROVED, NEEDS_WORK, or FAIL decision.

How do I validate work against a custom Markdown checklist?▼

Place your .md checklist in the checklists directory and reference it by name when invoking the runner. The engine resolves exact or fuzzy name matches and applies the same verdict and reporting logic to any checklist content.

What is the difference between yolo and interactive checklist modes?▼

YOLO mode processes all checklist sections autonomously and presents only the final report. Interactive mode pauses after each section for user confirmation, which suits reviews requiring human judgment at every step.

What happens if the checklist name does not match exactly?▼

The runner attempts a fuzzy match, so a partial name like dod resolves to story-dod-checklist.md. If multiple matches exist or none is specified, it presents a numbered list of options for selection.

How is the final checklist decision calculated?▼

The decision uses pass rate thresholds: APPROVED requires at least 90 percent pass with no critical failures, NEEDS_WORK covers 70 to 89 percent or non-critical failures, and FAIL applies below 70 percent or when critical items fail.