lo-milestone-tracker — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited lo-milestone-tracker (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Tracks customer progress against defined adoption and lifecycle milestones. Flags blockers, measures time-to-milestone, and reports on adoption velocity. Operates across the full lifecycle, not just onboarding -- milestones exist from first login through mature expansion.
This is a tracking and alerting skill. It monitors progress against defined checkpoints and surfaces deviations. It does not define the milestones (that is a joint human exercise with the customer) or resolve blockers (that is human judgment).
| Type | Definition | Example |
|---|---|---|
| Activation | First meaningful use of the product | First workflow completed, first report generated |
| Adoption | Sustained use of core capabilities | 80% of team logging in weekly for 4 consecutive weeks |
| Depth | Advanced feature or use case adoption | Second use case live, API integration active |
| Outcome | Business result achieved through the product | 20% reduction in manual process time, measurable ROI |
| Expansion | Growth beyond initial scope | New department onboarded, tier upgrade, additional product |
Each account can have a milestone plan -- a set of defined milestones with target dates and success criteria. Plans can be:
For each account:
references/milestone-templates.md)For each active milestone:
Detection methods by milestone type:
| Detection Source | Milestones Detected |
|---|---|
| Product analytics | Activation (first use), Adoption (usage thresholds), Depth (feature usage) |
| CRM data | Expansion (opportunity stage), custom milestones logged by CSM |
| Customer confirmation | Outcome milestones (business results -- requires CSM to confirm with customer) |
| Condition | Action |
|---|---|
| Milestone at risk (due in 14 days, no progress) | Alert CSM: "Milestone [X] is due in [N] days with no progress detected" |
| Milestone overdue (past due, not complete) | Alert CSM + include in overdue report: "Milestone [X] is [N] days overdue" |
| Milestone completed ahead of schedule | Log completion, notify CSM (positive signal -- may indicate readiness for acceleration) |
| No milestone progress across the entire plan for 30+ days | Alert CSM: "No milestone progress for [account] in 30 days -- investigate stall" |
For completed milestones, track:
Per-account milestone status:
{
"account_id": "string",
"plan_type": "custom",
"milestones": [
{
"name": "Core workflow live",
"type": "activation",
"target_date": "2026-03-15",
"status": "completed",
"completed_date": "2026-03-10",
"days_ahead": 5
},
{
"name": "80% team adoption",
"type": "adoption",
"target_date": "2026-04-15",
"status": "on_track",
"progress_indicator": "62% of team active, trending up"
},
{
"name": "ROI measurement",
"type": "outcome",
"target_date": "2026-06-15",
"status": "not_started",
"progress_indicator": "Requires customer input -- not yet requested"
}
],
"overall_velocity": "ahead_of_plan",
"next_milestone_due": { "name": "80% team adoption", "due": "2026-04-15", "days_remaining": 36 }
}Portfolio milestone report (weekly):
| Decision Point | Context Provided | What the Human Decides |
|---|---|---|
| Milestone plan creation | Segment template, customer goals from onboarding | Which milestones to set, what timelines are realistic, how to define success criteria |
| At-risk milestone | Milestone details, progress data, last touchpoint | Whether to intervene proactively, adjust the timeline, or investigate the blocker |
| Overdue milestone | Overdue details, account health, engagement data | Whether to push the customer, adjust the plan, escalate, or accept the delay |
| Stalled account | 30-day stall, usage data, last CSM interaction | Root cause investigation -- is this disengagement, a priority shift, or a technical blocker? |
| Outcome milestone confirmation | Usage data, suggested outcomes | Whether the customer has actually achieved the business result (requires customer conversation) |
Required:
Strongly recommended:
lo-onboarding-orchestrator (for onboarding milestone handoff)bi-usage-monitor (for progress indicators on usage-based milestones)bi-health-score (for health context on stalled accounts)references/milestone-templates.md -- Segment-default milestone plan templates~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.