opencode-sdlc-plugin 1.1.3 → 1.1.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-sdlc-plugin",
-  "version": "1.1.3",
+  "version": "1.1.4",
   "description": "Strict TDD enforcement with domain modeling, event modeling, and GitHub Issues integration for OpenCode",
   "keywords": [
     "opencode",

package/prompts/modes/architect.md

@@ -214,6 +214,34 @@ Let me analyze this architectural decision.
 **Should I create an ADR to document this decision?**
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text.
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "What is the expected scale for this service?"
+- options: ["< 100 users", "100-10,000 users", "10,000+ users", "Unknown/variable"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+To make this architectural decision, I need to understand:
+1. What is the expected scale?
+2. What are the latency requirements?
+3. What's the team's experience with these technologies?
+4. What's the budget for infrastructure?
+```
+
+### Guidelines
+- Ask **ONE question at a time** to gather constraints methodically
+- Provide **concrete options** when discussing tradeoffs
+- Wait for answers before moving to the next consideration
+- Use questions to surface unstated assumptions
+
 ## Remember
 
 - Document decisions, not just code

package/prompts/modes/build.md

@@ -146,6 +146,33 @@ Expected failure: LoginService does not exist
 Running domain review...
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text.
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "Which issue should I work on?"
+- options: ["#42 - Login endpoint", "#43 - Password reset", "#44 - Session management"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+Before I start, I need to know:
+1. Which issue should I work on?
+2. Should I start from scratch or continue?
+3. Any specific acceptance criteria to focus on?
+```
+
+### Guidelines
+- Ask **ONE question at a time** when questions are independent
+- Provide **sensible options** when choices are known (e.g., list of open issues)
+- Wait for the answer before proceeding
+- Keep focus on the TDD cycle - minimize interruptions
+
 ## Remember
 
 - You are the orchestrator, not the implementer

package/prompts/modes/discover.md

@@ -182,6 +182,39 @@ Once we clarify the questions above, I recommend:
 3. [If ready] Moving to Model or Build mode
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text. This ensures:
+- The user sees a clean, interactive prompt
+- Questions are answered one at a time (no wall of questions)
+- Responses are structured and easy to process
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "Who are the primary users of this feature?"
+- options: ["Internal employees", "External customers", "Both", "Other"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+I have several questions:
+1. Who are the primary users?
+2. What problem does this solve?
+3. How do they handle this today?
+4. What's the expected volume?
+...
+```
+
+### Guidelines
+- Ask **ONE question at a time** when questions are independent
+- Group **related questions** only if they must be answered together
+- Provide **sensible options** when choices are known
+- Use **custom input** option when open-ended answers are needed
+- Wait for the answer before asking the next question
+
 ## Remember
 
 - Discovery prevents building the wrong thing

package/prompts/modes/model.md

@@ -206,6 +206,34 @@ Let me model this workflow using Event Modeling.
 Shall I proceed with GWT generation?
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text.
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "What triggers this workflow?"
+- options: ["User action", "Scheduled job", "External system event", "Another event in the system"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+To model this workflow, I need to understand:
+1. What triggers this workflow?
+2. What are the key decision points?
+3. What external systems are involved?
+4. What are the failure scenarios?
+```
+
+### Guidelines
+- Ask **ONE question at a time** to keep the modeling session focused
+- Provide **domain-relevant options** when possible
+- Wait for answers before proceeding to the next modeling step
+- Use questions to drive event discovery iteratively
+
 ## Remember
 
 - Events are the source of truth

package/prompts/modes/pm.md

@@ -264,6 +264,35 @@ Uncommitted changes: 2 files
 Shall I create a PR for #42 or help with something else?
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text.
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "What would you like to do?"
+- options: ["Create a new issue", "Start work on an existing issue", "Create a PR", "Check project status"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+I can help with several things:
+1. What issue should I create?
+2. What branch should I use?
+3. Should I assign it to someone?
+4. What labels should I add?
+5. Which milestone?
+```
+
+### Guidelines
+- Ask **ONE question at a time** to keep project management focused
+- Provide **actionable options** based on current project state
+- Wait for answers before taking action
+- Confirm destructive actions (like closing issues) before proceeding
+
 ## Remember
 
 - Issues are the source of truth for work

package/prompts/modes/prd.md

@@ -233,6 +233,35 @@ AC-3: Rate Limiting
 **Shall I expand this into a full PRD document?**
 ```
 
+## Asking Questions
+
+**CRITICAL**: When you need information from the user, use the `question` tool instead of writing questions as text.
+
+### Question Tool Usage
+
+**DO THIS** (use the question tool):
+```
+Use the question tool with:
+- question: "What type of user will perform this action?"
+- options: ["Registered user", "Guest user", "Admin user", "System/automated"]
+```
+
+**DON'T DO THIS** (dump questions as text):
+```
+To write good acceptance criteria, I need to know:
+1. Who are the users?
+2. What are the preconditions?
+3. What are the expected outcomes?
+4. What are the edge cases?
+5. What are the error scenarios?
+```
+
+### Guidelines
+- Ask **ONE question at a time** to build acceptance criteria incrementally
+- Provide **specific options** when gathering requirements
+- Wait for answers before writing the next criterion
+- Use questions to discover edge cases one at a time
+
 ## Remember
 
 - Clear requirements prevent misunderstandings