The MySpec edit for brownfield workflow changes the spec files of a Brownfield project, checking each change against your code. In the picker it is MySpec edit-brownfield (v1): “Edit specs against an existing codebase → describe changes → review edits.”
At a glance
- Best for: Changing proposals, requirements deltas or tasks for an existing codebase
- Project type: Brownfield (or Auto)
- Steps: Reference → Describe → Review, reading your code before each round
- Files: The spec files you reference
Before you start
The AI reads the code related to your change before it edits any spec, so
connect your codebase first: run the local MCP server’s reverse command, or
mount the folder in your browser’s Local Workspace. See
Let MySpec read your code.
If it can’t read your code, the AI asks you to connect it and waits.
Steps
The steps are the same as in MySpec edit, with one addition: before every round of changes, the AI reads the code behind the change. A requirement you change is checked against what the code does today, so the spec doesn’t drift from the code.
- Reference the spec files to change with
@. - Describe the change. The AI asks a short round of questions and reads the related code.
- Review each change as a diff, then Accept or Discard it.
Each new round reads the code again, so you can change the code between rounds and the next edit sees it.
Tips
- Keep your codebase connected for the whole session. Leave the
reversecommand running, or keep the browser tab with the mounted folder open. - Share only the project folder. The AI can read anything in the folder you share. See Security and privacy tips.
See Edit sessions for every button and message.