Skip to content
Back to skills

Constraint Classification

ASecurity

Classify constraints into hard constraints, soft constraints, and assumptions.

  • 417 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added June 2, 2026
researchgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned June 2, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill constraint-classification --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Constraint Classification?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Constraint Classification
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-constraint-classification/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-constraint-classification)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: constraint-classification
description: Classify constraints into hard constraints, soft constraints, and assumptions.
execution: subagent
prompt: ./prompt.md
input: constraints[]
used-by: feasibility-assessment
---

# Constraint Classification

Take a list of identified constraints and classify each into one of three categories: hard constraints (immovable, must be accepted), soft constraints (can be worked around or mitigated), and assumptions (unvalidated beliefs that may or may not be real constraints).

## Execution

Spawns a subagent that:
1. Receives list of identified constraints
2. Evaluates each constraint against classification criteria
3. Assigns category with justification
4. Identifies which assumptions are most dangerous if wrong
5. Returns classified constraint inventory

## Why Subagent

Classification requires careful judgment about what is truly immovable vs. what merely appears so. A dedicated subagent can focus on this distinction without being biased by prior analysis.

## HARD-GATE

Output MUST include: all input constraints classified, at least one constraint in each category (hard/soft/assumption), and justification for each classification. Reject if any input constraint is missing from output.

Files in this skill

  • SKILL.md1.2 KB
  • prompt.md2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…