Skip to content

agent readiness score

rzp-slash[bot] edited this page May 5, 2026 · 4 revisions

Agent Readiness Score — razorpay/ifsc

Scored by /agent-readiness-score. Band scale: <30 Not Ready | 30–54 Needs Work | 55–79 Assisted | 80+ Ready.

Last scored: 2026-05-06

Pillar Score /Max % Band
Context 4 /14 28.6% Not Ready
Testing 0 /30 0.0% Not Ready
CI/CD 2 /14 14.3% Not Ready
Aggregate 6 /58 10.3% Not Ready

Sub-criterion Breakdown

# Sub-criterion Score Max Key Evidence
C1 Agent-ready plugin outputs 0 6 20 failures; AGENTS.md and .agents/ both missing
C2 Codebase navigability 4 4 No qualifying subdirs (≥15 src files); Navigability Coverage: 100%
C3 Context freshness 0 4 No repo-skill docs with frontmatter; Freshness Score: 0/4
T1 (UT) Unit test coverage 0 3 UT: 0% — no SonarQube project key configured
T1 (SLIT) SLIT / integration coverage 0 6 SLIT: 0% — not onboarded to MCC (no workflow-name match in 30d)
T1 (E2E) E2E coverage 0 5 E2E: 0% — not onboarded to MCC (no workflow-name match in 30d)
T2 API & gRPC contract docs 0 5 No gRPC (no razorpay/rpc in go.mod); no swagger/OpenAPI spec
T3 Devstack v2 readiness 0 5 Library repo; no dev/ifsc/ in kube-manifests; no helmfile in repo
T4 (Uptime) Devstack deployment SR 0 3 Uptime: N/A — not on devstack; no traefik metrics data
T4 (E2E SR) E2E test success rate 0 3 E2E SR: N/A — no argo_workflows_e2e_status_total data in 7d
D1 Agent skill coverage in CI 0 4 No .agents/skills/; no skill refs in CI workflows
D2 Deployment automation 0 4 spinacode: not found — no v3/ifsc or any match across all passes
D3 CI speed & build hygiene 2 3 p50: ~244s (~4.1 min) across last 5 PRs; no path filters; no Docker builds (library repo)
D4 Take-it-live config 0 1 absent
D5 Baseline-monitoring 0 2 metrics: no (no relevant surfaces detected), dashboard: no, alert: no

Summary

ifsc is a multi-language reference data library (Go, Node, Ruby, PHP) providing IFSC bank code validation — it is not a deployed microservice and lacks the standard service scaffolding expected by the agentic SDLC framework. Its CI is fast (~4 min p50 across five parallel language matrix builds) and the small codebase requires no large-subdir navigation docs, earning full C2 marks. However, all other agent-readiness signals are absent: no AGENTS.md or repo-skill context layer, no SonarQube or MCC test coverage, no Spinnaker pipeline, no devstack, and no baseline monitoring. The single highest-leverage fix is bootstrapping the agent context layer — adding AGENTS.md and .agents/skills/repo-skill/ — which would immediately unlock C1/C3 and give agents the domain knowledge to navigate this multi-language codebase effectively.


Cloned to /tmp/agent-readiness-score-ifsc — re-run after changes are pushed.

Clone this wiki locally