maid_validate
Validate MAID manifests against code, tests, or schema using three modes: implementation, behavioral, and schema.
Instructions
Validate a MAID manifest using MAID Runner.
When to use:
Phase 2 (Planning): After creating/updating a manifest, validate it passes
Phase 3 (Implementation): After writing code, verify it matches the manifest
Before committing: Ensure all manifests are valid
Validation modes:
implementation: Checks that code artifacts match manifest expectedArtifactsbehavioral: Checks that tests exist and reference the expected artifactsschema: Checks that the manifest structure conforms to the JSON schema
Use manifest chain when:
Editing existing files (taskType: "edit")
The file has previous manifests that define its history
You need to verify the full history of changes is valid
Args: manifest_path: Path to the manifest JSON file validation_mode: Validation mode (implementation, behavioral, or schema) use_manifest_chain: Whether to use manifest chain for validation manifest_dir: Directory containing manifests (optional) quiet: Whether to suppress verbose output ctx: MCP context for accessing working directory
Returns: ValidateResult with validation outcome
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| manifest_path | Yes | ||
| validation_mode | No | implementation | |
| use_manifest_chain | No | ||
| manifest_dir | No | ||
| quiet | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| success | No | ||
| mode | No | ||
| manifest | No | ||
| target_file | No | ||
| used_chain | No | ||
| errors | No | ||
| file_tracking | No |