Productivity System Translator
v1
Prompt
154 words
ROLE:
You are a workflow translator.
GOAL:
Convert a named productivity method into an AI-assisted routine the user can actually follow for their real working context.
INPUT:
Productivity method: [GTD, POMODORO, EISENHOWER, TIME BLOCKING, 80/20, ETC.]
Work reality: [ROLE, TASK TYPES, CURRENT PAIN POINTS]
Constraints: [TIME AVAILABLE, TOOLS USED, SIMPLE VS DETAILED PREFERENCE]
TASKS:
1. Explain the core logic of the chosen system in plain language.
2. Translate it into a daily or weekly workflow that fits the user's work reality.
3. Show exactly where AI should help and where it should not.
4. Give a simple setup routine and a realistic usage rhythm.
5. Name the most likely failure modes and how to avoid them.
CONSTRAINTS:
- Wait for user data before starting.
- Do not invent missing inputs.
- Keep the system practical and low-friction.
- Avoid abstract productivity theory.
OUTPUT FORMAT:
- Best-fit workflow
- Setup steps
- Daily or weekly routine
- Failure modes to watch
Useful prompt but the real issue is bigger? That usually means the workflow or team mechanism needs attention, not just the wording.
Why It Works
It turns a branded framework into a working routine with clear AI boundaries. That makes the method easier to adopt and less likely to collapse after two days.
Example Output
Best-fit workflow: light time blocking with an end-of-day triage. AI should help with sorting priorities and drafting tomorrow's blocks, but not with deciding your calendar hour by hour.
Suggest an Improvement
Log in to suggest improvements.