The MySpec edit workflow changes spec files that already exist: it fixes issues, adds detail or restructures content, and you review every change before you keep it. It is the edit workflow for Greenfield projects. In the picker it is MySpec edit-workflow (v1).
At a glance
- Best for: Fixing, extending or restructuring existing spec files
- Project type: Greenfield (or Auto)
- Steps: Reference → Describe → Review, repeated as often as you need
- Files: The spec files you reference. It writes no new bundle.
An Edit session needs at least one spec file in the project. If there is none, MySpec offers Switch to Generate.
Steps
Reference
Point the AI at the files to change: type @ or select Reference a file,
or drag a spec file onto the message box. If you only name a bundle or a file,
the AI looks it up itself. Attachments you reference give it extra context.
Describe
Say what to change, in plain language. Be specific, for example “In requirements.md, add an acceptance criterion to FR-003 for expired links”.
Before each round of changes, the AI confirms what you want, usually with a short round of multiple-choice questions: which files and which points to change. Answer them as in a Generate session.
Review
The AI makes its changes and shows a Review changes card, with one row per changed file and the revisions it moves between, such as Rev 3 → 4. Open each diff, then choose Accept or Discard for each file and select Submit.
Then describe what else to change, or type /complete to finish. See
Edit sessions for every button and message.
Tips
- One topic per round. Smaller requests give smaller diffs that are quicker to review.
- Fix a few words yourself. Select Edit manually on a spec file card instead of asking the AI. See View and edit spec files.
- Revise a running Generate session with
/gobackin that session, not with an Edit session.
When to pick another workflow
In a Brownfield project, use MySpec edit for brownfield, which checks each change against your code.