Performance Issue Analysis Workflow

Strong dependencies: clarifying-question-discipline (hard active-questioning discipline) and known-issue-research (known performance-pattern quick search, §2.1). If either is missing, abort and print the install command (npx skills add FuDesign2008/open-skills -g --skill '*' --yes).

Scope

This workflow is responsible for finding the root cause of a performance bottleneck: who triggered what expensive operation, and under what conditions. Once the root cause is confirmed, it can be used to design a fix, implement code/config optimizations, and verify the result. How to release, roll out, or ship the fix is out of scope — that is decided by the project itself.

Trigger Recognition

All triggers start with 「性能」 (performance), which makes them easy to recognize and remember. Saying a trigger word alone, or using the 「trigger + colon + space + description」 form, enters this workflow or the corresponding stage. When a colon is used, both the colon and the space are language-agnostic (Chinese or English punctuation both work).