Skip to content
Automation
Skill

/boundary-condition-specification

SOP: Specify the boundary conditions under which a hypothesis holds

From plugin
de-anthropocentric-research-engine
393200 skills
Install
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill boundary-condition-specification --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/boundary-condition-specification

Context preview

The summary Claude sees to decide when to auto-load this skill.

SOP: Specify the boundary conditions under which a hypothesis holds

SKILL.md

boundary-condition-specification.SKILL.md
name: boundary-condition-specification
description: 'SOP: Specify the boundary conditions under which a hypothesis holds'
version: 1.0.0
category: hypothesis-formation
type: sop
campaign: hypothesis-formulation
input: Hypothesis draft (with statement + variables + mechanism)
output: Boundary condition list (temporal/spatial/population/conditional/exclusions)
dependencies:
  skills:
  - subagent-spawning

Boundary Condition Specification

Systematically identify the preconditions required for a hypothesis to hold, preventing overgeneralization.

HARD-GATE

<HARD-GATE> Preconditions (all must hold before starting): 1. At least 1 hypothesis draft is available (with statement and mechanism) 2. The hypothesis involves identifiable entities, time, or context

Not satisfied → stop and return error: hypothesis draft incomplete, cannot determine boundary conditions. </HARD-GATE>

Pipeline

1. Precondition check: verify completeness of the hypothesis draft 2. Temporal boundary: in what time period/historical era does the hypothesis hold? Is there a time sensitivity? 3. Spatial boundary: within what geographic/cultural/organizational scope does the hypothesis hold? 4. Population boundary: to what kind of subjects does the hypothesis apply (populations, species, system types)? 5. Conditional boundary: what preconditions are required for the hypothesis to hold (technical, institutional, environmental)? 6. Exclusion conditions: explicitly list the situations where the hypothesis does not apply 7. Output structured boundary condition list

Output Format

{
  "hypothesis_id": "H1 (or hypothesis statement snippet)",
  "boundary_conditions": {
    "temporal": "Time period or duration constraints",
    "spatial": "Geographic, cultural, or organizational scope",
    "population": "Subject type, sample characteristics",
    "conditional": ["Prerequisite condition 1", "Prerequisite condition 2"],
    "exclusions": ["Situation where hypothesis does NOT apply"]
  },
  "generalizability": "narrow | moderate | broad",
  "notes": "Any additional caveats"
}

Each hypothesis draft yields 1 boundary condition object. </output>

Read more
Ships withde-anthropocentric-research-engine

The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.

Get the whole plugin
Stats
393
Stars
34
Forks
Active
Maintenance
HTML
Language
Apache-2.0
License
19h ago
Last commit
6mo ago
Created

Repo: yogsoth-ai/de-anthropocentric-research-engine