Update to Product & App Architect

{
  "description": "Check product release readiness across functionality, quality, security and operations with evidence-based verdicts.",
  "included_files": [],
  "name": "review-launch-readiness",
  "skill_md_contents": "---\nname: review-launch-readiness\ndescription: Check product release readiness across functionality, quality, security and operations with evidence-based verdicts.\n---\n\n# Review Launch Readiness\n\n## When to use\nCheck product release readiness across functionality, quality, security and operations with evidence-based verdicts.\n\n## Workflow\nAssess user core loop, error/recovery states, data safety, auth, accessibility, dependency failures, testing, observability, deploy/rollback, support, platform compliance and critical issues proportional to product scope. Require real evidence for pass; `not_assessed` isn't `passed`.\n\nClassify `ready`, `ready_with_limitations`, `not_ready`, or `not_assessed`. Map blockers to owners and tests. Use `../../references/rollout-and-governance.md` and `../../templates/release-check.md`. An attractive design or successful compile alone cannot establish production readiness.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/rollout-and-governance.md`.\n"
}