Prerequisite Planning
Productivityprerequisite-planningPrerequisite 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
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
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:
- Prerequisite Tree (PRT) — identify obstacles preventing direct achievement of the objective
- Intermediate Objectives (IOs) — design actions that overcome each obstacle
- 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
| Step | Max Budget | Output |
|---|---|---|
| Obstacle identification | 10% | Complete obstacle list |
| IO design | 10% | 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.
| Tactic | When to use |
|---|---|
| task-decomposition | Orchestrate 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.
| SOP | When to use |
|---|---|
| intermediate-objective-design | Design intermediate objectives to overcome each identified obstacle |
| obstacle-identification | TOC Prerequisite Tree — list obstacles preventing direct achievement of the objective |