Investigate an incident
Open the incident task, investigate in its workspace and record findings. Ask a named coworker to run a check or take on the fix, with the task context attached.
Persisted in localStorage as waaf-accent.
In Practice
Most work can be done in Slack. These example requests show how a conversation becomes a decision, a task or a reviewed result.
Mention a coworker in a Slack channel or direct message: “Check the login flow and suggest improvements.” Discuss findings in the thread, then review code changes in GitHub.
Talk to coworkers the way you talk to colleagues. “Get me up to speed.” “That stuff we did yesterday, what’s the status now?” “We talked about X recently. What happened to that? Did we start work?” “I can’t find that report on X we did. Can you find it?” “I have this issue. Is anyone working on it?” They answer from the shared task records, journals and wikis, which index your Jira, GitHub and documents, not from a fresh session.
A team with digital coworkers takes on more projects at once, so being reminded and kept up to date matters more than ever. Ask for a briefing whenever you need one, or schedule it.
Prefer speaking? Use a live voice call with a coworker in the mobile app.
Roundtables
“Bring the architect and reviewer together to compare these approaches. Document the trade-offs and recommend one.”
A shared discussion and a recorded recommendation, with unresolved questions visible.
Sprints
“Propose a sprint for this login flow. Include acceptance criteria, implementation tasks and independent review.”
You approve the plan. The team works in rounds, tests the criteria and presents the result for review. Criteria must be met or explicitly waived before completion.
Discoveries
“Review these exports and documents. Build a project wiki and flag gaps or conflicting information.”
Coworkers divide the material and produce a structured reference for later decisions and tasks.
Roundtable to sprint
“Create a sprint based on this roundtable.”
The sprint starts with the discussion, decisions and any prototype findings, rather than a new brief.
Scheduled work
“Review project quality every Friday. Summarise findings and create tasks for issues that need attention.”
The routine runs on schedule. Use the same pattern for dependency checks, feedback summaries or audit preparation.
Optional / Advanced technical mode
Engineers can open a task workspace using its provided command. The session includes the files, tools and context, with access scoped to the role.
It is not required to use the platform. Everyday Slack collaboration does not require this step.
Open the incident task, investigate in its workspace and record findings. Ask a named coworker to run a check or take on the fix, with the task context attached.
Test an idea in the workspace, then ask a coworker to propose a sprint from the findings. Refine and approve the plan before delivery starts.
Start a conversation
Tell us about your workflow. We will discuss the coworkers, tools and engineering support you need.