Projects

Create a project

Workspace owners and admins create projects, with New project in the project menu, which opens from the project’s name in the top bar. Give it:

Name

Up to 200 characters.

Key

Up to 10 letters or digits, made from the name unless you choose your own. It starts every job’s key, so the project WEB has jobs WEB-1, WEB-2 and on. A key can’t be changed later.

What’s it for

Optional. A line about the project, which Scout uses to draft its brief, skills and statuses for you.

You become the project’s owner. A new project’s board has the statuses Backlog, To do, In progress, Done and Dropped, and new jobs land in Backlog.

Project settings

Open the project menu and choose Project settings. Workspace owners and admins, and the project’s owners and project admins, can change what is there. Changes save themselves. Workspace viewers can read the settings but not change them.

The brief

The brief says what the project is for, in up to 10,000 characters. Every agent working in the project reads it, so it is the best place for context agents should always have.

Workspace owners and admins can ask Scout to draft the brief, the skills Scout will hold, and the project’s statuses. Nothing is saved until you accept each part, and statuses are offered only while the board has no jobs. Drafting spends credits.

Once the brief is saved, workspace owners and admins can use Propose first jobs to ask an agent to suggest a first set of jobs from it.

How agents work here

Who shapes new jobs

The agent that takes a first look at each new job and suggests its acceptance criteria, or each job’s own agent.

When a result is rejected

Whether the job waits for someone to run it again, or runs again straight away.

Pictures in documents

Whether reports and memos get pictures as well as decks. They do by default.

Before a person judges a result

Nobody checks it, the agent that did the work checks it, or another agent does, with up to five tries before it stops.

Statuses

A project’s statuses are the columns of its board. Each status is one of four kinds:

Not started

Work nobody has begun. New jobs land in one of these.

Underway

Work in progress.

Finished

Moving a job here finishes it.

Dropped

Moving a job here drops it. Every board has exactly one, which you can rename.

• Under Statuses on the settings page, add not started, underway and finished statuses, and use a status’s menu to rename it, change its colour or kind, choose it as where new jobs land, or move or delete it.
• A board can have up to 24 statuses, and keeps at least one not started and one finished status.
• Deleting a status moves its jobs to another status of the same kind, and deletes the rules that name it.
• Rules on a status can require a sign-off or a condition before a job moves into it. See Sign-off on board moves.

Members

The project’s owners and project admins manage its members, from People beside the settings. Add someone already in the workspace by name or email, as a project admin, an editor or a viewer. Removing someone stops them seeing the project’s jobs, and they stay in the workspace. A project always keeps at least one owner. See Project roles.

The settings page also holds the project’s request form, under From outside, and its GitHub repositories. See Intake forms and GitHub.

Delete a project

Workspace owners and admins can delete a project once it has no jobs, routines or documents left, from the menu on its settings page. Its board, its rules and its request form go with it.