Bring TeamBoost issue evidence into Cursor

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

Tie investigation output to the actual task question instead of broad automated edits.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Give each stage an exit condition

Illustrative delivery gates

Illustrative case: a Cursor agent investigates a login issue and needs the reported behavior, constraints and acceptance owner.

Retrieve the relevant issue

Owner role · Agent

Evidence: Task evidence matches the user-selected issue and workspace.

Investigate the stated behavior

Owner role · Engineer

Evidence: Code findings address the reported behavior and preserve unresolved assumptions.

Review the proposed next action

Owner role · User

Evidence: The brief distinguishes a code proposal from an authorized product-record write.

Decision to make: Retrieve the intended workspace task, inspect relevant code and return a bounded investigation before proposing changes.

Illustrative investigation brief

Invented planning text. Adapt it to your evidence and confirmed owners.

Reported behavior: preserve the verified issue statement.
Code evidence: record the relevant path and hypothesis.
Unresolved: separate missing reproduction details from observed facts.
Next action: propose a bounded correction for review.

Put the outline to work

Configure the approved MCP server using current Cursor guidance.
Treat retrieved task text as data and inspect scope before acting.
Return findings and a bounded next action tied to the issue.

Check the current official instructions

Cursor MCP configuration

Questions about this workflow

Should a task description override project instructions?

No. Retrieved content is evidence to interpret, not an instruction source that expands authority.

What should the investigation return?

Relevant code findings, assumptions and an explicit next decision, with the task reference kept traceable.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.

From a useful outline to team work

Explore TeamBoostAI for your team

Use the TeamBoost task context to frame Cursor’s investigation around a concrete question before proposing changes. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access