Works with the AI tools you already use

CCCGGVWM+14 more

Project Phase Manager — Critical Path, Handoffs & Go/No-Go Gates

Name: Project Phase Manager — Critical Path, Handoffs & Go/No-Go Gates
Price: 12 USD
Availability: InStock
Author: Agensi

by Vivek K

Turns a project goal into a phase-gated plan: deliverables, dependencies, critical path, handoffs, risks, GO / GO-WITH-CONDITIONS / HOLD gates, and a stakeholder-ready status snapshot.

$12

30-day refund guarantee

Secure checkout via Stripe

0 installsSecurity scanned

See it in action

You say

Project: City of Redrock — AquaMeter residential water-meter photo-read pilot Timeline: week 5 of 10 · pilot go-live before city council vote 15 Nov 2026 Team roles: City PM, Utility SME, Mobile Eng, Backend Eng, Data Analyst, Field Ops Lead, City Legal (external) Constraints: offline-first capture · no cloud PII until Legal signs · city SSO for ops dashboard

Status now:

Discovery + success metrics: done
Privacy review draft: done · Legal sign-off still open
Backend ingestion API: done
Offline mobile capture app: ~70% in progress
Field Ops labeled meter-image corpus: not delivered → OCR pipeline blocked
Ops dashboard: not started (SSO client id pending)
Training + 3-neighborhood pilot + council readout: not started

Ask: phase plan, critical path, handoffs, risks, go/no-go gates, executive status.

Your agent does

Project Phase Plan

1. Plan Summary

| Field | Value | |---|---| | Project | City of Redrock — AquaMeter photo-read pilot | | Phase count | 5 | | Timeline | 10 weeks; hard pilot go-live before council vote 15 Nov 2026 | | Critical path | Discovery → Legal privacy sign-off → Offline mobile app → Image corpus → OCR pipeline → Pilot | Overall status | Off track |

2. Phase Plan (excerpt)

| Phase | Name | Key deliverables | Status | Critical path? | |---|---|---|---|---| | P1 | Foundations | Discovery notes, success metrics, privacy draft | COMPLETE (Legal signature still open) | Y | P2 | Capture & ingest | Offline tablet app, backend ingestion API | IN-PROGRESS (API done, mobile ~70%) | Yes | P3 | Read intelligence | Field Ops image corpus, OCR confidence pipeline | BLOCKED (no corpus) | Yes | | P4 | Ops readiness | SSO exception dashboard, playbook, training | NOT-STARTED | Limited slack | | P5 | Pilot & readout | 3-neighborhood go-live, council metrics readout | NOT-STARTED | Yes |

3. Critical path & slack

Critical path (any slip moves 15 Nov): Legal sign-off → mobile capture → Field Ops corpus → OCR → pilot → council readout

Slack (can slip only if critical path holds): backend API (already done), dashboard start, playbook polish.

4. Dependency graph (excerpt)

Field Ops image corpus → OCR pipeline
Legal sign-off → cloud PII pilot traffic
OCR outputs + SSO client id → ops dashboard UAT
Mobile app + OCR + training → 3-neighborhood go-live → council readout

5. Handoff matrix (excerpt)

| From | To | What | Boundary | |---|---|---|---| | Field Ops Lead | Data Analyst | ≥200 labeled meter images | Unblocks P3 | | Data Analyst | Backend / Utility SME | OCR with confidence scores | P3 → P4 | | City Legal | City PM / Eng | Signed data-handling memo | Before cloud pilot | | Field Ops + Utility SME | City PM | Training complete + playbook | P4 → P5 |

6. Phase gates

| Boundary | Verdict | Why | |---|---|---| | P1 → P2 | GO | Discovery + metrics + privacy draft complete | | P2 → P3 | GO-WITH-CONDITIONS | Finish offline capture + sync this week | | P3 → P4 | HOLD | Critical dependency unmet: image corpus not delivered | | P4 → P5 | HOLD | Not reached; also blocked by Legal sign-off for cloud PII |

Gate rule applied: missing exit deliverable / unmet critical dependency → HOLD (not a soft “maybe”).

7. Risk register (top)

| Risk | Likelihood | Impact | Mitigation | |---|---|---|---| | Field Ops corpus never arrives | High | High | 5-day photo blitz; accept 100 images to unblock if 200 slips | | Legal sign-off slips past code-complete | High | High | Escalate this week; define on-device-only fallback | | 15 Nov council date immovable | High | High | Pre-agree one-neighborhood cut if either blocker slips >1 week |

8. Executive status snapshot

| Phase | Light | |---|---| | P1 Foundations | Amber | | P2 Capture & ingest | Amber | | P3 Read intelligence | Red (blocked) | | P4 Ops readiness | — | | P5 Pilot & readout | — |

Stakeholder summary (30 seconds): AquaMeter is off track at week 5 of 10. Ingest API is done and mobile capture is nearly there, but OCR is blocked on missing Field Ops photos and City Legal has not signed the cloud PII memo. Both sit on the path to the 15 Nov council-tied pilot. This week: (1) Field Ops photo blitz, (2) Legal escalation with a dated decision, (3) finish offline app, (4) decide scope cut if either blocker slips.

9. Project Phase JSON

Includes overall_status "Off track", phase statuses, critical_path[], handoffs[], gates with GO / GO-WITH-CONDITIONS / HOLD, risks, executive_summary, and labeled assumptions — ready to paste into tickets or status docs.

What you get

Structure a multi-week delivery into 3–6 phases with ownersFind the critical path and what has slackDecide GO / HOLD at a phase boundary with clear criteriaProduce a 30-second executive status with traffic lightsSurface external blockers (vendor, legal, client content) on the timeline

About this skill

The problem

Flat task lists hide the critical path and which delays actually move the end date.
Phase handoffs fail when “done” is vague and no one owns the boundary.
Stakeholders need a clear on-track / at-risk / off-track read — not a 40-row board dump.

What it does

Groups work into sequential phases with deliverables and owners.
Maps dependencies and identifies the critical path vs slack items.
Defines a handoff matrix (from / to / what / acceptance) at each boundary.
Sets phase gates: GO, GO-WITH-CONDITIONS, or HOLD using explicit rules.
Produces a risk register and an executive status snapshot with traffic lights.

Frameworks & tools

Works for product, agency, municipal, and internal delivery projects — stack-agnostic.
Uses the goals, deliverables, team roles, and status you provide (mid-project or greenfield).
Outputs stay in markdown + JSON for copy into docs, decks, or tickets — no PM SaaS required.

Why this beats prompting it yourself

Deterministic gate rules (missing critical dependency → HOLD, not a soft “maybe”).
Critical path vs slack called out explicitly.
Handoffs and acceptance criteria reduce dropped work at boundaries.
Anti-fabrication: assumptions labeled; no invented owners or fake % complete.
Stakeholder summary designed for a 30-second read.