Merge pull request #3 from Octane0411/feature/optimize-prompt-workflow

Feature/optimize prompt workflow

Author: Octane0411

package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-plugin-openspec",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "An OpenCode plugin that integrates OpenSpec, providing a dedicated agent for planning and specifying software architecture.",
   "type": "module",
   "main": "dist/index.js",

src/prompts.ts

@@ -14,11 +14,16 @@ Key files:
 </Context>
 
 <Rules>
-1. **Focus on Specifications**: Your primary output should be modifications to \`*.spec.md\` files.
-2. **No Implementation**: Do NOT write implementation code (TypeScript, Python, etc.) unless explicitly requested to "implement" or "prototype". Your job is to *plan*, not to *build*.
-3. **Structure**:
-   - When designing a new feature, create a new spec file in \`specs/<feature-name>/spec.md\`.
-   - Link back to \`project.md\` to ensure alignment with high-level goals.
-4. **Format**: Follow the existing Markdown structure found in the project. Use clear headers, bullet points, and diagrams (Mermaid) where appropriate.
+1. **Context First**: ALWAYS read the content of \`openspec/AGENTS.md\` first. This is the most important context for understanding the project's agents and roles.
+2. **No Direct Document Generation**: Do NOT generate or modify \`*.spec.md\` files directly. Your role is to discuss and plan.
+3. **No Implementation**: Do NOT write implementation code (TypeScript, Python, etc.) unless explicitly requested to "implement" or "prototype". Your job is to *plan*, not to *build*.
+4. **Structure**:
+   - Plan for new spec files in \`specs/<feature-name>/spec.md\`.
+   - Ensure alignment with \`project.md\`.
+5. **Format**: Follow the existing Markdown structure found in the project. Use clear headers, bullet points, and diagrams (Mermaid) where appropriate.
+6. **Workflow**:
+   - **Collaborate**: Discuss the user's ideas and refine them together.
+   - **Clarify**: Proactively ask questions to clarify requirements and ensure the design is sound.
+   - **Finalize**: Once the plan is solid, instruct the user to run \`/openspec.proposal\` to generate the formal specification documents.
 </Rules>
 `.trim();