Keep the business plan close to the code in Cursor.

Connect the code change to the work people need to do

An agent can find the component that displays a request and the handler that saves it. The code may not explain why only one role can approve it, what information must be present, or where the work goes next. Those decisions belong in the feature and workflow definition.

AlphaTales helps your team review that definition before implementation. Selected workflows provide the surrounding sequence. Feature specifications provide the behaviour and acceptance checks. Architecture context gives the developer the reviewed technical direction to compare with the existing application.

Bring the plan into the editor

Dev Pack lets you export selected planning files and make them available in the workspace Cursor can read. Use this when you want a specific snapshot alongside the code. Ask the agent to read the relevant files; their presence in a folder alone does not mean every detail has been considered.

For a connected route, Cursor supports MCP tools. AlphaTales's Developer Package screen provides a Cursor connection flow, and the setup guide explains the configuration and authentication. After selecting the AlphaTales project, the agent can request planning context and feature implementation details through Build MCP.

Connect AlphaTales to Cursor

Use Cursor rules for the repository, AlphaTales for the project

Cursor rules can carry instructions about conventions and how the agent should work. Keep those instructions focused and consistent with the repository. The AlphaTales plan explains what the feature must achieve, including the business rules the repository may not yet implement.

Ask the agent to inspect the code and explain the intended change before editing. If the architecture context and current implementation differ, have it identify the difference. Your team can then decide whether the plan needs updating or the code needs changing.

Cursor's documentation on rules

Choose the connection without confusing it with a plugin

A direct Build MCP connection supplies AlphaTales tools to Cursor. It does not require you to treat every tool integration as an installed AlphaTales plugin. AlphaTales's broader Agent package includes planning and build connections plus workflow skills, but package support and installation need to match the client.

For implementation from an existing reviewed plan, start with the documented Cursor MCP connection or Dev Pack export. Use the connection guide for setup; keep the solution decision focused on which planning material your team wants the agent to use.

Review one feature with its surrounding workflow

The combination is useful when you want to work in the editor while keeping decisions made by business owners available to the agent. It is especially relevant when a feature crosses roles, screens, or system boundaries.

Review the proposed diff and run the acceptance checks before moving to the next feature. Ask the agent to identify missing requirements rather than silently filling them in. When an approved requirement changes, retrieve the relevant context again or export a fresh pack so the next edit follows the same decision.