eSCM-SP Practice Coverage

Overview

Document eSCM-SP practice coverage by capability area and lifecycle phase; procedures, evidence, and artifacts for assessment or due diligence.

Getting Started

Add your source materials to the project workspace, then activate the eSCM-SP Practice Coverage skill. The agent will guide you through the process step by step.

Example Conversation

Below is an example of how a typical eSCM-SP practice coverage session unfolds. The agent confirms scope and then drafts coverage by capability area.

You: We need eSCM-SP practice coverage for our provider. Can you draft it by the ten capability areas?

Agent: I’ll draft the eSCM-SP practice coverage. Do you have existing procedures or policies in the workspace I should reference (e.g. SLAs, risk register, contract templates), or should I create a structure with placeholders from the eSCM-SP reference?

You: We have a relationship management policy and an SLA template. Use those and add placeholders for areas we haven’t documented yet.

Agent: I’ve loaded the eSCM-SP structure reference. I’ll create a section per capability area: how we implement the relevant practices, procedures, roles, and evidence. I’ll tie in your relationship management policy and SLA template where they apply and mark other areas for follow-up.

Sample Output Excerpt

Below is a representative excerpt from an eSCM-SP practice coverage document.

Relationship Management

Procedures: Client governance is defined in our Relationship Management Policy (v2.1). We hold monthly steering meetings, quarterly business reviews, and use a standard escalation matrix. Roles: Account manager owns the relationship; delivery manager owns operational liaison. Evidence: RMP document; steering meeting minutes; escalation log.

Performance Management

Procedures: SLAs are agreed at contract signature and reviewed quarterly. We report on SLA metrics via the standard dashboard and run corrective action when targets are missed. Evidence: SLA template; Q3 SLA report; corrective action register.

Extension and validation

This skill does not include custom validation tools. Elaboration is guided by the workflow in the skill and the eSCM-SP structure reference. You can add extension tools later (e.g. to check coverage of capability areas) by editing the skill’s extension.ts.