pm-pipeline

You can visualize your project processing pipeline by displaying items across five defined lifecycle stages: INBOX, DOCUMENTED, LINKED, UPDATED, and COMPLETE. This tracks work progress from initial intake to final completion.

Workflow queue commands allow you to advance, stall, add, or clear items within the processing pipeline. Operating the queue manually moves work through stages while surfacing health indicators to prevent processing bottlenecks.

Pipeline backlog reduction works by monitoring queue health and archiving completed items to surface bottlenecks. Advancing stalled items through the lifecycle stages reduces accumulated work and maintains steady flow.

Yes, you can enforce a specific lifecycle for documentation and processing queues using defined stages: INBOX, DOCUMENTED, LINKED, UPDATED, and COMPLETE. Runtime configuration governs behavior to ensure items follow this exact progression.

The best way to monitor workflow bottlenecks in a processing pipeline is by running health checks that surface items stuck in specific stages. Visualizing the queue state highlights where documentation or linking tasks are causing delays.

You should clear items from an inbox queue when work is obsolete or duplicated, rather than advancing them through the documentation lifecycle. Clearing invalid entries reduces backlog size and maintains accurate pipeline health.