agentleFS
45ck45ck/business-analysis-skills/.agents/skills/constraint-detector/SKILL.md

constraint-detector

Skill28 starsChanged 8 months agoMITView on GitHub

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer short, testable statements over long prose.

    line 49
  2. Distinctive:

    Do not invent stakeholder intent.

    line 54
  3. Distinctive:

    Do not convert preferences into mandatory requirements without evidence.

    line 55
  4. Distinctive:

    Do not hide unresolved ambiguity behind polished wording.

    line 56
  5. Distinctive:

    Do not collapse functional, non-functional, and business rule concerns into one blob.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

constraint-detector

Purpose

Identify hard boundaries that shape the solution space: technical, legal, organizational, financial, time, platform, and integration constraints.

Trigger this skill when

  • A team is picking solutions before checking boundaries.
  • The brief references mandated tools, vendors, deadlines, standards, or environments.
  • Feasibility or architecture work is starting.

Expected inputs

  • requirements
  • project brief
  • platform notes
  • org policies
  • integration context

Deliverables

  • constraint register
  • hard vs soft constraints split
  • design impact notes

Operating procedure

  1. Extract all explicit restrictions.
  2. Infer likely constraints from platform, regulation, team capability, procurement, environment, and integration context.
  3. Separate hard constraints from preferences and assumptions.
  4. Note which design options each hard constraint removes or weakens.

Quality gates

  • Preferences are not mislabeled as hard constraints.
  • Each constraint names its source where possible.
  • Design implications are captured.

Handoff targets

  • requirements-prioritizer
  • architecture-option-review if present
  • definition-of-done-drafter

Output style

  • Be explicit about uncertainty.
  • Prefer short, testable statements over long prose.
  • Surface risk and ambiguity instead of guessing.
  • Separate facts, assumptions, constraints, and open questions.

Failure modes to avoid

  • Do not invent stakeholder intent.
  • Do not convert preferences into mandatory requirements without evidence.
  • Do not hide unresolved ambiguity behind polished wording.
  • Do not collapse functional, non-functional, and business rule concerns into one blob.

Minimum output skeleton

## Summary
## Findings
## Structured outputs
## Assumptions
## Constraints
## Open questions
## Recommended next skill

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.