orient

To analyze project state for parallelizable work streams, you need to review git repository status, documentation, and task boards. This identifies ready tasks and maps dependencies to determine independent work paths for efficient agent dispatch.

The best way to identify ready and blocked tasks is by reviewing task boards like Beads. Checking task queue status alongside git history reveals the critical path and highlights which tasks are unblocked for immediate execution.

Dependency mapping determines critical path tasks by analyzing git repository structure and task board queues. It isolates independent work streams from sequential ones, ensuring orchestrator agents only execute parallelizable tasks without hitting blockers.

Yes, project orientation tools assess codebase health and documentation together by combining git repository analysis with documentation review. This provides a comprehensive overview of project status, ensuring agents have necessary context before dispatch.

You need a task board like Beads to fully scope independent work streams. While git analysis provides repository context, reviewing the task queue identifies specific ready and blocked tasks required for accurate parallel execution planning.