piyaz_analyze
Analyze the project dependency graph.
piyaz_analyze
Analyze the project dependency graph. All variants slim; lead with these for status, prioritization, 'what's next', 'what's stuck'. critical_path=longest dep chain (project bottleneck, minimum duration). Lead with this on continue / resume / 'guide me forward'; the most important type for prioritization. ready=planned tasks with all effective deps done (only status='planned' reaches this state; drafts with satisfied deps surface as plannable, not ready). Pick from ready ∩ critical_path for the highest-impact unblocked work. plannable=draft tasks with description + criteria, ready for planning. Fall back here when nothing is ready to code. blocked=tasks waiting on unfinished deps with blocker details. downstream=transitive dependents of one task; impact analysis before status change, refinement, or cancellation.
Actions
| Action | Purpose |
|---|---|
ready | planned tasks with all deps done (drafts with deps satisfied surface as plannable, not ready) |
blocked | waiting tasks with blocker details |
downstream | transitive dependents (impact analysis before changes) |
critical_path | longest dep chain (project bottleneck) |
plannable | draft tasks with description+criteria, ready for planning |
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
type | "ready" | "blocked" | "downstream" | "critical_path" | "plannable" | Yes | ready=planned tasks with all deps done (drafts with deps satisfied surface as plannable, not ready). blocked=waiting tasks with blocker details. downstream=transitive dependents (impact analysis before changes). critical_path=longest dep chain (project bottleneck). plannable=draft tasks with description+criteria, ready for planning. |
projectId | string (uuid) | No | Project UUID. Required for ready/blocked/critical_path/plannable. |
taskId | string (uuid) | No | Task UUID. Required for 'downstream'. |