Write the job in a sentence
Impostor Dominion advertises deploying troops, upgrading towers, and capturing rival outposts. Before using any of those actions, assign it a job. A useful job describes a change you want to cause: attempt a capture, respond to a visible threat, or prepare an available tower for a requirement the interface explains. The wording matters because it gives you something to reassess afterward.
This is an editorial planning method based on the listed actions, not a tested battle plan. Exact unit roles, costs, and combat rules must come from the game. Do not assign a specialist ability to a troop merely because of its appearance.
Distinguish action from intention
Deploying is what you do; the job explains why. Two deployments may look alike while serving different intentions. One might support an immediate attempt to take a stronghold; another might address an enemy action you can see, if the game supports that response.
Before acting, ask what evidence would show that the job is complete. Capture has an obvious candidate: the game acknowledges ownership. Preparation needs another visible criterion, such as the specific upgrade being applied. A vague instruction to become stronger makes it difficult to know when preparation should end.
Avoid jobs that compete silently
Suppose you want both an immediate capture and an upgrade. Compare the resources and actions the interface says each requires. If they compete, choose which job has priority for the present situation. Do not assume that both plans can proceed unchanged simply because both are attractive.
This hypothetical conflict is about attention and stated requirements, not an invented economy. Read the available information before deciding whether there is a real constraint. The useful habit is noticing when one intention prevents another from receiving the support it needs.
Retire or rewrite the job
After the action, compare the result with the sentence you started with. Is the job complete, still relevant, or based on information that changed? A failed capture may call for a different assignment rather than repetition. A completed upgrade may release attention for another task.
Keep the review brief. The purpose is to stop old intentions from continuing automatically after the battlefield has changed. Progress becomes a sequence of explicit assignments whose results you can inspect, instead of a stream of deployments chosen only because an action was available.