# Bring TeamBoost issue evidence into Cursor

Illustrative planning brief; no automatic product import.

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

## Decision

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

## Owned work

- Retrieve the relevant issue
  - Owner role: Agent
  - Acceptance evidence: Task evidence matches the user-selected issue and workspace.
- Investigate the stated behavior
  - Owner role: Engineer
  - Acceptance evidence: Code findings address the reported behavior and preserve unresolved assumptions.
- Review the proposed next action
  - Owner role: User
  - Acceptance evidence: The brief distinguishes a code proposal from an authorized product-record write.

## Workflow

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

## Judgment

A working MCP configuration does not prove feature entitlement, task completeness or permission to execute all exposed tools.


## Illustrative investigation brief

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.


## Workflow questions

### 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.

## Product connection

Use the TeamBoost task context to frame Cursor’s investigation around a concrete question before proposing changes.

Confirm account availability before adopting this manual outline.