Steady Do: understand → clarify → implement here → verify

When this skill applies

Ordinary feature, plugin, extension, and cross-module work in an existing project, implemented and verified in this session.
The user's explicit choice wins — never switch workflows silently; if the chosen one cannot fit the task, say why and ask. Bounded and clear → quick-do; long-horizon work needing a durable plan and a separate-session handoff → plan-brief (propose it when a handoff would help but was not requested).
These workflows govern requested development work, not every explanation or read-only question. Skill instructions are in English; replies and deliverables follow the user's language (Chinese by default).

Read the complete requirement and decisions already settled in this conversation. Separate explicit requirements from open questions; investigate before modifying files.
Read project rules, README, relevant entry points and modules. Trace the real flow, reuse opportunities, affected callers, and compatibility boundaries. Expand by relevance, not a whole-repo tour or a single-function guess.
Look at the live site first (seconds, no approval): activation command and interpreter, dependency versions that actually import now, launch commands, input/output formats, config paths, and whether anything relevant is already running. Inspect instead of assuming an interpreter or system Python. One cheap look buys the avoidance of a whole round of avoidable errors — skipping ceremony is the point, skipping this is not.
Briefly state the goal, scope, non-goals, and observable completion criteria in chat. Do not create a plan document.

Use the bounded, round-based grilling method below; it is self-contained and does not require a separate skill or document workflow.