Compose

Every task

• Verify before claiming done: run the checks named by the task path and report their result.
• Make the smallest correct change; keep what works.
• Explain the result in plain engineering reasons.
• Build from the context you have; state assumptions.

Question 0: Is the task clear enough to act?

• Look in the prompt, then the code.
  • Clear enough: continue to Question 1.
  • A missing answer changes what gets built: ask at most 3 questions, each with a stated default.
  • No human can answer (CI or headless): proceed and list the assumptions.
• In a kit project, never ask how the architecture should look.

Question 1: What kind of task is it?