> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkato.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan a project from a brief

> Turn a project brief into linked tasks with clear outcomes and a useful review order.

export const DocImage = ({src, alt, caption, kind = "workspace", thumbnail = false, natural = false}) => {
  const paths = {
    objects: "m12 3 9 4.5v9L12 21l-9-4.5v-9L12 3Z M3 7.5l9 4.5 9-4.5 M12 12v9",
    attributes: "M4 5h16 M4 12h16 M4 19h16 M8 3v4 M16 10v4 M10 17v4",
    records: "M5 3h14v18H5z M8 7h8 M8 11h8 M8 15h5",
    relationships: "M8 8H4v8h4 M16 8h4v8h-4 M8 12h8 M10 10l-2 2 2 2 M14 10l2 2-2 2",
    views: "M3 4h18v16H3z M3 9h18 M9 9v11 M15 9v11",
    importing: "M12 3v12 M8 11l4 4 4-4 M4 16v5h16v-5",
    workspace: "M4 4h16v16H4z M4 9h16 M9 9v11",
    navigation: "m5 5 14 5-6 3-3 6-5-14Z",
    team: "M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2 M16 4a4 4 0 0 1 0 8 M22 21v-2a4 4 0 0 0-3-3.87 M13 7a4 4 0 1 1-8 0 4 4 0 0 1 8 0Z",
    tasks: "M9 6h11 M9 12h11 M9 18h11 M3 6l1 1 2-2 M3 12l1 1 2-2 M3 18l1 1 2-2",
    meetings: "M4 5h16v15H4z M4 10h16 M8 3v4 M16 3v4 M8 14h3 M8 17h6",
    ai: "m12 3 2.5 6.5L21 12l-6.5 2.5L12 21l-2.5-6.5L3 12l6.5-2.5L12 3Z",
    automation: "M9 3h6v6H9z M3 16h6v5H3z M15 16h6v5h-6z M12 9v4 M6 16v-3h12v3"
  };
  return <figure className={["kato-visual", thumbnail ? "kato-visual--thumbnail" : ""].filter(Boolean).join(" ")}>
    {src ? <div className={["kato-visual-frame", natural ? "kato-visual-frame--natural" : ""].filter(Boolean).join(" ")}>
        {thumbnail ? <img src={src} alt={alt || ""} loading="lazy" decoding="async" /> : <a className="kato-visual-fullsize" href={src} target="_blank" rel="noreferrer" aria-label={`Open full-size image: ${alt || caption || "Kato guide"}`}>
            <img src={src} alt={alt || ""} loading="lazy" decoding="async" />
          </a>}
      </div> : <div className="kato-visual-frame kato-placeholder" role={thumbnail ? undefined : "img"} aria-label={thumbnail ? undefined : `Image placeholder: ${alt || caption || "Kato workspace"}`} aria-hidden={thumbnail ? "true" : undefined}>
        <span className="kato-orbit kato-orbit--outer" />
        <span className="kato-orbit kato-orbit--inner" />
        <span className="kato-visual-icon"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="1.4" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"><path d={paths[kind] || paths.workspace} /></svg></span>
        {!thumbnail && <span className="kato-placeholder-label">Image placeholder</span>}
      </div>}
    {caption && !thumbnail && <figcaption>{caption}{src && <span className="kato-visual-hint">Select the image to view it full size.</span>}</figcaption>}
  </figure>;
};

Start with a brief that describes what needs to change. Finish with a project
record and a small set of tasks that someone can pick up without attending the
kickoff. This example uses the Relio homepage project.

**Before you start:** you need access to a Projects object and permission to
create tasks. Use an existing project when one already represents the work.

<Steps>
  <Step title="Put the brief in the project context">
    Search for **Relio**, open the intended project, and review its description.
    Capture the audience, desired outcome, scope, and unresolved questions.
    Keep the current project status accurate; a drafted plan does not mean
    delivery has started.

    For this example, the outcome is a homepage brief explaining who Relio
    serves, its product benefits, the page structure, and the primary call to action.

    <DocImage natural src="/images/introduction/relio-record.png" alt="Relio project showing its description, status, linked client, and research activity" caption="The project holds the shared context. This example is On Hold even though preparation tasks exist." />
  </Step>

  <Step title="Break the outcome into reviewable pieces">
    Write a short task list before creating anything. Each task should produce
    something another person can review.

    | Task                                       | Done when                                                                  |
    | ------------------------------------------ | -------------------------------------------------------------------------- |
    | Define the homepage message for CRE teams  | A headline, supporting paragraph, and three benefits are ready for review. |
    | Map the homepage structure and primary CTA | The proposed sections and main visitor action are documented.              |
    | Capture Relio product screenshots          | The selected images illustrate the product claims in the brief.            |
    | Send the revised homepage brief            | The reviewed brief has been sent to the intended contact.                  |

    Check the existing tasks first. Reuse any that already cover these outcomes.
  </Step>

  <Step title="Create tasks with the context attached">
    Open **Tasks → New Task**. Enter the action in the title and add the
    completion conditions to the description. Choose assignees, status, and
    priority; set a due date when there is an agreed deadline.

    Use the record-link control to attach the Relio project, then select
    **Create task**. Repeat for the distinct outcomes you need.

    <DocImage natural src="/images/introduction/create-task.png" alt="Task creation form for Send the revised homepage brief with description, assignee, priority, date, and linked record" caption="Set the task details and project link before saving. Dates in this capture are examples; use your actual deadline." />
  </Step>

  <Step title="Make the review order explicit">
    Explain which work depends on an earlier result. For example, the final
    brief needs the reviewed message, page structure, and chosen screenshots.
    Put that context in the sending task's description instead of assigning
    every task the same deadline.

    If several people are assigned, name who takes the next step.
  </Step>

  <Step title="Open the saved work and check it">
    Reopen one task. Confirm that its description, assignees, dates, and linked
    project survived saving. Review the project’s **Tasks** tab to find its
    related work and check for duplicates.

    <DocImage natural src="/images/introduction/saved-task.png" alt="Saved homepage brief task with details, description, and Relio linked record" caption="A saved task should explain both the expected result and where to find the project context." />
  </Step>
</Steps>

## Check the result

A teammate should be able to explain the project outcome, find the next task,
and tell what makes it complete. If “Send the brief” only contains a vague title,
add the review criteria before handing it over.

Continue with [Hand work off to a teammate](/recipes/handoff-work) or
[Write a weekly project update](/recipes/weekly-project-update).


## Related topics

- [Hand work off to a teammate](/recipes/handoff-work.md)
- [Turn a meeting into a plan](/recipes/meeting-follow-ups.md)
- [Billing and plans](/documentation/billing-and-plans.md)
- [Get the daily brief](/api-reference/raycast/brief.md)
- [Use Ask Kato](/documentation/use-ask-kato.md)