tm-forum-oda-consumer

Plugin tm-forum-oda-consumer from marketplace tm-forum-oda-marketplace in tmforum-oda/oda-agent-skills-marketplace. Commands read from the repo's manifest — yesterday.

Skills (19)

• assess-change-impact

  Given a TM Forum ODA component (TMFCxxx), Open API (TMFxxx), or eTOM process (GB921 id such as 1.2.20) and a proposed change (deprecation, breaking version bump, removal), lists every TMFSxxx use case that depends on it, describes specifically how each one uses it, and drafts a maturity-weighted mig

• audit-implementation-against-component

  Given a TMFCxxx component id and a description of an existing implementation, checks conformance at Component-boundary granularity, split explicitly the way component.yaml itself is split -- Core Function (does it expose/consume the real exposedAPIs/dependentAPIs) and Supporting Function (does it pr

• audit-implementation-against-usecase

  Given a TMFSxxx use-case id and an existing implementation (codebase, API contract, or integration config), checks whether the implementation actually follows the use case's described flow and calls the right real APIs, flagging drift from spec. Use this to audit an existing system against ODA, not

• capture-requirements-from-usecase

  Given a TMFSxxx use-case id, reads its Description/Scope/Objective sections and drafts user stories and acceptance criteria, citing the exact component/API ids from frontmatter for any integration touchpoint rather than inventing them. Use this to turn an existing use case into requirements a delive

• check-usecase-maturity

  Given a TM Forum ODA use-case id (TMFSxxx), reads its cached frontmatter and returns a plain-language maturity/trust verdict -- whether it's safe to build against today. Reads only YAML frontmatter, no document-body parsing. Use this before starting requirements or test-case work against any TMFSxxx

• decompose-requirement-against-oda

  Given a plain-language requirement that `recommend-oda-components-for-requirement` couldn't match to an existing use case, produces a structured ODA-aligned decomposition (business intent, candidate eTOM processes, candidate components/APIs, candidate information entities, and explicit open question

• deliver-oda-requirement

  Given a plain-language requirement, orchestrates the full Discover-to-Run chain of existing consumer skills against it -- finding or decomposing the requirement, capturing it as requirements, drafting architecture/event designs, gating on validate-design-against-oda, generating a Build-stage impleme

• draft-architecture-diagram-from-usecase

  Given a TMFSxxx use-case id, reads its PlantUML/sequence-diagram sources and linked component/API frontmatter, and emits a component overview diagram plus one Mermaid sequence diagram per step as a design-doc-ready artifact, citing only real component/API ids. Use this when asked for an architecture

• draft-event-design-for-component

  Given a TMFCxxx component id (or one identified via decompose-requirement-against-oda/recommend-oda-components-for-requirement) and the APIs it exposes or depends on, drafts published/subscribed event definitions in the same shape every cached component.yaml's eventNotification block already uses --

• explain-etom-process

  Given a TM Forum eTOM (Business Process Framework / GB921) process id such as 1.2.20 or GB921:1.2.20, reads the cached process record and returns a plain-language explanation -- what the process is, where it sits in the hierarchy, whether it was added or renamed recently, and which ODA Components im

• generate-api-conformance-tests

  Given a TMFxxx id and version, generates conformance test assertions directly from its cached OpenAPI schema -- required-field presence, enum-value validity, declared operations per path, and expected status codes -- using real sample payloads as fixtures where they exist and pass/fail. If a real im

• generate-api-mocks-from-usecase

  Given a TMFSxxx use-case id, uses its linked APIs' cached OpenAPI schemas and real sample payloads to scaffold a mock server or example request/response fixtures for integration testing before a real backend exists. Use this when asked for API mocks, stub responses, or test fixtures for a use case's

• generate-component-svg-diagram

  Generate SVG architecture diagrams for TM Forum ODA Components (TMFCxxx) from their cached component.yaml — or from a component's Helm chart / reference implementation, compiled with helm template — rendered with D3 — a component box with its eTOM business activities and SID data entities, dependent

• generate-implementation-scaffold-from-usecase

  Given a TMFSxxx use-case id (or an explicit component/API set from recommend-oda-components-for-requirement/decompose-requirement-against-oda), generates typed request/response models and route/handler stubs directly from its linked APIs' cached OpenAPI schemas, in a language of the caller's choosin

• generate-test-cases-from-usecase

  Given a TM Forum ODA use-case id (TMFSxxx), reads its sequence-diagram section and linked component/API frontmatter, then drafts BDD-style (Gherkin) test scenarios grounded in the real component/API IDs and cached OpenAPI schemas in ${CLAUDE_PLUGIN_ROOT}/knowledge/apis/ -- never invented ones. Mirro

• implement-oda-component

  ⚠ Builds & deploys — the one skill in this plugin with real side effects (builds/pushes Docker images, can `helm install`). Build a complete TM Forum ODA Component implementation from scratch, including Node.js microservice source code, Dockerfiles, and Kubernetes Helm charts. Use this skill wheneve

• recommend-oda-components-for-requirement

  Given a plain-language business requirement (not yet a TMFSxxx id), finds the closest-matching existing use case(s) by name and component/API overlap, and proposes a starting architecture grounded in real component/API ids -- never invented ones. Use this at the start of a design, before a requireme

• review-architecture-against-oda

  Given a description of a proposed or existing multi-component architecture (not scoped to one use case or one component), reviews it against the cached ODA corpus for duplicated ownership (a capability the architecture assigns to a new/custom component that an existing TMFCxxx already owns), point-t

• validate-design-against-oda

  Given a proposed component or API design that claims to extend or depend on existing ODA components/APIs, checks those claims against the real cached specs and flags drift -- fields, operations, or behavior the design assumes exist but don't. Use this before building against an assumed ODA capabilit