菜单
Root-cause discipline for bugs, test failures, and unexpected behavior. Embedded grill on the hypothesis before writing fix code. Use when encountering any bug, failing test, or behavior that doesn't match expectation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Clarify intent, propose 2-3 approaches, embedded grill to stress-test the chosen path. Use before any creative work — new features, components, behavior changes, design questions. Mockup-only requests use mockup quick-mode (no spec/plan ceremony).
Manage long-session context to prevent drift and degradation. Strategies for proactive summarization, branch isolation, and /clear decisions. Invoke when context feels heavy, when accuracy starts slipping, or proactively after a major phase boundary. Addresses the
Design a module's interface using parallel sub-agents producing radically different designs ("design it twice"). Compare on depth, simplicity, and efficiency. Embedded grill on the synthesized choice. Use when designing a new API, exploring interface options, or deciding the shape of a refactor before writing code.
Execute a written implementation plan task-by-task with inline verification. Stop and ask on blockers. No forced sub-skill chains. Use when a plan exists and you're ready to implement.
Extract canonical domain terms into CONTEXT.md. Flag ambiguities (same word, different meanings) and synonyms (different words, same meaning). Re-invoking updates the file in place. Use when authoring or updating CONTEXT.md, or when a new domain term emerges in conversation.
Single entry-point orchestrator for the PolyFlow loop. The user says "let's polyflow this", "use polyflow", "polyflow this idea", "run this through polyflow", "implement with polyflow", or any similar phrasing — and you walk the loop (brainstorm → plan → execute → tdd → iterate → STOP) end-to-end, announcing each step, respecting checkpoints, and stopping where the user retains control. Trigger keywords: "polyflow", "let's polyflow", "use polyflow", "polyflow this".
| name | polyflow-debug |
| description | Root-cause discipline for bugs, test failures, and unexpected behavior. Embedded grill on the hypothesis before writing fix code. Use when encountering any bug, failing test, or behavior that doesn't match expectation. |
See polyflow meta-skill.
SKIP when: the cause is obvious and the fix is one line. Don't ceremonialize trivial bugs.
State the hypothesis explicitly:
"I think the bug is in : because when X happens, Y is supposed to happen but instead Z does."
A vague "probably the validation" is not a hypothesis.
Before writing any fix, ask:
Add an instrument (log, breakpoint, test assertion) that proves the hypothesis right or wrong. Watch the instrument fire. If it doesn't, the hypothesis is wrong — go back to step 2.
The test should fail because the bug exists. This is a vertical-slice TDD application — see polyflow-tdd.
Fix where the root cause originates, not where the symptom appears. If the fix is far from the symptom, leave a comment explaining the WHY (this is one of the few cases where a code comment earns its keep).
Run the test. Run the broader suite. Confirm no regressions.
polyflow-executing-plans. If standalone debug, report what was fixed and STOP. The user decides whether to commit or take further action.polyflow-improve-architecturepolyflow-brainstorming to align on intended behavior