concept-critic

Critique concept definitions against eight concept-design criteria.

1|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/igorrazvodovsky/pattern-playground --skill concept-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: concept-critic
Source: https://github.com/igorrazvodovsky/pattern-playground/tree/main/.claude/skills/concept-critic
Command: npx skills add https://github.com/igorrazvodovsky/pattern-playground --skill concept-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the problem of vague, poorly-reasoned, or flawed concept designs by applying a demanding, systematic critique methodology. It ensures concepts are robust, well-defined, and meet high intellectual standards before implementation, saving time and reducing complexity in development.

Core Features & Use Cases

  • Structured Validation: Systematically checks concepts against 8 essential criteria (user-facing, semantic, independent, behavioral, purposive, end-to-end, familiar, reusable).
  • Operational Principle Scrutiny: Rigorously evaluates "if...then" statements for specificity, value, and logical consistency.
  • Anti-Pattern Identification: Detects common design flaws like multi-purpose concepts, incomplete functionality, and hidden dependencies.
  • Use Case: Before a major feature development, use this skill to validate the core concept design, ensuring it's sound and avoids costly rework later.

Quick Start

Critique this concept design for a new "User Profile" feature, focusing on its operational principle and adherence to the 8 criteria.

Frequently Asked Questions about concept-critic

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

FAQPage Schema
How do I validate a concept design against quality criteria?

Concept validation systematically checks your design against eight criteria: user-facing, semantic, independent, behavioral, purposive, end-to-end, familiar, and reusable. This structured approach identifies flaws early, ensuring robustness before implementation and reducing costly rework later.

What makes a concept design flawed, and how do I spot design flaws?

Common concept-design flaws include multi-purpose definitions, incomplete functionality, and hidden dependencies. Rigorous critique detects these anti-patterns through operational-principle scrutiny and structural validation, helping you strengthen definitions before development begins.

How do I evaluate if my concept's operational principle is sound?

Operational-principle critique rigorously examines 'if...then' statements for specificity, logical consistency, and delivered value. This evaluation ensures your concept's core logic is clear, actionable, and free of ambiguity or hidden assumptions.

When should I critique a concept design in the product development cycle?

Critique concepts before major feature development begins. Validating core concept design early prevents architectural misalignment, reduces complexity, and saves time by catching design issues before implementation investment.

Can concept critique help with software architecture decisions?

Yes. Concept critique applies to architectural decisions by validating whether design concepts are independent, semantically clear, and end-to-end functional. This ensures architecture meets both quality standards and reusability requirements.