Problem
When using the /openspec-proposal slash command to describe a new feature or change, the generated proposal often instructs the AI to look only at the contents of the openspec folder. As a result, the tasks.md file contains steps like "make a plan" and "explore the codebase" as separate tasks. It doesn’t proactively inspect the rest of the repository, which makes it harder to ground the proposal in the actual code and can lead to unnecessary planning steps.
Proposal
- Update the default instructions for the proposal slash command to explicitly explore the entire repository rather than just the
openspec folder. The agent should scan relevant files and understand the current codebase before generating the proposal and tasks.
Benefits
- Proposals and tasks will be more accurate because they reflect the actual state of the codebase.
- Avoids generating generic "explore the codebase" tasks after the proposal is created.
- Aligns with the ideal workflow where the proposal and resulting specs/tasks are informed by the existing code and documentation.
Please consider enhancing the proposal workflow to support automatic codebase exploration.
Problem
When using the
/openspec-proposalslash command to describe a new feature or change, the generated proposal often instructs the AI to look only at the contents of theopenspecfolder. As a result, thetasks.mdfile contains steps like "make a plan" and "explore the codebase" as separate tasks. It doesn’t proactively inspect the rest of the repository, which makes it harder to ground the proposal in the actual code and can lead to unnecessary planning steps.Proposal
openspecfolder. The agent should scan relevant files and understand the current codebase before generating the proposal and tasks.Benefits
Please consider enhancing the proposal workflow to support automatic codebase exploration.