forked from diegoecab/oci-deal-accelerator
ca93a0aa4e
Why this set of changes:
- KB pricing was drifting silently — domain files (database.yaml,
storage.yaml, etc.) had prices 30-800% off the live Oracle API and
nobody read them. The skill was auditing as stale on every check
with no path to fix it.
- The skill itself violated Anthropic's spec (`name` field had
uppercase/spaces) and was over the 500-line guideline (647 lines),
hurting discovery and load performance.
- Welcome flow occasionally improvised the menu instead of reading
SKILL.md, missing options.
Pricing — single source of truth, fully automated:
- Extend tools/refresh_sku_catalog.py with --refresh-domain compute,
pulls shape-level prices from the Oracle public pricing API
(apexapps.oracle.com), preserves manual fields (notes, GPU specs,
free-tier annotations, estimation_helpers), recomputes derived
monthly values, and protects $0 free-tier prices from overwrite.
- Delete 12 redundant pricing/<domain>.yaml files. They duplicated
oci-sku-catalog.yaml with worse abstractions and were nobody's
source of truth (no tool consumed them).
- Migrate the genuinely valuable knowledge from those 12 files
(billing models, BYOL rules, free-tier rules, ECPU vs OCPU,
X11M elastic model, hyperscaler comparisons, service nuances)
into kb/field-knowledge/pricing-knowledge.yaml — non-numeric,
no refresh needed.
- Result: pricing freshness check goes from 13 stale files to 0.
KB freshness automation:
- Add tools/kb_freshness.py — wrapper around kb_linter.check_freshness()
with --check, --auto-refresh, --json, --quiet modes. Bridges stale
files to their refresh tools (SKU catalog, compute domain, arch
center). Wired into the welcome flow as a pre-flight banner that
asks the user before refreshing.
- Fix pre-existing kb_linter bug: it crashed on the 45 multi-doc
YAML files (frontmatter + body pattern) because it used safe_load
instead of safe_load_all. Freshness check was effectively dead.
- Standardize timestamp field: linter now accepts last_verified,
last_updated, and last_refreshed; refresh_arch_catalog writes
last_verified instead of last_refreshed.
- Add make freshness / make freshness-refresh targets.
Skill alignment with Anthropic Agent Skills best practices:
- Rename `name: OCI Deal Accelerator` to `oci-deal-accelerator`
to comply with the [a-z0-9-]{1,64} spec.
- Refactor SKILL.md from 674 to 445 lines via progressive disclosure:
extract WA review output format, ECAL readiness format, and output
conventions into docs/skill/*.md referenced from the main file.
- Add scripts/sync-skill.py + make sync-skill: source of truth is
root SKILL.md, .agents/skills/oci-deal-accelerator/SKILL.md is
auto-generated. make lint validates sync.
- Add evaluations/ with 3 manual baseline scenarios (welcome-flow,
full-proposal, wa-review) per the Anthropic best-practices guidance
to "build evaluations first."
Welcome flow hardening:
- Tighten CLAUDE.md to MANDATE reading SKILL.md before showing the
menu (no improvising), and document the freshness pre-flight check
with the ask-before-refresh user flow.
- Update SKILL.md welcome flow to instruct: parse kb_freshness JSON,
show banner with stale count + oldest file, prompt user to refresh
(only when an automated tool exists), fall back silently on errors.
Linter hygiene (zero remaining issues):
- Expand config/kb-tags.yaml taxonomy with features, operations,
metrics, limitations sections covering 31 previously-unknown tags
used in field findings (rac, ecpu, refreshable-clone, hnsw, etc.).
- Assign owners for kb/compatibility/, kb/competitive/,
kb/well-architected/ (Diego Cabrera as default until team grows);
kb/pricing/ marked as "Auto-refreshed" since it no longer needs
human ownership.
- kb_linter accepts top-level `date` as fallback for contributor
block; migrate FF-202603-008 from legacy `reported_by` to
contributor block.
- Result: linter goes from 45 issues to 0.
Other:
- Recompute estimation_helpers monthly values in compute.yaml after
the price refresh (they were derived from the old E5/A1 numbers).
- Add kb/README.md — contributor guide (directory map, frontmatter
spec, refresh tooling, review cadence).
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
89 lines
2.8 KiB
Markdown
89 lines
2.8 KiB
Markdown
# ECAL Readiness Scorecard Format
|
||
|
||
This document defines how option 12 (ECAL Readiness Score) presents its results.
|
||
Referenced from `SKILL.md` § Welcome Flow → Behavior Rules → option 12.
|
||
|
||
## Scoring model
|
||
|
||
Each artefact has a status: ✅ Complete | 🟡 Partial | ❌ Missing | ⬜ Not Applicable (future phase).
|
||
|
||
Phase scores are calculated as:
|
||
- ✅ = 1.0 point, 🟡 = 0.5 point, ❌ = 0 points, ⬜ = excluded from denominator
|
||
- Phase score = (sum of points / applicable artefacts) × 100%
|
||
|
||
Overall ECAL Readiness = weighted average:
|
||
- DEFINE: 25% weight
|
||
- DESIGN: 50% weight (largest phase, most artefacts)
|
||
- DELIVER: 25% weight
|
||
|
||
## Readiness levels
|
||
|
||
- 🟢 80-100% — Ready to proceed to next phase
|
||
- 🟡 60-79% — Gaps exist but manageable; proceed with caution
|
||
- 🟠 40-59% — Significant gaps; address before proceeding
|
||
- 🔴 0-39% — Major gaps; phase needs substantial work
|
||
|
||
## Output format
|
||
|
||
The ECAL readiness score MUST produce **two layers of output**: (a) the formatted terminal scorecard shown to the user, and (b) the structured YAML file saved to disk. The terminal output is the primary deliverable — the YAML is the backing data. Never produce YAML-only output without the formatted scorecard.
|
||
|
||
```
|
||
══════════════════════════════════════════
|
||
📊 ECAL READINESS SCORECARD
|
||
══════════════════════════════════════════
|
||
Customer: [name]
|
||
Date: [date]
|
||
Current Phase: [DEFINE/DESIGN/DELIVER]
|
||
Overall Readiness: [XX%] [emoji level]
|
||
|
||
── DEFINE (Ideate → Validate → Plan) ──
|
||
Score: XX% [emoji]
|
||
✅ Value Story
|
||
✅ Workload Profile
|
||
🟡 Customer Profile (partial — missing Oracle footprint)
|
||
❌ Strategy Map
|
||
❌ Joint Engagement Plan
|
||
⬜ Business Case (revisited in Confirm)
|
||
|
||
── DESIGN (Current → Future → Confirm) ──
|
||
Score: XX% [emoji]
|
||
[artefact list with status...]
|
||
|
||
── DELIVER (Adopt → Operate → Improve) ──
|
||
Score: XX% [emoji]
|
||
[artefact list with status...]
|
||
|
||
── TOP 5 GAPS ──
|
||
1. ❌ [artefact] — [why it matters] — [recommended action]
|
||
2. ...
|
||
|
||
── RECOMMENDED NEXT ACTIONS ──
|
||
1. [specific action]
|
||
2. [specific action]
|
||
3. [specific action]
|
||
|
||
── ENGAGEMENT RACI CHECK ──
|
||
Roles identified: [list]
|
||
Roles missing: [list]
|
||
══════════════════════════════════════════
|
||
```
|
||
|
||
## Files generated
|
||
|
||
Always list the files saved at the end of the scorecard:
|
||
|
||
```
|
||
📁 Files saved:
|
||
- examples/<customer>-ecal-scorecard.yaml
|
||
```
|
||
|
||
## After ECAL scorecard menu
|
||
|
||
```
|
||
What do you want to do?
|
||
→ [A] Fix the top gap now (I'll generate the missing artefact)
|
||
→ [B] Generate all missing artefacts for current phase
|
||
→ [C] Export scorecard as a slide (.pptx)
|
||
→ [D] Re-score after updates
|
||
```
|