Ask for work and review the result

Give feedback, answer questions, and follow documents and code changes through delivery.

Foreman keeps the conversation about your work alongside Tasks, where you can see the next action, worker activity, linked results, and pull requests. Use the same task when you correct or continue a request.

Describe the result and its limits

Give Foreman the project or source material, the outcome, and a way to tell whether the work is right. State whether you want research or implementation.

The sign-in button stays disabled after I enter a valid email. Reproduce it, fix it, and check the form. Don't change the sign-in design.

Read these two API guides and recommend one for our import tool. Write a comparison document for the team. Don't change code.

Paste links or name files in the selected repository. Use Add a photo to attach a screenshot when the problem is visual. A reference is useful only if the agent can access it; a link does not grant access to a private service.

Answer a question or change direction

  1. Read Foreman's question and the consequence of each choice.
  2. If the question offers choices or a form, select your answer. The controls put text into the message field; selecting a choice does not send it.
  3. Edit the answer if needed, then choose Send.

For a correction, name the task and what changed:

For the sign-in fix, keep the button label unchanged. Fix only when it becomes enabled.

Foreman can pass a correction to work already running. You do not need to start a duplicate task. If you no longer want the work, ask Foreman to stop that task and wait for confirmation; closing an app window is not a stop request.

Find who acts next

Open Tasks, select the task, and read its next step before starting another attempt. The task's label describes where attention belongs:

  • Not started: the work has not started. Check Status for computer or capacity requirements if it stays there.
  • Being built: a worker is assigned to the work. Use Status to distinguish recent activity from time since assignment.
  • Needs your answer: read the question and reply. A worker cannot decide a consequential product choice for you.
  • Ready to review: open the result and say what is missing or needs changing.
  • Done or Dropped: look in Closed for the record and its links.

You can also reply from a task's reply field when it is available. If it opens the conversation instead, send your answer there.

Review a document or page

Open the task's result link and check that it answers the request. A document can be a comparison or a proposal; its publication does not mean a proposed feature has been implemented.

Ask Foreman to revise the result, naming the part to change. For comments on the result itself, see Artifact comments. Use sharing before sending the link to someone else: receiving a link does not necessarily give that person access. Revisions can keep the same link with a new version.

Follow a code change through delivery

Open the linked pull request to inspect the change, checks, and any limits reported by the worker. Factory distinguishes two merge paths:

  • Routine: the pull request can merge automatically after its required review and checks pass, under the repository's rules.
  • Needs author: the pull request names a decision for you. Answer that question so work can continue; do not approve an unrelated design instead.

Review, merge, release, and verification are different steps. A merged change may still need a release or installation before you can use it. The project's configured delivery steps determine what follows the merge; Factory does not give every repository the same release schedule.

When Foreman closes a delivered task, the task can show Delivered and checked with the outcome it verified. If the result is still wrong, reply with the missing behavior. A delivery-closed task accepts that feedback so Foreman can reopen the work. A task you explicitly marked done or dropped does not offer the same reply path; bring the task back to Foreman in chat.