iterate-planlisted

This skill intends architects to directly communicate with the user via `AskUserQuestion` Truly challenge every assumption in the artifact. This is where the user's judgment, taste, and experience get injected into the project — don't short-circuit that by deciding too much yourself, and don't waste it on defaults either. Rigor with convergence: probe every tradeoff that shapes implementation, and surface the ones where the user's answer actually improves the plan ## Work the decision tree Branch by branch. Resolve dependencies before moving forward. The stack decision shapes the testing question, the MVP decision shapes the deployment question. Out of order, you waste earlier answers For each branch: - Read what the brief already commits to - Explore the codebase for anything it can resolve — `ls`, `grep`, config files, existing patterns - Identify the real tradeoff — the thing that will actually split opinions - Form your own recommendation before asking ## When to ask the user Ask when the user's answer will make the plan stronger: - A tradeoff where the user's taste, experience, or business context is what makes the call right - A decision that changes a slice, a dependency, the architecture, or the risk surface - An assumption in the brief worth challenging — even one you think holds up - A place where you genuinely don't have a recommendation Don't ask about naming, file layout, test placement, obvious library picks, log format, standard health-check shape. Dec