Customization
Before executing, check for user customizations at:
~/.claude/PAI/USER/SKILLCUSTOMIZATIONS/StandardsTracker/
If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.
StandardsTracker Skill
Purpose: Track TR-369 (USP), TR-069 (CWMP), and related Broadband Forum standards that affect [Your Company] product development. Surface spec changes, data model updates, industry adoption signals, and compliance gaps.
Standards Scope
| Standard |
Full Name |
Relevance |
| TR-369 |
User Services Platform (USP) |
Primary — next-gen device management, active adoption |
| TR-069 |
CPE WAN Management Protocol (CWMP) |
Legacy — still deployed, maintenance mode |
| TR-181 |
Device Data Model |
Critical — defines the data objects both protocols use |
| TR-106 |
Data Model Template |
Foundation — how data models are structured |
| TR-157 |
Component Objects for CWMP |
Supporting — reusable object definitions |
| TR-471 |
IP Performance Metrics |
Adjacent — speed test and QoE measurement |
| Wi-Fi Alliance |
EasyMesh, WPA3, Wi-Fi 7 |
Adjacent — wireless standards that interact with device management |
Sources
Custom sources: Add to USER/SKILLCUSTOMIZATIONS/StandardsTracker/sources.json
Output Format
# Standards Tracker Update
**Generated:** [timestamp]
**Sources Checked:** [list]
**Period:** Since [last check date]
---
## Spec Updates
*New releases, corrigenda, amendments to tracked standards*
1. **[TR-XXX vX.X]** - [What changed, 1-2 sentences]. [Source]
...
---
## Data Model Changes
*New objects, parameter additions/deprecations in TR-181/TR-106*
1. **[Object/Parameter]** - [What changed and why it matters for implementation]. [Source]
...
---
## Industry Adoption
*Vendor implementations, certification programs, deployment news*
1. **[Headline]** - [1-2 sentence summary]. [Source]
...
---
## [Your Company] Impact Assessment
| Change | Affects | [Your Product] Release | Action |
|--------|---------|-----------------|--------|
| [change] | [subsystem] | [2.x/3.0] | [implement/track/ignore] |
---
## Summary
| Category | Count | Top Item |
|----------|-------|----------|
| Spec Updates | X | [title] |
| Data Model | X | [title] |
| Adoption | X | [title] |
**Total:** X items | **Next check:** Run `/standards` anytime
Categories
Spec Updates
- New TR document releases (TR-369 amendments, new TRs)
- Corrigenda and errata
- Protocol version changes (USP 1.x → 1.y)
- Security advisories related to protocol implementations
Data Model Changes
- New Device.* objects added to TR-181
- Parameter additions, deprecations, or type changes
- Profile additions (Device:2.x profiles)
- Mapping changes between USP and CWMP models
Industry Adoption
- Vendor announcements of USP support
- ISP/operator deployment news
- Certification program updates
- Open-source implementation releases (OB-USP-Agent, prpl)
- Test tool releases and interop event results
[Your Company] Impact Assessment Rules
For each change found, assess impact on [Your Product]:
| Impact Level |
Criteria |
Action |
| HIGH |
Breaks existing implementation or blocks certification |
Immediate — flag for current release |
| MEDIUM |
New required object/feature in upcoming profile |
Plan — scope for next release |
| LOW |
Optional feature or future profile |
Track — add to 3.0 backlog |
| NONE |
Irrelevant to [Your Company] product line |
Ignore — note for completeness |
Workflows
| Workflow |
When to Use |
| Update |
"standards update", "TR-369 updates", "what's new in USP", "/standards" — fetch and report changes |
| ComplianceCheck |
"compliance check", "are we compliant", "TR-369 compliance" — assess [Your Product] against current specs |
| Briefing |
"standards briefing", "standards summary for leadership" — executive-ready overview |
State Tracking
State file: State/last-check.json
{
"last_check_timestamp": null,
"sources": {
"broadband-forum": { "last_checked": null, "last_hash": null },
"usp-technology": { "last_checked": null, "last_hash": null },
"usp-data-models": { "last_checked": null, "last_hash": null },
"bbf-github": { "last_checked": null, "last_hash": null },
"wifi-alliance": { "last_checked": null, "last_hash": null }
},
"known_versions": {
"TR-369": "1.3",
"TR-181": "2.17",
"TR-069": "1.6 Amendment 6",
"TR-106": "1.12"
}
}
Key Principles
- [Your Company]-first — Every finding assessed for [Your Product] impact
- Actionable — Changes tagged with release and action needed
- Crisp — 1-2 sentences per item, no spec-dumping
- Stateful — Track what's been seen, only surface new changes
- Versioned — Track known spec versions to detect updates
1---2name: standardstracker3description: TR-369/USP and TR-069/CWMP open standards tracker for [Your Company]. Monitors spec updates, data model changes, compliance gaps, and industry adoption. USE WHEN TR-369, TR-069, USP, CWMP, standards update, standards tracker, Broadband Forum, data model, BBF, open standards status, device management standards, what changed in TR-369, compliance check.4---56## Customization78**Before executing, check for user customizations at:**9`~/.claude/PAI/USER/SKILLCUSTOMIZATIONS/StandardsTracker/`1011If this directory exists, load and apply any PREFERENCES.md, configurations, or resources found there. These override default behavior. If the directory does not exist, proceed with skill defaults.1213# StandardsTracker Skill1415**Purpose:** Track TR-369 (USP), TR-069 (CWMP), and related Broadband Forum standards that affect [Your Company] product development. Surface spec changes, data model updates, industry adoption signals, and compliance gaps.1617## Standards Scope1819| Standard | Full Name | Relevance |20|----------|-----------|-----------|21| **TR-369** | User Services Platform (USP) | Primary — next-gen device management, active adoption |22| **TR-069** | CPE WAN Management Protocol (CWMP) | Legacy — still deployed, maintenance mode |23| **TR-181** | Device Data Model | Critical — defines the data objects both protocols use |24| **TR-106** | Data Model Template | Foundation — how data models are structured |25| **TR-157** | Component Objects for CWMP | Supporting — reusable object definitions |26| **TR-471** | IP Performance Metrics | Adjacent — speed test and QoE measurement |27| **Wi-Fi Alliance** | EasyMesh, WPA3, Wi-Fi 7 | Adjacent — wireless standards that interact with device management |2829---3031## Sources3233| Source | URL | What to Check |34|--------|-----|---------------|35| **Broadband Forum** | https://www.broadband-forum.org | Spec releases, corrigenda, new TRs |36| **USP Specification** | https://usp.technology | USP spec text, protocol updates |37| **USP Data Models** | https://usp-data-models.broadband-forum.org | Data model object additions/changes |38| **CWMP Data Models** | https://cwmp-data-models.broadband-forum.org | Legacy data model maintenance |39| **BBF GitHub** | https://github.com/BroadbandForum | Reference implementations, tools, OB-USP-Agent |40| **prpl Foundation** | https://prplfoundation.org | Open-source CPE software, USP adoption |41| **Wi-Fi Alliance** | https://www.wi-fi.org | EasyMesh specs, certification programs |4243**Custom sources:** Add to `USER/SKILLCUSTOMIZATIONS/StandardsTracker/sources.json`4445---4647## Output Format4849```markdown50# Standards Tracker Update51**Generated:** [timestamp]52**Sources Checked:** [list]53**Period:** Since [last check date]5455---5657## Spec Updates58*New releases, corrigenda, amendments to tracked standards*59601. **[TR-XXX vX.X]** - [What changed, 1-2 sentences]. [Source]61...6263---6465## Data Model Changes66*New objects, parameter additions/deprecations in TR-181/TR-106*67681. **[Object/Parameter]** - [What changed and why it matters for implementation]. [Source]69...7071---7273## Industry Adoption74*Vendor implementations, certification programs, deployment news*75761. **[Headline]** - [1-2 sentence summary]. [Source]77...7879---8081## [Your Company] Impact Assessment82| Change | Affects | [Your Product] Release | Action |83|--------|---------|-----------------|--------|84| [change] | [subsystem] | [2.x/3.0] | [implement/track/ignore] |8586---8788## Summary89| Category | Count | Top Item |90|----------|-------|----------|91| Spec Updates | X | [title] |92| Data Model | X | [title] |93| Adoption | X | [title] |9495**Total:** X items | **Next check:** Run `/standards` anytime96```9798---99100## Categories101102### Spec Updates103- New TR document releases (TR-369 amendments, new TRs)104- Corrigenda and errata105- Protocol version changes (USP 1.x → 1.y)106- Security advisories related to protocol implementations107108### Data Model Changes109- New Device.* objects added to TR-181110- Parameter additions, deprecations, or type changes111- Profile additions (Device:2.x profiles)112- Mapping changes between USP and CWMP models113114### Industry Adoption115- Vendor announcements of USP support116- ISP/operator deployment news117- Certification program updates118- Open-source implementation releases (OB-USP-Agent, prpl)119- Test tool releases and interop event results120121---122123## [Your Company] Impact Assessment Rules124125For each change found, assess impact on [Your Product]:126127| Impact Level | Criteria | Action |128|-------------|----------|--------|129| **HIGH** | Breaks existing implementation or blocks certification | Immediate — flag for current release |130| **MEDIUM** | New required object/feature in upcoming profile | Plan — scope for next release |131| **LOW** | Optional feature or future profile | Track — add to 3.0 backlog |132| **NONE** | Irrelevant to [Your Company] product line | Ignore — note for completeness |133134---135136## Workflows137138| Workflow | When to Use |139|----------|-------------|140| Update | "standards update", "TR-369 updates", "what's new in USP", "/standards" — fetch and report changes |141| ComplianceCheck | "compliance check", "are we compliant", "TR-369 compliance" — assess [Your Product] against current specs |142| Briefing | "standards briefing", "standards summary for leadership" — executive-ready overview |143144---145146## State Tracking147148**State file:** `State/last-check.json`149150```json151{152 "last_check_timestamp": null,153 "sources": {154 "broadband-forum": { "last_checked": null, "last_hash": null },155 "usp-technology": { "last_checked": null, "last_hash": null },156 "usp-data-models": { "last_checked": null, "last_hash": null },157 "bbf-github": { "last_checked": null, "last_hash": null },158 "wifi-alliance": { "last_checked": null, "last_hash": null }159 },160 "known_versions": {161 "TR-369": "1.3",162 "TR-181": "2.17",163 "TR-069": "1.6 Amendment 6",164 "TR-106": "1.12"165 }166}167```168169---170171## Key Principles1721731. **[Your Company]-first** — Every finding assessed for [Your Product] impact1742. **Actionable** — Changes tagged with release and action needed1753. **Crisp** — 1-2 sentences per item, no spec-dumping1764. **Stateful** — Track what's been seen, only surface new changes1775. **Versioned** — Track known spec versions to detect updates
kai-cli