Skip to content
Back to skills

Prerequisite Planning

ASecurity

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

  • 417 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
researchgo

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill prerequisite-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prerequisite Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prerequisite Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-prerequisite-planning/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-prerequisite-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prerequisite-planning
description: "Identify obstacles blocking direct achievement and design intermediate objectives to overcome each"
version: 1.0.0
category: experiment-execution
type: strategy
used-by: implementation-planning
sops:
  - obstacle-identification
  - intermediate-objective-design
tactics:
  - task-decomposition
---

# 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

| 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

Files in this skill

  • SKILL.md1.7 KB
  • prompt.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.