Prompt Optimizer
Diagnose prompt quality, pick the right framework (RACE, AIDA, SWOT, etc.), gather missing info, and produce an AI-ready prompt instantly.
Planning, coordination, estimates, risk, standups, and delivery operations.
Diagnose prompt quality, pick the right framework (RACE, AIDA, SWOT, etc.), gather missing info, and produce an AI-ready prompt instantly.
Reviews authorized finance evidence for exceptions, reconciliations, receivables priorities, and cash risks without posting transactions.
Synthesizes company signals into a focused operating brief, decision queue, and accountable follow-through plan.
Launch an Attendee meeting bot, capture the recording, and deliver a timestamped transcript with operator-ready next actions.
Build and run a 13-week direct-method cash flow forecast: opening cash from the bank, receipts by customer and aging using the user's own collection history, disbursements (payroll calendar, rent, vendor payment runs, taxes, debt service, capex), minimum cash buffer and covenant checks, weekly roll-forward with variance to actual, and scenarios and levers such as collections pushes, payment timing, and credit line draws. Includes a Python script that rolls weekly balances from dated flows and flags weeks below a minimum. Use when asked for a 13-week cash forecast, weekly cash flow, runway in weeks, liquidity planning, or a covenant check. Do not use for an annual operating budget (build-operating-budget), month-end close (run-month-end-close), or legal or insolvency advice.
Build and run a 13-week direct-method cash flow forecast: opening cash from the bank, receipts by customer and aging using the user's own collection history, disbursements (payroll calendar, rent, vendor payment runs, taxes, debt service, capex), minimum cash buffer and covenant checks, weekly roll-forward with variance to actual, and scenarios and levers such as collections pushes, payment timing, and credit line draws. Includes a Python script that rolls weekly balances from dated flows and flags weeks below a minimum. Use when asked for a 13-week cash forecast, weekly cash flow, runway in weeks, liquidity planning, or a covenant check. Do not use for an annual operating budget (build-operating-budget), month-end close (run-month-end-close), or legal or insolvency advice.
Diagnose a burndown or burnup from the user's own sprint, release, or project data plus team notes. Separates gross burn from scope change, fits velocity overall and recently, projects a finish with an explicit range, computes the velocity required to hit the date, classifies the curve pattern (flat then cliff, scope drift, steady shortfall, late batch landing, stale sizing), links each pattern to evidence in blockers, work in progress, carryover, and interruptions, and ends with ranked recovery options (cut scope, extend, add capacity, unblock, reduce work in progress) with trade-offs. Use when someone asks why we are behind, whether we will make the sprint or release date, what the burndown is telling us, how much scope to cut, or what the recovery options are. Do not use for turning raw standup updates into a summary (use standup-digest), for scoring risks (use risk-register), or for pricing a requested addition (use scope-change-brief).
Reviews burndown data and project notes to identify delivery risks, scope drift, blockers, and recovery options.
Build and interpret cohort retention analysis from a CSV of customers, subscriptions, or transactions, with a bundled Python script: a logo retention triangle and, when revenue is present, gross revenue retention (GRR, capped at 100%, excludes expansion) and net revenue retention (NRR, includes expansion) by cohort, plus trailing-twelve-month NRR. Handles reactivations, mid-month starts, plan changes, and small cohorts, then reads curves for flattening, cohort-over-cohort improvement, and segment differences. Use when asked for a cohort analysis, retention curve or triangle, NRR or GRR, or whether newer customers retain better. Do not use for churn risk on named accounts (churn-risk-review), a customer health score (design-customer-health-score), or unit economics (model-unit-economics).
Build and interpret cohort retention analysis from a CSV of customers, subscriptions, or transactions, with a bundled Python script: a logo retention triangle and, when revenue is present, gross revenue retention (GRR, capped at 100%, excludes expansion) and net revenue retention (NRR, includes expansion) by cohort, plus trailing-twelve-month NRR. Handles reactivations, mid-month starts, plan changes, and small cohorts, then reads curves for flattening, cohort-over-cohort improvement, and segment differences. Use when asked for a cohort analysis, retention curve or triangle, NRR or GRR, or whether newer customers retain better. Do not use for churn risk on named accounts (churn-risk-review), a customer health score (design-customer-health-score), or unit economics (model-unit-economics).
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).
Maps delivery dependencies across teams, systems, vendors, and decision points with critical path callouts.
Extract a faithful meeting record from a transcript, recording, rough notes, or chat log: attendees and date, decisions, action items, unresolved questions, and source gaps. Use for meeting notes, decision logs, handoffs, or follow-up summaries. Do not use for meeting preparation, invented consensus, or silently assigning owners and due dates.
Extract a faithful meeting record from a transcript, recording, rough notes, or chat log: attendees and date, decisions, action items, unresolved questions, and source gaps. Use for meeting notes, decision logs, handoffs, or follow-up summaries. Do not use for meeting preparation, invented consensus, or silently assigning owners and due dates.
Run, document, and speed up a month-end close for a small-to-mid-size company: a business-day close calendar (BD-3 to BD+10) with owners, pre-close and cutoff procedures, the core checklist (cash and bank reconciliations, AR and AP subledger ties, revenue recognition review, accruals, prepaids, fixed assets, payroll, intercompany, deferred revenue roll-forward, inventory), journal entry review standards, balance-sheet reconciliations, flux analysis against user-set thresholds, sign-off and lock, and a faster-close plan. Use when asked to build a close checklist or calendar, reconcile accounts, review journal entries, run a flux review, or shorten the close. Do not use to explain one budget variance (budget-variance-explainer), for a 13-week cash forecast (build-cash-forecast), or for accounting-standard opinions.
Run, document, and speed up a month-end close for a small-to-mid-size company: a business-day close calendar (BD-3 to BD+10) with owners, pre-close and cutoff procedures, the core checklist (cash and bank reconciliations, AR and AP subledger ties, revenue recognition review, accruals, prepaids, fixed assets, payroll, intercompany, deferred revenue roll-forward, inventory), journal entry review standards, balance-sheet reconciliations, flux analysis against user-set thresholds, sign-off and lock, and a faster-close plan. Use when asked to build a close checklist or calendar, reconcile accounts, review journal entries, run a flux review, or shorten the close. Do not use to explain one budget variance (budget-variance-explainer), for a 13-week cash forecast (build-cash-forecast), or for accounting-standard opinions.
Prepare source-backed nonprofit development, grant, reporting, impact, leadership and staff deliverables through the fifteen-capability Relay Nonprofit Pack. Use approved tenant configuration and immutable evidence; preserve independent review and external-action boundaries.
Prepare source-backed nonprofit development, grant, reporting, impact, leadership and staff deliverables through the fifteen-capability Relay Nonprofit Pack. Use approved tenant configuration and immutable evidence; preserve independent review and external-action boundaries.
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).
Builds and updates project risk registers with severity, probability, owner, mitigation, and trigger conditions.
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).
Turns a requested scope change into impact, alternatives, cost, timeline, and approval language.
Convert raw team updates (standup posts, chat threads, transcripts, ticket comments) into a concise, attributed digest. Classifies every statement as done, in progress, planned, blocked, decision, question, or risk signal; keeps only what changes someone's work; merges duplicates; ages each blocker and names who can unblock it; records decisions with decider and date; turns commitments into actions with owner and due date; flags vague, missing, contradictory, or stale updates as follow-up questions instead of guessing; compares against the previous digest for carryover; and sizes the output for the audience. Use when someone asks to summarize standup updates, write a daily or weekly team digest, pull blockers and decisions out of a thread, or produce a status roll-up from notes. Do not use for diagnosing a burndown (use burndown-diagnosis), extracting outcomes from a full meeting recording (use extract-meeting-outcomes), or maintaining a risk log (use risk-register).
Converts raw team updates into a concise digest with progress, blockers, decisions, owners, and next actions.