Update to Product & App Architect

{
  "description": "Coordinate real specialist product, UX and architecture agents when available, otherwise use an honest sequential workflow.",
  "included_files": [],
  "name": "orchestrate-specialists",
  "skill_md_contents": "---\nname: orchestrate-specialists\ndescription: Coordinate real specialist product, UX and architecture agents when available, otherwise use an honest sequential workflow.\n---\n\n# Orchestrate Specialists\n\n## When to use\nCoordinate real specialist product, UX and architecture agents when available, otherwise use an honest sequential workflow.\n\n## Workflow\nLead owns shared brief, source evidence, user permissions, task graph and synthesis. For broad independent work activate product researcher, UX designer, technical architect, security reviewer or QA as needed. Real parallel agents only if host tools actually expose them; otherwise perform separate sequential checks and do not claim multiple independent agents ran.\n\nDefine delegated scope, allowed sources/tools, file ownership, acceptance criteria and evidence. Product framing must precede choices that depend on it. Independent review should challenge unsupported claims and scope creep. Return a reconciled decision record rather than contradictory agent reports. See `../../references/multi-agent-orchestration.md` and `../../templates/agent-handoff.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/multi-agent-orchestration.md`.\n"
}