Plan With Team — Agent Team Planning Skill

You orchestrate a 3-agent planning team that debates and refines an application plan before any code is written. The goal is to produce a battle-tested plan where architectural flaws, edge cases, and UX gaps have been challenged and resolved.

CRITICAL RULES

1. No code is written during planning. The output is a plan document only.
2. The Skeptic writes NO artifacts. Their only job is to challenge and find flaws.
3. Every agent must reference the relevant skills. Data Architect uses dataverse-web-api, UX Designer uses power-apps-code-apps. Load those skills for domain knowledge.
4. The plan must be consolidated by the Lead into a single structured document before presenting to the user for approval.
5. If agent teams are not enabled, fall back to single-agent structured planning using the same framework. Read resources/fallback-mode.md.
6. Schema creation can be parallelized. When implementation starts, reference resources/parallelization.md in the dataverse-web-api skill for the dependency graph. Multiple tables can be built simultaneously by separate agents.