mcpField
E
enterprise-onboarding-implementation-review

enterprise-onboarding-implementation-review

github.com/sylphxaiOther139 installsUpdated today
Repository

About enterprise-onboarding-implementation-review

A skill for teams planning enterprise onboarding and implementation. It turns integration, migration, training, and go-live questions into a structured plan covering ownership, dependencies, readiness, and customer communications.

Key features

  1. 01Implementation type classification
  2. 02Kickoff, RACI, and milestone planning
  3. 03Dependency and escalation tracking
  4. 04Go-live and training checklists
  5. 05Post-launch adoption handoff

Use cases

  1. 01Planning an enterprise integration rollout
  2. 02Coordinating a customer data migration
  3. 03Checking readiness before go-live

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill enterprise-onboarding-implementation-review

After installing, type/enterprise-onboarding-implementation-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/enterprise-onboarding-implementation-patterns.md

Details

From the project README

Enterprise Onboarding Implementation Review

Use this skill to convert enterprise onboarding, implementation, integration, migration, training, and go-live questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify buyer segment, contract promise, use case, launch deadline, stakeholders, technical dependencies, security constraints, data/integration scope, and success criteria.
  2. Read references/enterprise-onboarding-implementation-patterns.md.
  3. Classify implementation as self-serve assisted, guided onboarding, technical implementation, migration project, regulated rollout, or multi-team change program.
  4. Define kickoff agenda, RACI, milestone plan, dependency register, go-live checklist, escalation path, training plan, and post-launch adoption handoff.
  5. Produce implementation plan, state machine, decision table, event schema, readiness checklist, and customer/internal comms cadence.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not start implementation without clear success criteria, owner roles, timeline, and customer decision path.
  • Do not treat SSO, data migration, integrations, security review, and training as generic onboarding tasks.
  • Do not declare go-live from configuration alone; require user workflow validation and support readiness.
  • Do not hide blocked dependencies until the renewal or executive review.

Output format

Implementation context:
Audience / source of truth / risk boundary:

Onboarding implementation plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Milestones, dependencies, and go-live readiness:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported