Update to Product & App Architect

{
  "description": "Compare architecture options, vendor choices or build-versus-buy without overengineering.",
  "included_files": [],
  "name": "compare-solutions",
  "skill_md_contents": "---\nname: compare-solutions\ndescription: Compare architecture options, vendor choices or build-versus-buy without overengineering.\n---\n\n# Compare Solutions\n\n## When to use\nCompare architecture options, vendor choices or build-versus-buy without overengineering.\n\n## Workflow\nIdentify actual capabilities needed, hard constraints, cost ownership, migration/lock-in, data controls, team expertise and operation burden. Use a decision matrix only when criteria are explicit; rank evidence strength. Distinguish current vendor facts from future assumptions and verify changing pricing/features with official sources.\n\nMake a recommendation, runner-up, tradeoffs, reversible stages and triggers to reevaluate. Avoid adding tooling just because it is popular. Use `../../templates/architecture-decision.md` and `../../references/research-and-evidence.md`.\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/architecture-decisions.md`.\n"
}