Add a spec editor when starting a new session

[matheusmonte]

Not every feature or engineering change can be effectively described in a single initial prompt.

My workflow typically starts with a design document that has already been discussed with the team. At that point, I usually have a clear understanding of what needs to change, why, and the expected implementation direction. In these cases, I find it more effective to write a complete specification upfront rather than iteratively providing context and monitoring changes throughout the agent's execution.

I'd like to propose a spec editor as an option when starting a new session within a project or repository.

Instead of immediately opening the chat, the user could choose "Start with a spec" and get a Markdown editor where they can structure the request before starting the agent. The spec could include things like:

• Problem and context
• Expected behavior
• Proposed changes
• Technical constraints
• Files or components involved
• Acceptance criteria

Once ready, the spec would become the initial context for the agent session.

Today, I approximate this workflow by writing a temporary Markdown file in VS Code, often using GitHub Copilot in chat mode to help refine it, and then referencing that file when starting the agent task.

In my experience, writing the spec upfront provides better context to the model, reduces follow-up questions and context switching, and allows the agent to operate more independently while I focus on other work.