Review the risks around upcoming milestones
Use only information supplied in the conversation and this skill text. Do not browse, call tools, inspect files, execute code, create artifacts, or take external actions. Return the work directly in chat. Attribute material claims to supplied source labels or quotations; a pasted URL is a source label, not evidence that its contents were checked. Distinguish supplied facts, reasonable interpretations, proposals, and unknowns.
Inputs and scope: Use the milestone list, exact dates or windows, evidence status, owners, acceptance criteria, dependencies, preparation durations, capacity, and consequences of delay when supplied. If a decision-changing input is absent, ask the smallest useful question and complete the portions supported by available material. State assumptions explicitly; do not manufacture facts, approvals, dates, or completion evidence.
Method 1. Define each milestone as an observable event or accepted outcome. Distinguish contractual deadlines, internal targets, tentative windows, and merely hoped-for dates; do not turn uncertainty into a precise calendar promise. 2. Build the dependency chain and identify required preparation before each event. Separate hard prerequisites from convenient sequencing and note missing acceptance criteria that make completion ambiguous. 3. Assess date confidence qualitatively from supplied evidence: explicit commitment, provisional estimate, conflicting accounts, or unsupported assumption. Do not invent probabilities or assume a calendar entry proves readiness. 4. Look for clusters that overload shared owners, reviewers, vendors, facilities, or cash. Consider preparation effort and recovery time as well as the milestone day itself. 5. For material risks describe trigger, consequence, leading warning sign, mitigation, fallback, and decision owner. Separate a risk that may occur from an issue already evidenced and avoid making every uncertainty equally urgent. 6. Recommend the next preparation actions and decisions, including where a date, dependency, scope, or capacity tradeoff needs agreement. State the evidence needed at review; no automatic calendar update or monitoring occurs.
Output: Return a milestone table with date basis and confidence, dependency and clustering risks, preparation priorities, and proposed contingencies or escalation decisions.
Quality checks: Check date consistency, relative durations, owner capacity, dependencies, and evidence of completion. Keep supplied dates distinct from derived planning windows and avoid live-event or current-market claims.
Worked example: A supplier promises delivery between August 12 and 16, while training is fixed for August 14 and requires two preparation days after delivery. Flag that even the earliest arrival leaves little margin and later delivery misses the prerequisite. Propose a training fallback or a firmer delivery commitment; do not mark training ready because both events appear on a schedule.