Dependency Chains

Understanding dependencies ensures tasks complete in the correct order.

Core Pipeline

Creative Vision → Game Design → Asset Specs → Assets → Integration → Implementation → Testing → Publishing

Each phase depends on the previous. Skipping phases causes problems.

Key Dependencies

Parallelizable Tasks

Can run simultaneously (no dependencies):

• Different asset types (textures, meshes, sounds)
• Different enemy types
• Different UI elements
• Analysis tasks (reviews, audits)

Sequential Requirements

Must run in order:

1. Design → Implementation
2. Generation → Integration
3. Integration → Usage
4. Code → Test
5. Pass tests → Release

Dependency Verification

Before starting a task, verify dependencies:

# Before feature using assets:
ls generated/meshes/feature*.obj
grep "feature" nether.toml
grep "FEATURE" src/assets.rs

# Before testing:
nether build

# Before rendering:
grep "mod feature" src/lib.rs

For detailed phase and feature chains, load the references.