Prompt Optimizer
Diagnose prompt quality, pick the right framework (RACE, AIDA, SWOT, etc.), gather missing info, and produce an AI-ready prompt instantly.
Assets tagged with project-delivery.
Diagnose prompt quality, pick the right framework (RACE, AIDA, SWOT, etc.), gather missing info, and produce an AI-ready prompt instantly.
Launch an Attendee meeting bot, capture the recording, and deliver a timestamped transcript with operator-ready next actions.
Map the delivery dependencies of a project across teams, systems, vendors, and decision points, then call out the critical path. Inventories every input a deliverable needs, classifies each link (finish-to-start, data, access, decision, external), assigns a provider owner and a needed-by date, computes earliest and latest dates and float, finds the critical and near-critical chains, flags uncommitted and cyclic dependencies, and ranks them by how much a slip would move the end date. Use when someone asks what depends on what, who is blocking whom, what the critical path is, which handoffs or decisions put a date at risk, or for a dependency map before planning or a launch review. Do not use for scoring uncertain events as risks (use risk-register), for pricing a requested change (use scope-change-brief), or for diagnosing a sprint burndown (use burndown-diagnosis).
Build or update a project risk register that a team will actually use. Writes each risk as cause, event, and effect; scores probability and impact on a stated 1-5 scale with explicit band cut-offs; adds expected monetary exposure when amounts exist; names a single owner, a response type, a concrete mitigation, an observable trigger with a threshold and date, a residual score, and a review date; separates risks from issues, assumptions, and dependencies; and on updates reports new, changed, closed, and realized risks. Use when someone asks for a risk register, to log or rescore project risks, what could go wrong with a plan, which risks need an owner or a trigger, or how to refresh a stale register before a steering meeting. Do not use for mapping what depends on what (use dependency-map), for a live production incident (use coordinate-production-incident), or for pricing a scope request (use scope-change-brief).
Turn a requested scope change into a decision-ready brief. Restates the request as a testable delta against the baseline, separates the need from the proposed solution, estimates effort with ranges, converts hours to cost and schedule through the critical path, lists knock-on effects on dependencies, risks, quality, and other commitments, offers at least three alternatives (accept, trade, defer, reduce), recommends one, and drafts the approval language with named approver, price, date, and what is unchanged. Use when someone asks to evaluate a change request, add a feature mid-project, price a scope addition, show the impact of a client or stakeholder ask, or write approval wording for a change order. Do not use for scoring uncertain events (use risk-register), mapping handoffs (use dependency-map), reforecasting spend after approval (use budget-forecast), or defining deliverables for a new engagement (use match-engagement-deliverables).