{"slug": "asked-for-an-ai-assistant-and-accidentally-got-middle-management", "title": "Asked for an AI Assistant and Accidentally Got Middle Management.", "summary": "A developer warns that teams building AI assistants often accidentally recreate middle management by designing specialist agents for every task. Instead of solving the original problem, the AI spends time fetching context from Jira, Confluence, and other tools. The developer advocates embedding knowledge directly into Markdown files to reduce runtime dependencies and improve efficiency.", "body_md": "\"Someone opened a Miro board.\"\n\nThat's how I knew we were in trouble.\n\nNot because I dislike diagrams.\n\nI like diagrams.\n\nI dislike what usually happens **after** someone opens a Miro board.\n\nBoxes appear.\n\nThen arrows.\n\nThen more boxes.\n\nThen someone says:\n\n\"What if we had a Requirements Agent?\"\n\nSomeone else nods.\n\n\"What if that fed into an Architecture Agent?\"\n\n\"Which then talks to a Coding Agent.\"\n\n\"Which hands over to a Testing Agent.\"\n\n\"Oh! And a Documentation Agent.\"\n\n\"Don't forget the PR Review Agent.\"\n\nAt this point we have accidentally hired an AI engineering department.\n\nThe funny part?\n\nWe still haven't solved the original problem.\n\nThe thing that fascinates me about the current AI tooling landscape is that everyone seems obsessed with designing specialists.\n\nEvery prompt has a job title.\n\nEvery workflow has another agent.\n\nEvery new capability apparently deserves another box in the diagram.\n\nMeanwhile the poor model starts every conversation by asking:\n\n*\"Where are the coding guidelines?\"*\n\nAgain.\n\nLet's be honest.\n\nMost of us aren't inventing new consensus algorithms before lunch.\n\nOur work usually looks something like this:\n\nThe difficult part isn't typing Java (or Python, or C#, or TypeScript, or Rust... or, God forbid, Visual Basic).. It's reconstructing context.\n\nEvery. Single. Time.\n\nEvery fresh chat starts the same way.\n\n\"Can you fetch Confluence?\"\n\n\"Can you open Jira?\"\n\n\"Where are the guidelines?\"\n\n\"Do we have an ADR for this?\"\n\nEventually your AI spends more time talking to MCP servers than helping you write software.\n\nCongratulations.\n\nYou've recreated a junior developer during week one.\n\nExcept unlike the junior developer...\n\n...you wipe its memory every morning.\n\nThis was probably the biggest mindset shift for me.\n\nJira is... fine.\n\nConfluence is... also there.\n\nFor humans.\n\nBut if every implementation requires the AI to continuously fetch Jira tickets, Confluence pages and random documentation...\n\n...your documentation has become a runtime dependency.\n\nAnything your AI repeatedly needs should simply exist in your knowledge base.\n\nCoding standards.\n\nArchitecture decisions.\n\nBusiness terminology.\n\nReview expectations.\n\nCommon implementation patterns.\n\nThe \"please don't touch this query after 4pm on a Friday\" notes.\n\nMarkdown.\n\nMarkdown.\n\nMore Markdown.\n\nIf Confluence is still the source of truth, great.\n\nSynchronise it.\n\nExport it.\n\nEmbed it.\n\nI don't particularly care how it gets there.\n\nI care that the AI opens a local Markdown document instead of making its fifteenth MCP request of the day.\n\nLess fetching.\n\nMore building.\n\nPeople ask me why I like using Obsidian alongside AI.\n\nIt's not because I enjoy collecting Markdown files.\n\nIt's because Obsidian becomes a second brain.\n\nEvery architectural decision.\n\nEvery naming convention.\n\nEvery lesson learned.\n\nEvery business quirk.\n\nEvery \"we tried that in 2024 and production caught fire.\"\n\nOnce it's written down, the AI stops rediscovering it every conversation.\n\nThis is where tools like Superpowers really clicked for me.\n\nHonestly, replace \"Superpowers\" with SpecKit, Matt Pocock's workflows, or whatever orchestration framework you prefer.\n\nThe name doesn't matter. The orchestration does.\n\nImagine the flow.\n\nOne skill gathers context.\n\nIt reads the Jira ticket.\n\nFinds related Markdown.\n\nLoads business specifications.\n\nPulls architecture decisions.\n\nFinds similar implementations.\n\nDone.\n\nThe next skill takes over.\n\nLoads project guidelines.\n\nChecks architectural constraints.\n\nReminds the model about naming conventions.\n\nHighlights business rules that everyone forgets.\n\nDone.\n\nImplementation finishes.\n\nAnother skill takes over.\n\nGenerate the PR description.\n\nCheck documentation updates.\n\nSuggest release notes.\n\nIdentify defects.\n\nRaise technical debt where appropriate instead of adding another immortal `TODO`\n\n.\n\nGenerate review comments that actually sound like your team.\n\nNotice what didn't happen?\n\nWe never created a PR Agent.\n\nOr an Architecture Agent.\n\nOr a Documentation Agent.\n\nThey're just small reusable skills passing context to one another.\n\nThe clever bit isn't the individual skills.\n\nIt's the choreography.\n\nSome prompts start like this:\n\nYou are a Distinguished Principal Senior Staff Software Architect with twenty-five years of enterprise experience...\n\nMate. You're writing a commit message.\n\nTake it easy.\n\nModern models are already ridiculously capable.\n\nThe difference is rarely intelligence.\n\nIt's context.\n\nThe more I experiment with AI-assisted development, the more I believe we've been optimising the wrong thing.\n\nWe don't need another specialist.\n\nWe need better memory.\n\nWe need better orchestration.\n\nWe need our project knowledge to be available before the first line of code is written.\n\nIronically, that's also what makes human developers productive.\n\nKnowledge.\n\nContext.\n\nShared conventions.\n\nNot job titles.\n\nNext time someone opens a Miro board and proudly shows you twenty AI agents connected with colourful arrows...\n\nAsk one question.\n\n\"Where are your coding guidelines?\"\n\nIf the answer starts with:\n\n\"Well... they're mostly spread across Confluence...\"\n\nClose the Miro board.\n\nOpen Obsidian.\n\nStart there.\n\nBecause most backend teams don't need another AI employee.\n\nThey need a second brain and a handful of well-orchestrated skills.\n\nEverything else is just middle management.", "url": "https://wpnews.pro/news/asked-for-an-ai-assistant-and-accidentally-got-middle-management", "canonical_source": "https://dev.to/srsandrade/asked-for-an-ai-assistant-and-accidentally-got-middle-management-253n", "published_at": "2026-07-23 00:42:18+00:00", "updated_at": "2026-07-23 01:29:32.975587+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-agents", "developer-tools", "ai-tools"], "entities": ["Miro", "Jira", "Confluence", "Obsidian", "Superpowers", "SpecKit", "Matt Pocock"], "alternates": {"html": "https://wpnews.pro/news/asked-for-an-ai-assistant-and-accidentally-got-middle-management", "markdown": "https://wpnews.pro/news/asked-for-an-ai-assistant-and-accidentally-got-middle-management.md", "text": "https://wpnews.pro/news/asked-for-an-ai-assistant-and-accidentally-got-middle-management.txt", "jsonld": "https://wpnews.pro/news/asked-for-an-ai-assistant-and-accidentally-got-middle-management.jsonld"}}