Kunlun Growth Reporting Workflow

Problem

Reporting work often fails because goals are vague, document handoff is slow, repetitive work eats time, meeting conclusions scatter, and follow-up or review keeps getting forgotten. Plain to-do lists capture tasks but usually miss acceptance criteria, owners, deadlines, and review loops. Document tools operate in isolation, so conversion and extraction lack validation steps. If a meeting ends with notes but no owner, deadline, or follow-up, the information decays quickly.

How It Works

The skill treats reporting as a set of routed capabilities: task planning converts a goal and timebox into breakdown, priority, and schedule; document handling maps requests such as PDF, Word, conversion, or extraction to concrete steps; automation turns repetitive actions into a process and tool selection; memory enhancement generates spaced repetition and retrieval practice; meeting efficiency produces agenda, minutes, and review templates. The core workflow starts by turning a fuzzy goal into an acceptable outcome, then splits steps into chunks under half a day, ranks them with an urgency/importance matrix, and binds them to time blocks. Document work begins with the objective, prefers local tools, runs in batches, samples checks accuracy, and finishes with naming and backup. Meeting work requires an agenda before the call, time control and decision capture during the meeting, minutes within 24 hours, and tracked follow-ups.

Boundaries And Caveats

This skill is a methodology, template, and checklist system. It does not replace professional judgment, connect to external accounts or keys, or upload sensitive files. Automation scripts should be tested first to avoid accidental deletion or batch errors. Efficiency methods should be adapted to personal workflow instead of copied wholesale.