cp-implement

Manages consulting implementation workstreams, steering committees, blockers, and RAG progress tracking.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill cp-implement-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cp-implement
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/cp-implement
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill cp-implement-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Consulting engagements often stall after recommendations are approved because execution lacks structure. This Skill provides a complete framework for the Implement phase of a McKinsey-style consulting process, keeping workstreams on track, blockers resolved, and sponsors informed. ## Core Features & Use Cases - Workstream & RAG Management: Run kickoff meetings, weekly execution rhythms, and Green/Amber/Red status reporting with defined escalation protocols. - Steering Committee Facilitation: Structured deck outlines, decision documentation templates, and guidance for handling difficult governance conversations. - Blocker & Change Management: Categorized blocker escalation (resources, data, decision, technical, political) plus adoption tracking and resistance signal detection. - Use Case: A consultant supporting a client's 6-month transformation program uses this Skill to run weekly working sessions, produce the implementation tracker artifact, escalate aging blockers, and prepare monthly steering committee decks. ## Quick Start Ask the assistant to run the cp-implement step to set up workstream tracking, RAG reporting, and steering committee governance for your approved implementation plan.

Frequently Asked Questions about cp-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage consulting implementation workstreams?▼

Run a kickoff meeting to confirm scope and governance, then maintain a weekly rhythm of working sessions, team syncs, and written status reports. Track each workstream with RAG status and escalate blockers unresolved after 5 business days.

How to structure a steering committee meeting during implementation?▼

Use a six-section deck: summary, workstream status, impact tracking, decisions needed, risks, and next period. Send pre-reads 48 hours ahead, keep the meeting to 60-90 minutes, and document every decision with owner and deadline.

When should a blocker be escalated to the sponsor?▼

Escalate when a blocker remains unresolved 5 days after being surfaced (Amber status) and escalate immediately to the sponsor at 10 days (Red status) with 2-3 resolution options. If the sponsor cannot resolve it, convene an emergency steering committee.

When should I not use a formal implementation structure?▼

Skip formal implementation structure when the engagement is advisory only, when the client has a strong internal PMO owning execution, or when implementation lasts under 4 weeks. In those cases use a simplified task tracker or transition and monitor only.

What are the signs of a failing implementation?▼

Key red flags include no steering committee within 30 days of kickoff, blockers aging beyond 2 weeks without escalation, missing impact tracking against projected benefits, consultants doing client work, and absent adoption metrics.