OpenParable
Skip to content
← Back to skills

Prerequisite Planning

Productivity
prerequisite-planning

Prerequisite Planning 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.

Identify obstacles blocking direct achievement and design intermediate objectives to overcome each

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/prerequisite-planning/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/prerequisite-planning, 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: Prerequisite Planning

Key Question: What obstacles are in the way?

Methodology

Theory of Constraints (TOC) Prerequisite Tree + Transition Tree:

  1. Prerequisite Tree (PRT) — identify obstacles preventing direct achievement of the objective
  2. Intermediate Objectives (IOs) — design actions that overcome each obstacle
  3. Transition Tree — sequence IOs into executable steps with cause-effect logic

Execution Flow

[Objective from experiment design]
    → obstacle-identification (PRT)
        → intermediate-objective-design (IOs for each obstacle)
            → [sequence IOs by dependency]
                → OUTPUT: ordered list of IOs with obstacle-IO mapping

Budget Gate

StepMax BudgetOutput
Obstacle identification10%Complete obstacle list
IO design10%IO for each obstacle

Key Decisions

  • If an obstacle cannot be overcome: escalate to experiment redesign (return to Campaign 3)
  • If multiple IOs address same obstacle: choose simplest (Occam's razor)
  • If IOs create new obstacles: recurse (but limit depth to 3 levels)

Integration with Critical Path

Obstacles identified here feed back into the critical path:

  • Each IO becomes an activity in the network
  • IO dependencies become edges in the activity graph
  • This ensures the plan accounts for real-world blockers, not just ideal-path tasks

Available Tactics

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

TacticWhen to use
task-decompositionOrchestrate the breakdown of experiment design into sequenced, estimated, and formatted task plan

Available SOPs

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

SOPWhen to use
intermediate-objective-designDesign intermediate objectives to overcome each identified obstacle
obstacle-identificationTOC Prerequisite Tree — list obstacles preventing direct achievement of the objective