constraint-action

Identify and classify constraints as hard, soft, or unknown into guardrails.

37|5|Updated Nov 18, 2025

Search Tags:#compliance #constraints #guardrails #risk #non-negotiables

Ready to run

npx skills add https://github.com/BellaBe/lean-os --skill constraint-action

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: constraint-action
Source: https://github.com/BellaBe/lean-os/tree/main/.claude/skills/action-constrain
Command: npx skills add https://github.com/BellaBe/lean-os --skill constraint-action

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Makes hard/non-negotiable constraints visible to downstream work.

Core Features & Use Cases

Constraint extraction: Hard vs soft constraints.
Guardrails: Actionable guardrails.
Conflict surface: Surface conflicts needing decisions.

Quick Start

Provide constraints; returns guardrails and conflicts.

Frequently Asked Questions about constraint-action

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

FAQPage Schema

How do I identify hard vs soft constraints in my project requirements?▼

Hard constraints are non-negotiable limits that cannot be violated; soft constraints are flexible guidelines. Identifying them early clarifies which requirements are absolute blockers versus trade-offs, preventing downstream rework when conflicts surface during planning or execution.

What's the best way to surface compliance and risk constraints before they cause violations?▼

Extract constraints explicitly from compliance requirements, guardrails, and risk assessments, then translate them into actionable rules. Surfacing them upfront prevents violations in downstream actions and flags conflicts that need human decisions.

How do I handle conflicting constraints when gathering requirements?▼

Conflicting constraints surface when hard limits clash or soft guidelines contradict. Classify each constraint's type and source, then surface conflicts to stakeholders immediately so decisions can be made before execution proceeds.

Can I use constraint-action to prevent non-negotiable limits from being violated in planning?▼

Yes. By identifying and classifying hard, soft, and unknown constraints upfront, you create guardrails that guide planning and execution decisions, preventing actions that violate non-negotiable requirements.

What sources should I check when discovering hard-limit constraints?▼

Constraints come from compliance rules, regulatory requirements, risk frameworks, stakeholder non-negotiables, and technical limits. Identifying their source helps classify their strength and ensures guardrails address the right scope.

When should I classify a constraint as unknown rather than soft?▼

Classify constraints as unknown when their enforcement level is unclear—neither explicitly hard nor confirmed soft. Unknown constraints require discovery and stakeholder clarification before guardrails can be reliably applied.