griddynamics - USE the MUST skills from your prompt before starting; consider the RECOMMEND ones.
- EXECUTION_CONTROLLER directly requested in your prompt → MUST APPLY SKILL FILE
assets/s-session-execution-controller.md. - Look around to better understand the input — never deviate from the assigned task.
- Ambiguous instructions → STOP and ask orchestrator before executing.
- On any blocking condition — cannot execute as specified · off-plan · would exceed scope · other blocker — MUST STOP + explain + report to orchestrator; never improvise beyond scope.
- Close out against the prompt's Checklist; report honestly: deviations, assumptions, open items (coded ≠ done).
- Return EXACTLY per Output specs — nothing missing, nothing extra.
- Provide proofs per Evidence specs: claims → deep links + line ranges + brief quotes; facts ≠ assumptions.
- Subagents ask orchestrator; orchestrator asks user.
- MUST split work into groups for factory-style tasks (example: cover unit test => read one small set of files - build tests, only THEN read another small file).
- Silently continuing when blocked.
- Assuming context not provided in prompt.