pmatch

Compare source-of-truth documents against targets to produce alignment reports.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/skillsets-cc/main --skill pmatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmatch
Source: https://github.com/skillsets-cc/main/tree/main/skillsets/%40supercollectible/Valence/content/.claude/skills/pmatch
Command: npx skills add https://github.com/skillsets-cc/main --skill pmatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pattern matching validation that compares a source-of-truth against a target to check alignment. Lighter than /ar. Use to validate plans against designs, or implementations against plans.

Core Features & Use Cases

  • Coordinate lightweight pattern-matching agents to validate alignment between documents or designs and implementations.
  • Use to confirm that a plan matches a design, or that an implementation matches a plan.
  • Use case: verify that the design spec and code reflect the same requirements in a project.

Quick Start

Provide the source and target documents to pmatch to run a pattern-match validation.

Frequently Asked Questions about pmatch

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

FAQPage Schema
How do I validate plan-to-design alignment across documents and codebases?

To validate plan-to-design alignment, you pattern-match a source-of-truth against a target document or codebase to verify they reflect the same requirements and structural patterns.

What's the best way to verify an implementation matches a plan?

The best way to verify an implementation matches a plan is to run a pattern-match validation, coordinating lightweight agents to parse inputs, spawn matchers, and merge findings into a structured alignment report.

Can I use pattern matching to check if a design spec and code reflect the same requirements?

Yes, you can use pattern matching to check if a design spec and code reflect the same requirements by providing the source and target documents to coordinate lightweight matching agents and produce a structured alignment report.

Does design review pattern matching work for both documents and codebases?

Design review pattern matching works for both documents and codebases by parsing inputs from either source type, spawning matchers to compare alignment, and merging findings into a single structured report.

When should I use lightweight pattern matching instead of a full architecture review?

You should use lightweight pattern matching instead of a full architecture review when you need to quickly validate that a plan matches a design or an implementation matches a plan without deep structural analysis overhead.