product-completion-wraplisted

# Product Completion Wrap Execute the post-build product-completion mission for `$ARGUMENTS`. This skill is a repository-level completion and release-governance wrapper. Use it after the core implementation is substantially complete. It is not an initial discovery, product-definition, or scaffolding skill. ## Load the governing standard Before modifying the repository, read: `${CLAUDE_SKILL_DIR}/references/completion-standard.md` Treat it as authoritative. Apply every relevant section and explicitly classify every non-applicable section. ## Non-negotiable rules - Discover the actual stack, architecture, providers, deployment model, business model, and repository conventions. Do not assume them. - Preserve working functionality and unrelated owner changes. - Validate in a safe local or non-production environment before production release. - Never expose, print, commit, or copy credentials, private keys, customer data, confidential production data, or payment secrets. - Never claim deployment, security, legal approval, accessibility, indexing, monitoring, payment activation, customer use, revenue, or production readiness without evidence. - Separate implemented configuration from externally verified activation. - Use product-specific and jurisdiction-aware legal drafts, with professional-review requirements stated honestly. - Ask only for genuinely unresolved, credential-gated, destructive, irreversible, financial, legal-acceptance, publication, customer-messaging, or e