tmforum-oda/oda-agent-skills-marketplace/check-usecase-maturity

Check Use-Case Maturity — Skill Instructions

What this skill answers

"Is TMFSxxx safe to build against right now?" — a plain-language verdict, not a raw dump of frontmatter fields. Reads only YAML frontmatter, zero document-body prose parsing.

Where the data lives

Given an id like TMFS030, the file is at a known path — no directory scan, no search:

knowledge/use-cases/{ID}/{ID}.md

Read just the YAML frontmatter block (between the two --- lines at the top). The fields that matter for this skill:

status is just "{maturity} - {approval_status}" concatenated — don't re-derive it, and don't rely on it alone either. maturity and approval_status are surfaced as separate fields specifically because they can, and do, disagree — see the decision table below.

If the file doesn't exist at that path, say so plainly — don't guess a nearby id or silently fall back to the matrix/index files. A missing use case isn't this skill's job to explain; point at knowledge/index/usecase-list.json's status_in_ig1228 field if the caller wants to know why it isn't there.

Decision table

Do not treat maturity: GA alone as "safe." TM Forum's own catalog listing marks every Available document identically, whether it's a year-stable GA spec or a first-draft Alpha — and GA maturity and TM Forum Approved approval do NOT always travel together. TMFS008 and TMFS019A are both maturity: GA but only approval_status: Team Approved, not TM Forum Approved — a real, current example in this corpus, not a hypothetical edge case. Read both fields, always; never shortcut to a verdict from maturity alone.

release_status: Pre-production vs Production is TM Forum's own separate publication-track signal — report it alongside the verdict (e.g. "GA / TM Forum Approved, but still Pre-production release status") rather than folding it into the maturity/approval verdict above; it's supporting evidence, not a fifth row of the table.

Output format

A short verdict, not a field dump. Example, for TMFS030:

TMFS030 (v1.1.0) — Beta / Member Evaluated, Pre-production release

status. Provisional — expect changes; usable for exploration, not yet as

a committed dependency.

Always cite the id, version, and both maturity/approval_status verbatim (not paraphrased) alongside the plain-language verdict, so a reader can see the raw fields the verdict was derived from and disagree with the interpretation if they want to.

What this skill does NOT do

• Does not read the use case's body (Executive Summary, Description,

sequence diagrams) — that's capture-requirements-from-usecase / generate-test-cases-from-usecase's job.

• Does not resolve component/API links or check whether those are

not_yet_specified/fetch_failed — this skill is about the use case document's own maturity, not its dependencies' maturity. (A natural follow-on skill, not built yet: cross-check a use case's linked components/APIs for their own status too.)

• Does not query TM Forum's website — everything it needs is already in

knowledge/; a skill must be able to answer "is this safe to build against?" without a network call.