Update to Product & App Architect

{
  "description": "Route Product & App Architect requests into the appropriate product planning, UX, architecture or review workflow.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Route Product & App Architect requests into the appropriate product planning, UX, architecture or review workflow.\n---\n\n# Get Started\n\n## When to use\nRoute Product & App Architect requests into the appropriate product planning, UX, architecture or review workflow.\n\n## Workflow\nClassify the request into raw idea, validation, audit, feature change, UX, PRD, architecture, data/API, AI feature, prioritization, delivery handoff or release review. Don't force planning onto coding-only tasks when another tool is more appropriate.\n\nIf the user supplied screenshots, links, files or repositories, inspect them with the available tools first. Write down the user outcome, observed facts, assumptions, non-goals and the smallest useful next deliverable. For known scope, act immediately; ask one targeted question only when essential decisions cannot proceed. Choose the relevant specialist skill and avoid loading unrelated instructions.\n\nStart with product problem and user value, not a technology stack. Never invent access, markets, constraints, users, metrics or source contents. Read `../../references/research-and-evidence.md`. When the request entails several skills, define dependencies and route their execution truthfully under `orchestrate-specialists`.\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/research-and-evidence.md`.\n"
}