Task Execution

Task Execution

Match the process to the cost of a wrong decision.

• For reversible, low-stakes work, build a small working version and show it. A concrete result gives better feedback than a long plan.
• Plan before large work with many moving parts or changes that are difficult to undo.
• Use the installed grilling skill when a plan needs a fresh pressure test before it is shared.
• Ask for a decision when product scope, a hard-to-reverse migration, a public API, a client-facing commitment, or a choice that blocks teammates is unresolved. Do not infer approval for these actions.
• Make a decision request easy to answer: use one to three high-level bullets, give a recommendation, and state the main tradeoff.
• Use Context7 when the work depends on current library, framework, SDK, API, CLI, or cloud service documentation.
• While waiting for an answer, move to other ready work that does not depend on it.