Gather — 5 April 2026

The Term Shift: “Vibe Coding” → “Agentic Engineering” #

• Vibe coding is passé. Karpathy has a new name for the future of software. (The New Stack) — The term-coiner declares the term obsolete. Karpathy now prefers “agentic engineering” — “agentic” because you orchestrate agents 99% of the time; “engineering” because there’s an art & science to it.
• The End of Vibe Coding: Andrej Karpathy’s Shift to ‘Agentic Engineering’ in 2026 (Buttondown / Verified) — Deeper framing: maturation from casual experimentation into professional, structured practice with human oversight and architectural understanding.

Spec-Driven Development (Formalised) #

• Spec-Driven Development Is Eating Software Engineering: A Map of 30+ Agentic Coding Frameworks (Medium, Mar 2026) — Landscape map of spec-driven frameworks. METR study finding cited: developers using AI tools were 19% slower on average despite reporting higher confidence — debugging loops from unstructured prompts consume time saved on generation.
• Diving Into Spec-Driven Development With GitHub Spec Kit (Microsoft for Developers) — GitHub’s open-source toolkit (72,000+ stars). Formal tooling for spec-first AI coding.
• Understanding Spec-Driven Development: Kiro, spec-kit, and Tessl (Martin Fowler / ThoughtWorks) — Definitive analysis of the three major tools. Authoritative comparison.
• Spec-Driven Development: Unpacking 2025’s Key New AI-Assisted Engineering Practice (Thoughtworks) — Industry framing: living-spec vs static-spec platforms.
• How to Write a Good Spec for AI Agents (Addy Osmani) — Practitioner guide to spec authorship.
• Beyond the Vibes: Lessons from Using Spec-Driven Development Frameworks (Agentic Conf Hamburg 2026) — Conference session, Apr 2026.

Multi-Agent Orchestration (Architecture) #

• The Code Agent Orchestra — what makes multi-agent coding work (Addy Osmani) — Three-tier framework: Tier 1 in-process subagents (single Claude session), Tier 2 local orchestrators (Conductor, Vibe Kanban, Gastown, Claude Squad, Antigravity, Cursor Background Agents) with worktrees + dashboards, Tier 3 cloud async (assign task → close laptop → PR appears).
• Orchestrating Coding Agents (O’Reilly CodeCon 2026) (Addy Osmani) — Talk version of the orchestra framing.
• AI Coding Agents in 2026: Coherence Through Orchestration, Not Autonomy (Mike Mason) — Argues against fully autonomous agents; orchestration with human-in-loop is the winning pattern.
• From Vibe Coding to Multi-Agent AI Orchestration: Redefining Software Development (CIO) — Enterprise framing of the transition.
• Hands On with New Multi-Agent Orchestration in VS Code (Visual Studio Magazine, Feb 2026) — Microsoft’s VS Code multi-agent features.

Industry Data & Adoption #

• 2026 Agentic Coding Trends Report (Anthropic) — Official industry report PDF.
• AI Tooling for Software Engineers in 2026 (Pragmatic Engineer / Gergely Orosz) — Survey ran Jan 27 - Feb 17, 2026. Headline: Claude Code went from zero to #1 in eight months, overtaking GitHub Copilot and Cursor.
• The Pulse: Industry leaders return to coding with AI (Pragmatic Engineer) — CTO/VPE tier returning to hands-on coding via AI tools.
• DORA Report findings: 90% AI adoption → 9% bug rates, 91% more code review time, 154% larger PRs (via Addy Osmani citing Google’s 2025 DORA Report) — Counter-narrative: AI adoption correlates with more bugs and review burden. Critical signal.
• 57% of companies now run AI agents in production (via Addy Osmani) — enterprise adoption metric.
• Stripe: 1,000+ AI-generated PRs/week merged autonomously (via Addy Osmani) — concrete enterprise scale.

Prompt-Driven Development (Academic & Industry) #

• Prompt-Driven Development with Claude Code: Developing a TUI Framework (MDPI Electronics Journal) — Academic study: 7,420-line TUI framework built via Claude Code through 107 prompts (21 features, 72 bug fixes, 9 doc-sharing, 4 architectural, 1 docs generation). Concrete data point.
• Prompt-Driven Development: What We Were Really Doing All Along (Accidentally) (Chris Perrin, Jan 2026) — Reframes existing practices as PDD.
• Prompt Driven Development (Capgemini) — Consultancy framing of the methodology.

Vibe Coding in Practice #

• Vibe Coding in Practice: Patterns, Pitfalls, and Prompting Strategies (AIM Consulting) — Balanced analysis closer to technique than product roundup.
• A Structured Workflow for “Vibe Coding” Full-Stack Apps (DEV - Wasp) — Concrete workflow recipe.
• Intent-Based Code Patterns (Vibe Coding eBook) — Pattern catalogue.
• Patterns Introduction (Vibe Coding Iceberg) (Danielle Ackerman) — Pattern-language approach to vibe coding.

Cross-links #

• Claude-Specific Expertise Boris Cherny’s 5-parallel-terminal workflow + Gergely Orosz’s Claude Code survey are direct Claude-specific corroboration of the multi-agent Tier-1/Tier-2 framing.
• Claude-Specific Expertise The METR “19% slower” finding and DORA bug-rate numbers are the cautionary counterweights to optimistic Claude Code tips content.
• Applications of Vibe Coding Stripe’s 1,000 PRs/week + 57% enterprise adoption are concrete application data points.
• AI Impact on Society METR + DORA findings (AI makes devs slower, bugs up) are the empirical basis for sentiment skepticism.
• Open vs Closed AI Ecosystems Claude Code dominance in Pragmatic Engineer survey is a closed-ecosystem win worth tracking.

Meta-observations #

• Emerging theme: The term “vibe coding” is being actively retired by its coiner in favour of “agentic engineering”. Worth watching whether industry follows Karpathy or keeps the viral term.
• Emerging theme: Spec-Driven Development has graduated from concept to tooled-up category with GitHub Spec Kit (72k stars), AWS Kiro (IDE), Tessl. This is the structural antidote to unstructured vibe coding.
• Emerging pattern: Three-tier orchestration taxonomy (in-process / local / cloud async) is becoming a shared mental model — cite Addy Osmani as canonical.
• Emerging pattern: Counter-narrative is gathering empirical backing — METR 19% slowdown, DORA 9% more bugs, 154% larger PRs. Previously only anecdotal.
• Keyword suggestion: “agentic engineering” — new umbrella term, worth adding as keyword.
• Keyword suggestion: “spec-driven development” OR “spec coding” — now concrete enough to track independently of vibe coding.
• Keyword suggestion: “GitHub Spec Kit” / “AWS Kiro” / “Tessl” — specific tools warranting their own queries.
• Author to watch: Addy Osmani (addyosmani.com) — producing the most cited architectural analysis this cycle.
• Author to watch: Mike Mason (mikemason.ca) — thoughtful essays on orchestration philosophy.
• Source to watch: martinfowler.com — long-form authoritative analysis (Spec-Driven Development article).
• Source to watch: resources.anthropic.com — official Agentic Coding Trends reports.
• Source to watch: agentic.hamburg — conference proceedings from Agentic Conf Hamburg.
• Quality signal: Pragmatic Engineer (Gergely Orosz) publishes survey data rare in this space — treat as high-signal primary source.
• Quality signal: DORA Report and METR study are empirical counterweights to marketing-adjacent content — always worth surfacing.
• Noise pattern: Same problem as last gather — “Top N AI Agent Frameworks” listicles still dominate search results. The -"top 7" -"top 10" -"best tools" exclude list helps but doesn’t catch “12 Best…” and similar variants. Consider adding more exclude terms.