From enterprise-readiness
Formatted enterprise readiness assessment report
Configuration options for this output style
When generating enterprise readiness reports, use this structure:
# Enterprise Readiness Assessment
**Project:** {project_name}
**Date:** {date}
**Overall Score:** {score}/100 {grade_emoji}
{grade_emoji} based on score:
- 90-100: 🟢 Excellent
- 70-89: 🟡 Good
- 50-69: 🟠 Needs Improvement
- <50: 🔴 Critical
## {Category} ({score}/{max})
| Requirement | Status | Details |
|-------------|--------|---------|
| {req_name} | ✅/❌/⚠️ | {details} |
{Specific findings and recommendations}
## Priority Actions
### Critical (Must Fix)
1. **{Issue}**: {Description}
- Impact: {impact}
- Fix: {specific_fix}
### High Priority
1. ...
### Recommended
1. ...
## Score Breakdown
| Category | Score | Weight | Weighted |
|----------|-------|--------|----------|
| Security | X/40 | 40% | X |
| Quality | X/30 | 30% | X |
| CI/CD | X/30 | 30% | X |
| **Total** | | | **X/100** |
---
Generated by enterprise-readiness skill
See: https://github.com/netresearch/enterprise-readiness-skill
npx claudepluginhub netresearch/claude-code-marketplace --plugin enterprise-readinessFormats Claude's responses for the Harness Plan/Work/Review workflow. Planning phase uses task tables with status markers; implementation shows code changes with context; review structures findings by severity. Includes progress reporting (Done/Current/Next). Preserves coding behavior.
Formats Claude's responses to be concise, native, and execution-first. Avoids ceremony, planning, or multiple options unless explicitly requested. Preserves coding behavior. Prioritizes native tools and agent/plan usage. Table-friendly output.
Enforces fact-grounded FinOps analysis: evidence-backed claims with citations/derivations, standardized currency/percentage/variance formatting, structured tables for comparisons, explicit time periods and assumption labels for cloud cost data. Preserves coding instructions.