Skip to lesson
Exit
Cursor team workflows in a shared repo1 / 3

1 min lesson

The capability × SDLC-phase one-pager

Put this idea into your own words: "Give them a grid of which capability earns its keep in which phase of the SDLC."

Step 1 of 3

The capability × SDLC-phase one-pager

Don't talk to a VP of Engineering feature-by-feature. Give them a grid of which capability earns its keep in which phase of the SDLC. That's the artifact that turns a demo into a rollout plan.

Learn more

Advanced table

Read this top-to-bottom as a rollout

SDLC phase
Understand / onboard
Primary pattern
Explore (read-only)
Surface
IDE agent + search
Where the value lands
Faster ramp, fewer 'where does X live' interrupts
SDLC phase
Design / shape
Primary pattern
Plan a reviewable change
Surface
IDE agent + MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. (Jira/Confluence)
Where the value lands
Catch wrong approaches before code exists
SDLC phase
Implement
Primary pattern
Constrain a refactor
Surface
IDE / CLI agent
Where the value lands
Small diffs, tests as targets, house-style by rules
SDLC phase
Review
Primary pattern
Prepare human review + BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition.
Surface
Cloud / CI
Where the value lands
Cursor's June 2026 BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. update: average review about 90 seconds. Findings support human review, they don't replace it
SDLC phase
Operate / maintain
Primary pattern
Explore + constrained fix
Surface
Cloud agents (parallel multi-repo)
Where the value lands
Bulk migrations, dependency bumps, async report-back

Read this top-to-bottom as a rollout: each SDLC phase gets a primary pattern and the surface that earns its keep there. A grid like this, not a feature list, is what an engineering org hears as an adoption plan.

Bring this to the interview

If asked to 'roll Cursor out to a 200-person org,' draw the capability × phase grid and overlay the autonomy ladder.

Then close with governance: Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition. and AGENTS.md as the house style, ignore/allowlists as the blast-radius control, the ownership rule as the cultural anchor. A grid plus a ladder plus governance is what an org hears as a rollout.

Learn more

Optional practice

Practice: The capability × SDLC-phase one-pager