Workflows, gates and the board
Shape how work moves with a workflow, decide at its gates, and follow every task and run live on the board.
A workflow is the path a piece of work follows, from idea to merged pull request, with gates where people decide. A run is one task moving through a workflow. The Board shows every task in your org, and its cards move on their own as runs start and pull requests merge.
Before you start:
- Board is in the left rail when your org has the
workmodule. - Workflows is in the rail when your org has both the
workandlibrarymodules, and never for a guest. When your plan doesn't include it, the page says Workflows isn't enabled and an admin can ask about turning it on. - A run is driven by a session, and sessions start in the desktop app.
How do I make a workflow?
Open Workflows and choose New workflow. With no workflows yet, choose Start from a template.
Pick the template closest to how your team works and choose Use template, or choose Start blank for an empty canvas.
Shape it on the canvas. Add step offers each step type, and the inspector on the right edits the step you select.
Fix what the Checks panel lists. It names each problem and warning, and opens the step it is about.
Choose Publish, pick Patch, Minor or Major, and write a summary. If you don't approve library changes yourself, the button says Propose change and an approver reviews it first. See propose a library change.
A workflow is a library asset, so it has versions. Versions on the list shows them, and a run stays on the version it started on.
The step types
| Step | What it does |
|---|---|
| Skill | Runs a skill from the library |
| Agent | Hands the step to an agent |
| Prompt | Says what to do in your own words |
| Check | Runs a command that must pass, and can loop back when it fails |
| Decision | Chooses a route |
| Checkpoint | Stops until the author confirms |
| Gate | Stops until a person approves |
| Parallel | Runs steps together |
| Workflow | Includes another workflow |
| End | Finishes the workflow |
Besides Canvas, the editor has two views. YAML shows the workflow file itself. Dry run walks the route through it and shows what the assistant gets in each harness. Nothing runs there.
How do I set who approves a gate?
Select the gate step. Under Who approves, choose Add an approver and make each one a role (owner, admin, lead, maintainer or contributor), a team, or a person by email. Set Quorum to the number of approvals the gate needs. Tick Not the author so that whoever owns the run or one of its sessions can't approve their own work.
Shows sets what approvers read before they decide: the diff, a file, or a task document such as the spec. If changes are asked for, go to sends the run back to an earlier step.
How do I run a workflow on a task?
Open the task from the Board and choose Run workflow.
Pick a published workflow, fill in any inputs it asks for, and choose Start the run.
The run waits for a session. On the web, choose Open in desktop to open the task in the desktop app and start one there. Inside the desktop app, Run workflow opens the new-session composer directly.
The session reports each step as it goes. In a session, your assistant uses run_step for steps, gate_request to ask for an approval, checkpoint_request to stop and ask you, and run_status to see where the run stands.
Runs, from the Workflows page, lists every run with its status: Running, Waiting, Blocked, Failed, Done or Canceled. A run's page shows its steps, its open gates and its log. Someone who may act on the run can choose Resume, Move next (with a reason, which goes in the log) or Cancel run.
How do I decide a gate?
Open the gate from its run, with Open the gate.
Read what it shows. A diff or file is pinned to a commit, and a document is pinned to a version.
Choose Approve, Request changes or Reject. Request changes needs a note saying what to change. Reject blocks the run until the session asks again or someone cancels it.
Only a person signed in at the web or desktop app can answer a gate. A session, the CLI or a machine can ask for an approval, but never give one. A gate that says Waiting for the approvers means only the people it names can answer.
Gates may be advisory here
A run shows this note when one of its sessions isn't running blocking hooks, or couldn't reach EasyCode to check its gates. A person's Create PR in EasyCode still stays held while a gate is open.
A checkpoint is lighter than a gate: the session asks you in the chat, and you answer there or on the run page with Confirm or Request changes. It passes no gate.
How do I use the board?
The Board has a Board tab and a Progress tab. The board shows tasks in columns: Backlog, Blocked, To do, In progress, In review and Done. Show canceled adds Canceled.
- Kanban or List switches the layout.
- Filters narrows by product, teamspace, assignee, source, type, status, label, dates, or Has a spec. Saved views keeps a set of filters under a name.
- New task creates a task on a product. Link a ticket makes it follow a Jira or Linear ticket, which then owns its title and status. See Jira and Linear.
- On a task, Start task begins it as a session, Move changes its column, and Edit changes its title, assignee or size. Documents holds its spec, plan and notes. See write a spec with your team.
A guest sees tasks in their teamspaces and products only. On a phone, the board is read-only.
When runs stop
EasyCode staff can switch off workflow runs for an org with runs. Runs then can't start or move on, and the board still works. See kill switches and modules.
Something wrong or missing? Suggest a change
Set up knowledge for a repo
Let EasyCode scan a repo and map your org's code, so every session can read how the repos fit together before it changes anything.
Write a spec with your team
Write a spec together on a task: live editing, comments, review requests and versions, then hand it to a session to build.