forge-validate

Validate system conformance to Forge specs via static analysis and test mapping.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/GreyFlames07/forge --skill forge-validate-greyflames07
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: forge-validate
Source: https://github.com/GreyFlames07/forge/tree/main/.agents/skills/forge-validate
Command: npx skills add https://github.com/GreyFlames07/forge --skill forge-validate-greyflames07

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Forge-validate helps teams verify that implemented systems conform to the Forge spec corpus by surfacing gaps between declared contracts, tests, and runtime behavior.

Core Features & Use Cases

  • Static analysis: checks inputs, outputs, failure modes, and side effects against L3/L2 specs.
  • Test-suite mapping: maps test results to spec elements via audit matrices and reports coverage gaps.
  • Live interactions: optionally starts the system, fires exact/probing requests, and validates real responses against specs.
  • Observability groundwork: optionally references L5 observability to compare SLAs and metrics.

Quick Start

Invoke forge-validate after forge-implement completes to generate the validation report.

Frequently Asked Questions about forge-validate

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

FAQPage Schema
How do I validate my codebase against a spec corpus?▼

To validate a codebase against a spec corpus, you cross-check declared contracts, tests, and runtime behavior using static analysis, test-suite mapping, and live interaction probes to surface implementation gaps.

What is static analysis for spec validation?▼

Static analysis for spec validation checks inputs, outputs, failure modes, and side effects of your implemented system directly against L3 and L2 specs without executing the code.

How do I map test results to spec elements?▼

You map test results to spec elements by generating audit matrices that compare test-suite outcomes against declared spec requirements, producing a structured report of coverage gaps.

Can I validate runtime behavior against specs using live probes?▼

Yes, you can validate runtime behavior by optionally starting the system, firing exact or probing requests, and checking real responses against the spec corpus requirements.

Does validation require a supporting implementation plan file?▼

Yes, validation requires loading context from supporting-docs/implementation-plan.yaml to guide the structured Phase 1 through Phase 4 workflow and write the validation report.

What is the best way to generate a validation report for Forge specs?▼

The best way to generate a validation report is running a read-only validation workflow that writes structured findings to supporting-docs/validation-report.md within the spec directory.