Skip to main content
Tasks gives project engineers a focused view of assigned work across projects. Open a task to see its project context, requirements, dependencies, files, and available Chat.

Start a task

  1. Confirm the intended outcome and acceptance criteria.
  2. Check whether predecessor tasks and customer decisions are complete.
  3. Read linked source files and recent project activity.
  4. Verify the account and target system before using tools.
  5. Break ambiguous work into an investigation step and an execution step.

Work with Chat

Ask mode is a good place to investigate, compare configurations, draft a change plan, or prepare a PSA note. If execution is allowed:
  • switch to Full access only for the required action;
  • review the target and proposed effect;
  • approve protected calls individually;
  • verify the result in the connected system;
  • return to Ask mode for the next reasoning step if appropriate.

Document the result

A useful task note records:
  • what changed;
  • where it changed;
  • the evidence that it succeeded;
  • any deviation from the plan;
  • any customer or project impact;
  • follow-up work and its owner.
When supported, Forge can help draft or post a note to the PSA. Review the note as an operational record, not as a transcript of the conversation.

Complete or hand off

Mark the task complete only when its acceptance criteria are met and required writebacks are visible. If blocked, state:
  1. the blocker;
  2. the evidence gathered;
  3. the decision or access required;
  4. the specific next owner.
Keep reusable discoveries out of a one-off task note. Capture them in the relevant project template, skill, runbook, or account context so the next project can benefit.