plan-verify

Execute .spec-based acceptance checks via Playwright MCP and generate verify.md reports.

9|1|Updated Mar 11, 2026

Search Tags:#automation #verification #mcp #playwright #acceptance #plan-verify

Ready to run

npx skills add https://github.com/mark22013333/crew --skill plan-verify-mark22013333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-verify
Source: https://github.com/mark22013333/crew/tree/main/plugins/feature-workflow/skills/plan-verify
Command: npx skills add https://github.com/mark22013333/crew --skill plan-verify-mark22013333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual, error-prone validation of acceptance criteria across multiple .spec tasks is slow and inconsistent. This skill automates end-to-end verification by executing .spec-based checks through Playwright MCP and producing a structured verify.md report with an optional Word output.

Core Features & Use Cases

Orchestrates automated validation of .spec/ tasks using Playwright MCP (with optional chrome-devtools-mcp support).
Generates a comprehensive verify.md report and health score, showing pass/fail status across all criteria.
Supports modes like api-only, manual, and recheck to fit diverse QA workflows across projects.

Quick Start

Trigger a complete verification by issuing /plan-verify for the active project spec set.

Frequently Asked Questions about plan-verify

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

FAQPage Schema

How do I automate browser-based acceptance verification for .spec tasks?▼

Automated acceptance verification executes .spec-based criteria through Playwright MCP to run API checks and UI validations. It locates active .spec/ tasks, constructs a verification plan, and generates a verify.md report with a health score.

What is the best way to generate automated verification reports across multiple spec tasks?▼

Generating automated verification reports involves executing .spec-based checks through Playwright MCP and producing a structured verify.md file. An optional Word report can also be generated to comprehensively show pass and fail status across all criteria.

Can I run Playwright MCP verification in api-only or manual modes?▼

Yes, Playwright MCP verification supports api-only, manual, and recheck modes to fit diverse QA workflows. These modes allow you to execute targeted API checks or guide UI validations across your defined .spec/ tasks.

Do I need chrome-devtools-mcp to perform UI validations with Playwright MCP?▼

No, chrome-devtools-mcp is an optional browser tooling component for UI validations. Playwright MCP handles the core end-to-end acceptance verification and automated report generation independently by default.

How does automated acceptance verification handle projects with defined .spec/ tasks?▼

Automated acceptance verification locates active tasks within your .spec/ directory, reads the spec files, and constructs a verification plan. It then connects browser tooling to execute checks and output a verify.md report.