OpenParable
Skip to content
← Back to skills

Resource Constraint

Productivity
resource-constraint

Resource Constraint is an Agent Skill for productivity published in the yogsoth-ai/de-anthropocentric-research-engine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Are resources sufficient? — Quantify compute, data, time, human, and financial resource constraints

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/yogsoth-ai/de-anthropocentric-research-engine/blob/HEAD/skills/resource-constraint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/resource-constraint, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Strategy: Resource Constraint

Methodology

Systematic resource feasibility assessment:

  • Demand modeling: What does the experiment need?
  • Supply inventory: What do we actually have?
  • Gap analysis: Where does demand exceed supply?
  • Critical chain: Which resource constraints lie on the critical path?
  • Buffer sizing: How much slack do we need?

Resource categories:

CategoryExamples
ComputeGPU hours, CPU cores, memory, storage
DataTraining samples, labeled data, access rights
TimeCalendar time, researcher hours, review cycles
HumanExpertise, headcount, availability
FinancialBudget, cost per experiment, opportunity cost

Execution Flow

  1. Quantify Resources → call resource-quantification SOP

    • Input: experiment plan, resource inventory
    • Output: demand/supply/gap table per category
  2. Identify Critical Chain → call critical-chain-identification SOP

    • Input: task list with resource assignments
    • Output: critical chain with resource contention points
  3. Size Buffers → call buffer-sizing SOP

    • Input: critical chain, task duration estimates
    • Output: project/feeding/resource buffer recommendations
  4. Rank Sensitivity → invoke sensitivity-ranking tactic

    • Determine which resource gap is most binding
  5. Report → synthesize feasibility assessment

    • Go/No-Go/Conditional recommendation

Budget Gate

ResourceBudgetNotes
Subagent calls≤63 SOPs + synthesis
Iterations≤2Re-quantify if estimates change
Output size≤3000 tokensGap table + recommendation

Available Tactics

Optional, no fixed order; the final leaf is always a sop.

TacticWhen to use
sensitivity-rankingRank constraints by sensitivity — which ones most impact the outcome if they shift

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOPWhen to use
buffer-sizingCalculate project, feeding, and resource buffers — shared with implementation-planning
critical-chain-identificationIdentify the critical chain — longest path considering resource contention
resource-quantificationQuantify resource demand vs supply vs gap for each resource category