atelier-orchestratorlisted

<EXTREMELY-IMPORTANT> If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT. This is not negotiable. This is not optional. You cannot rationalize your way out of this. </EXTREMELY-IMPORTANT> # Planning Workflow You have skills. You MUST use them. Not "should." Not "when convenient." MUST. Invoke relevant skills BEFORE any response or action. Even a 1% chance a skill might apply means you invoke it. If an invoked skill turns out to be wrong for the situation, you don't need to follow it. But you must check. ## The One Rule **When an implementation choice exists, never write code until the human has reviewed and approved a written plan.** Exact mechanical changes may use the exception below. The plan may be inline in the conversation or backed by persisted spec artifacts. Select the mode before invoking an artifact-producing skill, state the choice with one brief reason, and let the human override it. ## Governing Principles Invoking a skill selects relevant guidance. It does not make every pattern in every loaded skill part of the solution. Existing source, explicit requirements, and the smallest correct change determine which patterns apply. Begin with the current design and the minimum behavior-preserving change. Product, infrastructure, and architectural expansion require explicit scope. Keep **ponytail** active throughout d