Cách Giao Việc và Chạy Quy Trình Tự Động

From "using a tool" → "running a system"

Core principle: Invest in setup, reduce prompting. The goal is to shift from operator to steward — you define the outcome, AI does the execution, you own the result.

3 Levels of AI Use — Pick the Right One

Rule of thumb: Start at Automation. Move to Agency only when the task is repeating, low-risk, and output is verifiable.

Step 1 — Decide What to Delegate (Delegation)

A task is right for full automation when:

• It repeats with the same pattern (3+ times/week)
• Output is verifiable — you can check it fast
• Risk of error is low, OR you set an approval gate before any real-world action

Keep for yourself: Strategic decisions, ethical judgment, relationship-building.

Step 2 — Brief It Clearly (I-T-O Formula)

Input:          Where is the data? (folder name, file, Slack channel)
Transformation: What should Claude do with it?
Output:         What does "done" look like? (format, filename, location)

"Tell Claude what done looks like." — Describe the finished file, not the steps to get there.

❌  "Make me a weekly report"

✅  "Every Friday: read Excel file in /sales-data folder.
    Extract top 3 KPIs vs. last week.
    Output: 1-page .docx report saved to /weekly-reports/
    Include a traffic-light status (green/yellow/red) per KPI."

Step 3 — Package It as a Skill

If you paste the same instructions more than 3 times → stop and build a Skill.

A Skill is a SKILL.md file that stores:

• The workflow step-by-step
• Output format and rules
• Parameters (so values are configurable, not hardcoded)

Result: Instead of a 300-word prompt each time, you just type /weekly-report and Claude loads the full workflow automatically — same result every time.

Start with 1 skill for the task you repeat most. Don't build 20 at once.

Step 4 — Schedule It (Full Automation)

Combine Skill + Schedule = automation engine that runs without prompting.

Setup via /schedule or Sidebar → Scheduled Tasks:

"Every weekday at 7:55am: pull today's calendar + priority emails.
Output: 1-page daily brief in /briefings/ folder. Draft only."

Approval gate: Always add "Draft only — don't send" for any task that affects the real world (emails, database updates). You are the final checkpoint.

Step 5 — Review Every Output (Diligence)

Automation doesn't remove responsibility. You own 100% of what gets shipped.

3-step review habit (takes 5 min):

1. Open the actual file
2. Check one number against the source
3. Follow one reasoning thread

A polished output and a wrong output look identical. The review is what catches the difference.

Source: Claude Course 2026 — NotebookLM