majiayu000 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
| Blocker | Blocked Tasks | Resolution |
|---|---|---|
| No GDD | All implementation | Create with /design-game |
| No assets | Visual features | Generate with asset-generator |
| Assets not integrated | Rendering | Run integration-assistant |
| No handles | Asset usage in code | Create src/assets.rs |
| Build fails | All testing | Fix compilation errors |
| Module not in lib.rs | Feature doesn't run | Add mod declaration |
| Not in update() | Feature doesn't update | Add update call |
| Not in render() | Feature doesn't display | Add render call |
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:
- Design → Implementation
- Generation → Integration
- Integration → Usage
- Code → Test
- 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.