Skip to main content
Not every ask needs consult first, and not every ask should Execute immediately. Clear goals with endless discussion slow you down; unclear rules with early generation cause expensive rework.

​
Before you start, ask two questions

  1. Am I clear on what to build?
  2. Does it include business rules only I know?

​
1. Clear goal, no special rules → Execute

Common flows with clear pages and outcomes — e.g. a booking form (name, phone, time) that notifies an admin.

​
2. Unclear goal → Free consult first

“I want a membership system” without points rules, tiers, or benefits — discuss scope and the first slice in consult.

​
3. Clear goal, proprietary rules → Explain first

E.g. store submit → manager approve → HQ confirm. State the rules fully, have Su Xiaoqiang restate them, then generate.

​
4. Unclear direction and rules → Shrink the task

Don’t generate a kitchen-sink v1. Consult to lock one core flow, then add features. Before Execute, spend a few seconds: do you need action, or clarity? Consultation guide

​
Original WeChat post

Original WeChat post