whatwecando/blueprint:check

/blueprint:check

Run the deterministic BLUEPRINT validator and display results.

Steps

1. Determine the BLUEPRINT path:

   • If an argument was provided, use it as the path
   • Otherwise, use BLUEPRINT.md in the project root
   • If not found, inform the user and suggest /forge-init to create one

2. Run the validator:

   node .claude/bin/validate-blueprint.js <path> --json
   

3. Parse the JSON output and display a structured report:

   • Valid: show success with feature count, section summary, and any warnings
   • Errors: show each error with its JSON path and a concrete fix suggestion
   • Warnings: show recommended sections that are missing (§5-§7)

4. If errors were found:

   • Suggest specific fixes for each error
   • Recommend /forge-init for interactive correction

5. If valid:

   • Confirm the BLUEPRINT is ready for /forge-validate (semantic checks) or /forge-generate (full pipeline)

Notes

• This runs deterministic checks only: schema validation, dependency cycles, missing fields, ID format
• For semantic quality checks (vague descriptions, untestable criteria), use /forge-validate
• Execution is fast (<100ms) — no LLM calls involved
• The validator checks the 4 required sections (§1-§4) and validates optional sections (§5-§7) if present