mcp-everything-search: Skill for Claude Code

MAID Plan Review

Review a manifest and its behavioral tests before implementation begins. This is the quality gate between planning and coding.

Distinguish draft inventory from an implementation-ready contract. Drafts under manifests/drafts/ may exist before behavioral test files are created. Missing planned tests, pytest "file not found", or E200 means the draft is not ready to promote or implement yet; it is not automatically a defect in inventory planning. Apply the behavioral-test and red-phase gates only when reviewing a manifest for approval, promotion, or immediate implementation.

Rules

• NEVER modify the manifest or tests during review.
• NEVER proceed to implementation if blockers are found.
• ALWAYS confirm the red phase.
• Judge the plan, not the idea.
• Treat missing explicit signatures and missing field types as blockers.
• Treat E200 behavioral misses as blockers only for manifests presented as approval-ready, promotion-ready, or implementation-ready.
• Treat missing rationale for important design choices as a revision item.
• Treat generic, missing, or unpaired temptations as blockers when the task has obvious implementation shortcuts.

Phase 1 — Locate the Manifest

Use the path provided by the user. If none is provided, inspect recent manifests/*.manifest.yaml files and pick the most likely draft. Ask only if the choice is ambiguous.

Phase 2 — Structural Review

Check:

• schema version
• specific goal
• manifest type
• created date
• adequate description
• valid files.create, files.edit, files.read, and validate sections
• lean task-specific temptations when implementation gaming is plausible
• sensible paths and dependency coverage

Phase 3 — Scope Review

Flag manifests that are too broad, too narrow, or missing critical read dependencies.

For current MAID manifests, distinguish contracted, scope-only, and contextual files:

• files.create and files.edit are the public artifact contract.
• files.scope is writable implementation scope for files that need narrow no-artifact changes, such as route/page wiring covered by behavioral tests.
• files.read is dependency context and must not be used to authorize production edits. Test files may appear in files.read as behavioral contract inputs, but production call-site rewiring belongs in files.scope or files.edit.
• Require an intentional production edit to move from files.read to files.scope when the file has no stable public artifact contract, or to files.edit when the task changes/contracts public artifacts.
• Be wary of forcing large existing public classes into files.edit; MAID may then require declarations for the class's full public surface, expanding the manifest beyond the behavioral contract. Use files.scope for narrow no-artifact wiring instead.