From first issueto verified result.

In New issue, add a title and description, then choose the assignee, starting status, and priority. Attach screenshots or a reproduction video when they clarify the work.

• Include the expected result and completion criteria in the description.
• Use Queued for ready work and Backlog for requests that still need shaping.

Work moves from Backlog and Queued through Analyze, Implement, Local validation, and Review. Blocked and completed work stays visible in the same operating view.

• Use In progress and Needs attention to focus on what matters now.
• Open a card to inspect its current stage and latest activity.

Open Run Task for the issue processing agent in Agents to find queued issues and move each one through analysis, implementation, and validation. Briar keeps every issue isolated and records its progress on the board.

• Confirm the request says “Owns the project's development and code-related work.”, then choose Run Task.
• Once the run starts, queued issues move through the workflow and continue into the required checks.

The Issue tab keeps human follow-ups and agent replies together. New constraints and questions stay attached to the work while it is running.

• Use comments for added requirements, edge cases, and review feedback.
• Move between Result, Evidence, Work log, and Status without losing the issue context.

When work finishes or reaches a review checkpoint, Result organizes the implementation, completed stages, validation summary, and next action in one view. You can understand what changed without reading the entire work log.

• Start with Work result for the implementation and validation summary.
• Use Next action to approve or request changes, then open Evidence when you need the supporting detail.

Evidence organizes artifacts and verification by workflow stage. Commands, pass states, attempts, and revisions remain available for review.

• Use Passed, Pending, and Not recorded to spot missing verification.
• Read the summary in Result, then confirm the supporting record in Evidence.

Combine one responsibility, a provider, and a model into a reusable project agent. Shape agents around real team roles such as queued issue processing, error intake, or feedback analysis.

• A specific one-sentence responsibility keeps execution scope clear.
• Use the run action on a card to perform that responsibility on demand.

Choose an agent, recurrence, time, and notification level in Schedule. Automate easy-to-miss work such as repository audits or feedback triage in your team's time zone.

• Choose weekdays, daily, or weekly recurrence to match the job.
• Important updates keeps notifications focused on moments that need human judgment.