mcpField
E
enterprise-readiness-review

enterprise-readiness-review

github.com/sylphxaiMarketing & growth147 installsUpdated today
Repository

About enterprise-readiness-review

A skill for product and sales teams to turn enterprise requirements into a reviewable readiness assessment. It separates launch blockers from sales evidence and product polish, and produces a matrix, risk register, proof pack, and rollout plan.

Key features

  1. 01Enterprise stakeholder and context mapping
  2. 02Readiness matrix and risk register
  3. 03Blocker and polish prioritization
  4. 04Sales proof pack and rollout plan

Use cases

  1. 01Assessing readiness for an enterprise launch
  2. 02Preparing evidence for sales and security reviews
  3. 03Prioritizing gaps across security, identity, legal, and support

Install

Copy the command and run it in a terminal.

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

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

Bundled filesagents/openai.yamlreferences/enterprise-readiness-patterns.md

Details

From the project README

Enterprise Readiness Review

Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice.

Workflow

  1. Identify buyer, champion, economic owner, IT/security reviewer, deployment model, data sensitivity, and contract motion.
  2. Read references/enterprise-readiness-patterns.md.
  3. Map enterprise asks into security/trust, identity/admin, legal/procurement, support/SLA, implementation, and product gaps.
  4. Separate launch blockers from sales-enablement evidence and premium-plan polish.
  5. Produce readiness matrix, risk register, sales proof pack, and rollout plan.

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 promise certifications, compliance, SLAs, or data residency that do not exist.
  • Do not build enterprise features without a buyer/problem/use-case map.
  • Separate security evidence from marketing claims.
  • Escalate legal, regulatory, and contractual obligations to qualified owners.

Output format

Enterprise context:
Buyer / reviewer / data sensitivity:

Readiness matrix:
| Area | Current proof | Gap | Buyer impact | Priority | Owner |
| --- | --- | --- | --- | --- | --- |

Blockers vs polish:
- Blocker:
- Sales enablement:
- Future plan:

Pilot / rollout plan:
- <step, proof, gate>

Comments

Markdown supported