substantive-critique

Critique design artifacts against evidence and produce prioritized findings.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Hellblazer/nexus --skill substantive-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: substantive-critique
Source: https://github.com/Hellblazer/nexus/tree/main/nx/skills/substantive-critique
Command: npx skills add https://github.com/Hellblazer/nexus --skill substantive-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers deep, constructive critique of architectural decisions, implementations, and documentation by matching artifacts against stated specs and evidence.

Core Features & Use Cases

  • Structured, evidence-based critique of design documents, specifications, and code artifacts.
  • Prioritized findings with actionable recommendations to improve quality and alignment with requirements.
  • Agent-based workflow that coordinates with the substantive-critic to surface gaps and ensure traceability to evidence.

Quick Start

Provide the artifact to review (design document, architecture, or specification) and request a substantive critique with prioritized findings.

Frequently Asked Questions about substantive-critique

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

FAQPage Schema
How do I critique architecture decisions against evidence?

To critique architecture decisions, you match artifacts like specifications and documentation against stated evidence to identify gaps, structural issues, and logical flaws, producing a prioritized critique report with actionable recommendations.

What is an evidence-based design document review?

An evidence-based design document review is a structured evaluation that matches specifications and architectural plans against traceable evidence to surface gaps, ensuring implementation plans align with actual requirements and quality standards.

How do I analyze specifications to find structural gaps?

You analyze specifications by performing a logical and structural analysis against gathered evidence, prioritizing the discovered gaps, and compiling them into a formal critique report to improve overall alignment.

Can I use this to review implementation plans and documentation?

Yes, you can use it to review implementation plans and documentation by applying an agent workflow that coordinates evidence gathering and structural analysis to ensure traceability and improve architectural quality.

What is the best way to generate actionable recommendations for design artifacts?

The best way to generate actionable recommendations is through a structured workflow that coordinates evidence gathering and logical analysis, prioritizing findings to directly improve architectural quality and requirement alignment.

When do I need a formal critique report for my architecture?

You need a formal critique report when you must validate architectural decisions, specifications, or implementation plans against evidence to ensure traceability, surface structural gaps, and improve alignment before proceeding.