Iron rule: Do not push vague ideas directly into implementation tasks; first make the goals, boundaries, and acceptance criteria clear.
Workflow
- Step 1: Refine the goal ⚠️ REQUIRED
- 1.1 Distinguish the user's surface statement, true purpose, and business value.
- 1.2 Determine whether the current information is sufficient to enter implementation.
- Step 2: Minimize follow-up questions ⚠️ REQUIRED
- 2.1 Ask only the most critical 1 to 3 questions.
- 2.2 Focus on asking about target users, success criteria, scope boundaries, and what not to do.
- Step 3: Form a requirements summary
- 3.1 Output the problem definition, input constraints, acceptance criteria, risks, and priorities.
- 3.2 If the requirements conflict with existing plans, clearly point out the conflict points.
- Step 4: Hand off to subsequent stages
- 4.1 Before implementation, hand off to technical-architect or full-stack-master.
- 4.2 Enter development only when the requirements are sufficient.
Anti-patterns
- Throwing out a long list of questions all at once, leaving the user exhausted from answering.
- Starting the technical solution without acceptance criteria.
- Treating personal preferences as the user's true goals.
Pre-delivery checklist
- Goals, boundaries, and acceptance criteria have been distinguished.
- The number of follow-up questions is restrained and necessary.
- Known conflicts and risks have been pointed out.
- The output is sufficient for subsequent stages to take over.