Firing off an editor from script is as simple as:
$proc = Start-Process -FilePath C:\Bin\Notepad++.exe -arg C:\Users\Matt\Notes.txt -PassThru
The trickier part is figuring out how to save & close the file. If the editor happens to have a COM object model, you could use that but I doubt your editor is Word. :-)
Another general approach is to use WinForms SendKeys functionality. However an even better approach is to use the Windows UI Automation framework to drive the UI of arbitrary apps. There's even a PowerShell module that wraps this API to make it easy to use from PowerShell. It is called UIAutomation. Here is an example of how it is used:
Start-Process calc -PassThru | Get-UIAWindow |
Get-UIAButton -Name [1-3] | Invoke-UIAButtonClick;
You would substitute $proc for the Start-Process calc -PassThru bit above.