AI Agent Hub
Back to skills
Efficiency Booster: Four-Step Thinking Framework icon

Efficiency Booster: Four-Step Thinking Framework

Office Efficiency Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Follow https://skillhub.cn/install/skillhub.md and install @user_aad6add3/efficiency-booster.

About this skill

Problem it solves

When tasks are complex, boundaries are unclear, or the execution path keeps shifting, the failure mode is often not lack of effort but lack of structure: reports get started before the goal is clear, research begins before the scope is fixed, and work piles up while deadlines slip. This skill helps you settle the important questions before execution: whether the task is worth doing, what done means, who owns the result, where the boundary is, and how long to allow.

How it works

It organizes the workflow into a four-step loop: clarify, deconstruct, optimize, and review. First, use 5W1H and worst-case thinking to confirm purpose, completion criteria, ownership, timing, scope, and method. Second, use WBS and MECE checks to break a large task into actionable items that can be executed without ambiguity. Third, apply the Pareto principle, remove low-value fake actions, and set stop-loss limits so uncertain work does not consume the schedule. Finally, use PDCA and root-cause analysis to turn experience into reusable SOP steps. It can also produce a Word document plan containing problem framing, task breakdown, path optimization, and review templates.

Fit and limits

This is useful for project execution, report writing, process improvement, team coordination, and personal workflow design, especially when you need to reduce rework, prioritize higher-impact work, and control time spent on uncertain tasks. It is a thinking framework, not an automated executor: it will not make business decisions for you or remove missing domain knowledge. If the direction is unclear or resources are missing, the first step is still to confirm scope and make the decision.

Use Cases

  • After receiving a complex industry report, define goal, scope, and done criteria, then break work into research, outline, and drafting.
  • When projects keep slipping, map task dependencies and set stop-loss limits for research or technical validation.
  • Before quarterly review, use PDCA to check goal gaps, attribute blockers to method, resources, or attitude, and codify SOPs.
  • When team roles are blurred, define owner, executor, collaborator, and approver permissions to reduce handoff friction.

Best For

  • Product or consulting writers who must deliver weekly reports and industry analyses: clarify scope and completion criteria before drafting.
  • Project managers running parallel projects: define dependencies, owners, and milestones before scheduling to reduce delays.
  • Operations or content creators who fall into fake busywork: identify excessive preparation and set stop-loss limits for research.
  • Team members or knowledge managers who need to codify workflows: turn post-task analysis into SOPs, checklists, and templates.