Prompting Is Dead. Long Live the Loop.

A Realistic First Migration

Before (prompting): Every PR: manually ask the agent to fix CI, re-prompt after each failure.

After (looping): /loop 5m check my PR, address review comments, and fix failing CI. Add a skill that says: never mark CI fixed without re-running the full pipeline. Add /goal all checks green, stop after 10 tries for stubborn failures.

Run it for a day. Note where it stalls-too eager merges, wrong files touched, missed edge cases-and encode those failures into skills. That iteration is the product. The prompt was never the product.

The Bottom Line

Prompting isn’t worthless. It’s incomplete. The best teams still write clear instructions-but they’ve stopped treating a single response as the finish line. They design loops: agents that gather context, act, verify, and repeat until a condition they didn’t have to guess at is satisfied.

Prompting is dead as the default paradigm for serious agentic work. Not because words stopped mattering, but because outcomes beat utterances. The loop is here.

Your job moved upstack: define what done means, how to verify it, when to run, and when to stop. Start with one loop this week. Hand off one thing you used to re-prompt manually. Watch what breaks. Fix the system, not just the output. That’s not prompt engineering. That’s engineering.

Inspired by Anthropic’s Claude Code team and their guide: Getting started with loops. Examples use Claude Code primitives (/goal, /loop, /schedule, skills, workflows); the loop mindset applies to any agentic coding tool.

Tags: AI, Agentic AI, Prompt Engineering, Claude Code, Software Development, Developer Productivity, LLM, Automation

Estimated read time: 8 min