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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write ad variants that each test one idea, within platform limits and supported claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.