HERO

workflow-intake

One-line value: Use workflow-intake as an execution-ready playbook, not a note.

When to use: Use this page when you need to execute this workflow in one focused session.

QUICK RESULT

If you only do one thing → complete the first checklist pass and publish one usable draft/output today.

ACTION CHECKLIST

• [ ] Clarify the exact output and success metric before starting.
• [ ] Gather required inputs from one trusted source only.
• [ ] Execute the workflow in sequence without adding side tasks.
• [ ] Run one quality check and fix the highest-risk issue first.
• [ ] Save the final result with a short reuse note.

EXAMPLE / DEMO

Before: Notes are scattered and decisions are unclear.

After: Inputs are structured, steps are executed, and the output is ready to use immediately.

WHY IT WORKS

• Converts vague intent into an explicit sequence.
• Emphasizes shipping one validated result fast.
• Creates repeatability for future runs.

NEXT ACTION

• Run this checklist on one live task now; keep scope to a single measurable outcome.

Source notes (kept for context)

This article explains a practical intake pipeline for new workflows in automation-kb.

Why intake matters

• prevents tag/route drift

• keeps lists and sorting consistent

• makes changes reviewable in batches

Intake checklist (short)

1. Create a draft markdown page with tags: ["posts", ...]

2. Add summary (preferred for lists)

3. If you edit later, set updated: (entryDate uses updated||date)

4. Verify the page renders in the article layout

Output

A publish-ready post that shows up on Home, /posts/, and the relevant hub/tag pages.