app-readiness

Assesses production readiness across eight architecture domains and generates an HTML report.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill app-readiness-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-readiness
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/app-readiness
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill app-readiness-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams approaching go-live often lack a structured, evidence-based way to judge whether an application is truly ready for production, relying on gut feel instead of verifiable signals from pipelines, code, and architecture docs. ## Core Features & Use Cases - Eight-domain scoring: Evaluates deployment pipeline, resilience, observability, security posture, scalability, data integrity, operational runbook, and test coverage on a 1-5 maturity scale with RAG ratings. - Azure DevOps integration: Queries ADO pipelines, environments, approval gates, and service connections via the REST API to verify real deployment state. - Hosting-model awareness: Applies tailored checklists for IIS, container, App Service, and VSTO/ClickOnce deployments, including Entra ID and SPA authentication checks. - Use Case: Before a go-live decision, run the assessment to get an HTML report with a verdict (production ready, conditionally ready, not ready, or blocked), top blockers, and a tiered remediation roadmap. ## Quick Start Ask the assistant to run an app production readiness assessment in quick mode to score all eight domains and produce the HTML report.

Frequently Asked Questions about app-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my application is production ready?

Run the app-readiness assessment, which scores eight domains including deployment pipeline, resilience, observability, security, scalability, data integrity, runbook, and test coverage. It produces an HTML report with a RAG score grid, an overall verdict, and a remediation roadmap.

What is the difference between quick and full readiness assessment modes?

The --quick mode runs bash evidence collection, architecture doc analysis, and ADO pipeline checks without reading source files, using about 12K tokens. The --full mode adds consent-gated targeted source reads for domains scored Red, using about 25K tokens.

Does the readiness check work with Azure DevOps pipelines?

Yes, it queries the Azure DevOps REST API for pipeline runs, environments, approval gates, and service connections when AZURE_DEVOPS_PAT is set. Without the PAT, pipeline checks are skipped and that domain is scored as unverifiable.

Can it assess VSTO or ClickOnce Office add-in deployments?

Yes, when the deployment architecture indicates a VSTO hosting model, it loads a dedicated checklist covering signing and trust, ClickOnce manifest, Office compatibility, build pipeline, tests, secrets, and runbook domains.

What happens if no security scan report exists?

The security posture domain is scored 1 or 2 and flagged as blocking, since an unscanned application has an unknown security posture. Unresolved Critical or business-context findings also block the overall verdict regardless of other scores.

Why does the assessment stop and ask for the architect skill first?

It requires deployment context from .claude/architecture/architecture-deployment.md, including hosting model, environments, secrets strategy, and auth provider. If that file is missing or unanswered, you must run the architect skill to capture deployment context before readiness can be scored.