prerequisite-planning
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/prerequisite-planning**Key Question**: What obstacles are in the way?
SKILL.md
.github/skills/prerequisite-planningView on GitHub ↗
---
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
More from yogsoth-ai/de-anthropocentric-research-engine
- abductive-hypothesis-generationStrategy: 面对异常的最佳解释推理
- ablation-brainstormRemove components one by one, observe system changes to reveal hidden dependencies and generate ideas from structural gaps.
- ablation-component-mappingMap system architecture to ablatable units for ablation studies
- ablation-designDesign ablation studies to isolate component contributions in ML systems
- ablation-executionRemove components one by one from a system, record the response/impact of each removal.
- abp-vulnerability-classificationClassify assumptions on 2 axes — load-bearing (how much conclusion depends on it) × vulnerable (how likely to be false). Focuses attention on High-Load × High-Vulnerable quadrant.
- abstraction-extractionExtract abstract principles from concrete domain cases. Strips domain-specific details to reveal transferable mechanisms.
- abstraction-ladderPerform bisociation at multiple abstraction levels
- abstraction-ladderingMove between concrete and abstract framings — 3 levels up (Why?) and 3 levels down (How?) to find the most productive research level.
- abstraction-to-designAbstract biological principle to design principle. Bridge from biology to engineering.