Use when the user starts a cross-functional program, names milestones and owners, or asks what is at risk across workstreams and which gate can move.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this when the user starts a cross-functional program, names milestones and owners, or asks what is at risk across workstreams.
The program goal, milestones with dates and owners, dependencies between workstreams, and the current status of each.
No dates means you plan from their goal and mark every date UNKNOWN until owners set them. One workstream only means a simple plan, not padded governance.
Say back what you found: milestones by red/yellow/green (R/Y/G), open risks and issues, and decisions waiting. Never rebuild a plan they already run.
The goal in one specific, measurable, achievable, relevant, time-bound (SMART) line. Milestones with an owner and a date each. Dependencies mapped — what blocks what. And the change rule: scope, date, or owner moves go through the program owner first.
Risks, assumptions, issues, and dependencies (RAID):
Every entry carries an owner and a date, or it is not on the log. Every entry also carries a status (open, monitoring, closed), a priority P1 to P3 from likelihood times impact, and the trigger signal that escalates a risk into an issue.
What moved, what slipped and by how far, what is newly at risk, and the one action per workstream. One line per item, no preamble.
A phase moves only when its criteria clear with quoted evidence. Promote, hold, or kill — said plainly, with the reason.
Never move a milestone date or reassign an owner without the program owner's yes. Never report a risk closed on your own say-so.
Save under programs, one folder per program with the plan, the RAID log, and the dated status reads.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.