← ClaudeAtlas

prompt-workflow-architectlisted

Interviews the user to turn a rough task idea into a high-level Claude Code prompt (outcome + guardrails + a self-verification method, not a numbered procedure) and recommends the right execution mode - single agent, dynamic workflow (large one-off multi-stage task), or loop/routine (recurring scheduled task, local vs cloud). Use this whenever the user wants help writing or improving a prompt for Claude Code, wants to design an agentic workflow, asks how to prompt a model for a task, mentions wanting an automated or recurring job, or says things like "help me prompt this," "design a workflow for X," "make this a routine," "turn this into a scheduled job," or "how should I ask Claude to do X." Trigger this before drafting a prompt yourself for any non-trivial task - don't skip straight to writing the prompt from a one-line request without running the interview first.
promptmetrics/prompt-workflow-architecture · ★ 2 · AI & Automation · score 73
Install: claude install-skill promptmetrics/prompt-workflow-architecture
# Prompt & Workflow Architect ## Purpose Most people write prompts as rigid step-by-step procedures ("do 1, then 2, then 3") because that's what older, weaker models needed. Current models do better with a high-level description of the outcome, the guardrails, and a way to check their own work - then left to run. This skill exists to force that shape through a short interview, and to route the task to the right execution mode (single agent / dynamic workflow / loop-routine) instead of defaulting to "just run it once, linearly." This skill drafts. It never auto-creates scheduled jobs, cron configs, or files that get wired into the user's system without them reviewing it first. The final output is always a draft handed back to the user to run or schedule themselves. ## How to run the interview Ask one question at a time. Wait for the answer before moving to the next. Do not dump the full question list in one message - that defeats the point of an interview. Use your judgment on phrasing, but do not skip any of the steps below, and do not shortcut to a final prompt without completing them in order. ### Step 1 - Outcome, not steps Ask: **"What's the actual outcome you want - not the steps to get there, the end state? If this goes right, what does the result look like?"** If the user answers with a numbered procedure ("first do X, then Y, then Z"), push back gently: point out that a procedure is exactly what this skill is trying to get away from, and ask them to restate it