{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieng3uxeiymunuwhvsauiouu6h5mxclrskol3jsbmdxrvl3dg3sau",
    "uri": "at://did:plc:pgryn3ephfd2xgft23qokfzt/app.bsky.feed.post/3mlrxoor5v252"
  },
  "path": "/t/it-s-the-architecture-stupid-why-prompt-engineering-won-t-fix-agents/175246#post_20",
  "publishedAt": "2026-05-14T03:29:04.000Z",
  "site": "https://discuss.huggingface.co",
  "textContent": "This is a strong framing.\n\nI especially like the distinction between the model and the architecture around it. Treating the model as the execution engine, rather than the whole agent, makes the problem much clearer.\n\nThe shift from Prompt → Model → Output to Skill → Execution → Structured Output also seems important, because it turns vague reasoning into reusable operational units.\n\nOne small point I would add: clarification should also be part of the architecture, not just a prompt instruction.\n\nIf a skill does not have enough required input, the agent should not silently infer the missing context. It should enter a clarification state and ask before execution.\n\nIn that sense, “ask if unsure” should be a runtime behavior, not just wording inside a prompt.",
  "title": "“It’s the Architecture, Stupid” — Why Prompt Engineering Won’t Fix Agents"
}