Workflow collection

Agents and MCP workflow collection

Choose the actual decision you face. Each guide includes an illustrative case, evidence-led tasks and a downloadable manual work brief.

13 guides in this collection. Examples are planning resources; account functionality must be verified separately.

Use the native TeamBoost CLI and its agent guidance to turn a known task into a scoped engineering brief.

Prepare a remote MCP task-context workflow with the right transport, workspace binding and allowed tool purpose.

Use current task evidence alongside a code investigation while preserving the boundary between issue data and agent instructions.

Use semantic task search for a topic question and preserve the difference between relevant matches and an exhaustive attribute list.

Preserve status, owner and project constraints when a request needs a structured set of TeamBoost tasks.

Identify how the deployed TeamBoost MCP authentication mode binds a request to the intended organization.

Review generated task scope, owner assumptions and distinct items before invoking TeamBoost’s task-creation tool.

Confirm an existing task and the exact requested change before allowing an agent’s update tool to alter it.

Separate a semantic indexing gap from missing task persistence, workspace mismatch or an incorrect query.

Separate user intent, client tool selection and source-enforced permissions before enabling task-writing agent workflows.

Choose between native command execution with packaged guidance and remote MCP tools based on the actual workflow contract.

Use a manual MCP member-resolution guide to distinguish similar names, confirm the intended teammate and review responsibility before a task write.

An investigation brief should distinguish reported facts, possible explanations and missing acceptance evidence before an agent starts changing code.