{"slug": "workflow-packaging-audit-prompt", "title": "Workflow Packaging Audit Prompt", "summary": "An engineer has developed a workflow packaging audit prompt that systematically identifies recurring manual tasks suitable for automation. The prompt prioritizes evidence from recent Codex sessions, memories, and rollout summaries, requiring candidates to have occurred at least twice or be costly to repeat manually. It directs the creation of only high-confidence assets like skills, subagents, or automations, while skipping speculative or poorly evidenced workflows.", "body_md": "Review my recent work from the past 30 days, or the full available record if there is less than 30 days of history, and find recurring manual workflows that are good candidates to package.\n\nPrioritize evidence in this order:\n\n- Recent Codex sessions and task summaries.\n- Codex Memories and rollout summaries, especially where the same pattern shows up across more than one session.\n- Chronicle, if it is available, to discover repeated work outside Codex. Use Chronicle only as a discovery layer; verify anything important in the appropriate source system when possible.\n- Existing skills, custom agents, and automations, so you improve or reuse what already exists instead of creating duplicates.\n\nSearch broadly for work that is repeated, slow, error-prone, context-heavy, or better handled through a consistent process. Include workflows from coding, research, writing, planning, communication, operations, analysis, and personal administration.\n\nOnly move a candidate forward when it meets these conditions:\n\n- it has happened at least twice, or it is clearly likely to happen again and would be costly to repeat manually;\n- it has stable inputs, a repeatable process, and a clear output or stopping point;\n- packaging it would meaningfully improve speed, quality, consistency, or reliability;\n- it is not already covered well enough by an existing asset.\n\nChoose the smallest useful package:\n\n- Skill: a reusable workflow, checklist, or playbook.\n- Custom subagent: a focused specialist role or bounded investigation task that is useful to delegate.\n- Automation: a scheduled or recurring check, report, reminder, or monitor.\n- Extend existing: improve something that already covers most of the need.\n- Skip: leave it alone if the work is too one-off, vague, sensitive, poorly evidenced, or already handled.\n\nStart by producing a compact shortlist. For each item, include:\n\n- the recurring workflow;\n- supporting evidence and dates;\n- frequency and confidence;\n- recommended form: skill, subagent, automation, extend existing, or skip;\n- why it is or is not worth packaging.\n\nAfter the shortlist, create only the high-confidence missing items. Keep each one narrow, practical, source-aware, and easy to validate. Do not create speculative, overlapping, or overly broad assets.\n\nFinish with:\n\n- what you created or extended;\n- what you intentionally skipped;\n- what needs more evidence before it should be packaged.", "url": "https://wpnews.pro/news/workflow-packaging-audit-prompt", "canonical_source": "https://gist.github.com/surim0n/6b2f469a0acddad25ded88518d61c8a1", "published_at": "2026-05-24 13:57:29+00:00", "updated_at": "2026-05-25 23:04:25.004376+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "ai-products", "ai-research", "ai-infrastructure"], "entities": ["Codex", "Chronicle"], "alternates": {"html": "https://wpnews.pro/news/workflow-packaging-audit-prompt", "markdown": "https://wpnews.pro/news/workflow-packaging-audit-prompt.md", "text": "https://wpnews.pro/news/workflow-packaging-audit-prompt.txt", "jsonld": "https://wpnews.pro/news/workflow-packaging-audit-prompt.jsonld"}}