References
Reviewed: October 26, 2026.
Grouped by theme, with publication dates for fixed works and review dates for living documentation. Source descriptions identify the claim supported and the kind of evidence. Historical tool releases document the book's dated examples. Entries disclose access limitations.
Foundations: engineering practice, decision records, plain-text-as-code
- Sam Newman: "Backends For Frontends". November 18, 2015. Original description of the client-specific backend pattern.
- Andrej Karpathy: "Vibe coding". X, February 2, 2025. Original post introducing the term.
- Simon Willison: "Not all AI-assisted programming is vibe coding (but vibe coding rocks)". March 19, 2025. Practitioner commentary distinguishing vibe coding from AI-assisted programming with code review and understanding.
- Ian Sommerville: "Software Engineering", 10th edition. Pearson, 2015 (copyright 2016). Textbook treatment of software processes and lifecycle activities.
- David Farley: "Modern Software Engineering: Doing What Works to Build Better Software Faster". Addison-Wesley, 2021. Engineering principles and feedback. With Jez Humble: "Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation", Addison-Wesley, 2010. Deployment pipelines and delivery feedback. The associated continuousdelivery.com site defines continuous delivery (reviewed October 21, 2026).
- Kent Beck: "Test-Driven Development: By Example". Addison-Wesley, 2002 (copyright 2003). Original book on the test-first cycle and red-green-refactor practice.
- Dan North: "Introducing BDD". First published in Better Software, March 2006, republished online September 20, 2006. Original account of behavior-driven development and executable acceptance criteria.
- Ron Jeffries: "Essential XP: Card, Conversation, Confirmation". August 30, 2001. Original essay describing a user story as a card that tokens a requirement, a conversation that carries its detail, and a confirmation through acceptance tests.
- Mike Cohn: "User Story Template: What It Is and Why It Works So Well". Mountain Goat Software (reviewed October 25, 2026, page shows last updated April 22, 2026). Author-maintained description of the who, what, and why template, its attribution to Rachel Davies at Connextra, and the role of the "so that" clause. The page quotes Cohn saying he described the template in User Stories Applied as "As a (role), I want (function) so that (business value)", without a chapter or page number. Seb Rose (listed below) independently says the book includes the template. This review could not confirm the exact wording in the book, so the wording rests on this page.
- Mike Cohn: "User Stories Applied: For Agile Software Development". Addison-Wesley, March 1, 2004. Book on user stories. This review read the publisher's free sample pages (front matter, Introduction, Chapter 3, index) and an archived copy of the author's free Chapter 2, "Writing Stories" (original address returned 404 on October 25, 2026). The Introduction says stories keep just enough written down to prompt conversation, and Chapter 2 says details settled in conversation become tests. The remaining chapters were not read.
- Agile Alliance: "User Story Template" (reviewed October 25, 2026). Primary glossary entry dating the role, feature, and reason format to Connextra in 2001, and describing it as an aid more than a rule.
- Seb Rose: "User stories and BDD (part #1): the origins and evolution of the user story". Cucumber blog, October 31, 2019. Practitioner account crediting the template to Rachel Davies in the early 2000s and its spread to Cohn's books Agile Estimating and Planning and User Stories Applied. The post gives no publication years for those books.
- Clayton M. Christensen, Taddy Hall, Karen Dillon, and David S. Duncan: "Know Your Customers' 'Jobs to Be Done'". Harvard Business Review, September 2016 (reprint R1609D). Primary article for the framing that buying a product means hiring it to do a job. The HBR page shows only an excerpt, so the definition was checked in a reprint copy.
- Paul Hammant: trunkbaseddevelopment.com (reviewed October 21, 2026) and "Trunk-Based Development and Branch By Abstraction", Leanpub (available by 2020). Author-maintained explanations of shared-trunk development, short-lived branches, and branch by abstraction.
- Yue Jia and Mark Harman: "An Analysis and Survey of the Development of Mutation Testing". IEEE Transactions on Software Engineering, vol. 37 no. 5, 2011, pp. 649-678. Research survey covering mutation testing and equivalent mutants. An earlier technical report provides an accessible version of the work.
- ISTQB: "Certified Tester Foundation Level Syllabus v4.0.1". September 15, 2024. Versioned primary documentation for equivalence partitioning and boundary value analysis.
- Michael Nygard: "Documenting Architecture Decisions". November 15, 2011. Original ADR writeup covering context, decisions, consequences, and supersession.
- Oliver Kopp, Anita Armbruster, and Olaf Zimmermann: MADR template (reviewed October 21, 2026) and "Markdown Architectural Decision Records: Format and Tool Support", CEUR-WS Vol. 2072, 2018. Original paper and maintained documentation for the Markdown ADR format.
- ISO/IEC/IEEE: "42010:2022: Software, systems and enterprise - Architecture description". November 2022. Published architecture-description standard, distinguishing architecture from an architecture description. Publisher metadata and abstract checked October 21, 2026.
- Flemming N. Larsen: "Plain Text as Code Manifest" (reviewed October 21, 2026). Author's statement of the philosophy applied in the Foundation chapters.
- Eric Holscher and the Write the Docs community: "Docs as code" (reviewed October 21, 2026). Community documentation on applying development tools and workflows to documentation.
- GitHub Blog: "Viewing YAML Metadata in your Documents", September 27, 2013 (reviewed October 23, 2026). GitHub's product announcement for rendering YAML front matter above prose files.
- GitHub: "About the repository README file" and "Get a repository README for a directory" (reviewed October 23, 2026). Primary documentation for README presentation and directory lookup.
- GitLab: "File management" (reviewed October 23, 2026). Primary documentation for automatic README and index rendering.
- Mermaid: open-source documentation and live editor (reviewed October 21, 2026). Primary documentation and tooling for diagrams defined in text.
- Simon Brown: C4 model (reviewed October 21, 2026). Creator-maintained documentation for architecture abstractions and diagrams.
- Simon Brown: Structurizr documentation (reviewed October 21, 2026). Primary documentation for model-based architecture diagrams and the Structurizr DSL.
- D2 contributors: D2 documentation (reviewed October 21, 2026). Primary documentation for the diagram language and its layout and export options. The Mermaid comparison in this book is an editorial choice.
- Frederick P. Brooks Jr.: "The Mythical Man-Month: Essays on Software Engineering". Addison-Wesley, 1975, anniversary edition 1995. Chapter 11, "Plan to Throw One Away", supplies the historical planned-discard argument. The agent-regeneration analogy is book synthesis.
- Alistair Cockburn: "Crystal Clear: A Human-Powered Methodology for Small Teams". Addison-Wesley, 2004 (copyright 2005). Walking-skeleton strategy. Cockburn also restates his original definition (reviewed October 21, 2026). The analogy to
skeleton.mdis book synthesis.
Spec-driven development
- Fission AI: OpenSpec, repository, "Concepts", and "Commands" (reviewed October 22, 2026). Primary project documentation for change folders, delta specs, and synchronization into main specs. The default schema (
schemas/spec-driven/schema.yaml) and validation source (src/core/validation/) were read on October 26, 2026 for the scenario rules. The Stores beta guide (reviewed October 23, 2026) documents shared planning across repositories and the remaining task-routing and synchronization limits. - Fission AI: OpenSpec FAQ (reviewed October 21, 2026). Primary project description of lightweight, iterative planning. The book adds its AC ID and coverage conventions.
- GitHub: Spec Kit repository and documentation (reviewed October 21, 2026). Primary documentation for structured specification and implementation processes. Positioning Spec Kit at one end of a formality spectrum is book synthesis.
- LeanSpec: project documentation (reviewed October 21, 2026). Primary documentation for concise specifications maintained alongside implementation.
- Rick Hightower: "Agentic Coding: GSD vs Spec Kit vs OpenSpec vs Taskmaster AI: Where SDD Tools Diverge". Spillwave, February 27, 2026. Practitioner comparison of tool workflows and context strategies, reflecting its February snapshot. Author-site republication of the Medium article.
- GSD: original repository and GSD Core (reviewed October 21, 2026). Primary project documentation for the named development system, its move to GSD Core, and its phase workflow.
- Rick Hightower: "What Is GSD? Spec-Driven Development Without the Ceremony". Spillwave, February 23, 2026. Practitioner walkthrough of GSD's context engineering, orchestration, and state management. Author-site republication of the Medium article.
- Den Delimarsky: "Spec-driven development with AI: Get started with a new open source toolkit". GitHub Blog, September 2, 2025. Vendor-authored introduction to Spec Kit and specification-first workflows.
- Deepak Babu Piskala: "Spec-Driven Development: From Code to Contract in the Age of AI Coding Assistants". January 30, 2026, arXiv:2602.00180. Author-submitted preprint describing spec-first, spec-anchored, and spec-as-source workflows. The arXiv record says submitted to AIWare 2026. Submission does not establish acceptance or field consensus. The OpenReview record required browser verification during this review.
- Ani Galstian: "The Spec as Source of Truth: Why Codebases Should Be Rebuildable from Documentation". Augment Code, April 9, 2026, updated June 18, 2026. Vendor-authored argument for treating specifications as regenerable-code inputs.
- Framelink: Figma-Context-MCP (reviewed October 21, 2026). Primary repository documentation for exposing Figma design information to coding agents through MCP.
- Cucumber: "Behaviour-Driven Development", Gherkin reference, and tags documentation (reviewed October 21, 2026). Primary documentation for collaborative examples, scenario notation, execution filtering, and tags linking to external requirement records.
- JUnit: "Tagging and Filtering", JUnit 5.13.4 User Guide (reviewed October 21, 2026). Version-pinned primary documentation for
@Tag. Reusing tags for AC ID traceability is this book's convention. The formercurrentURL now redirects to JUnit 6 documentation. - Git: "githooks" documentation (reviewed October 22, 2026). Primary documentation for event-triggered scripts, including
pre-commit. - GitHub: "About protected branches" (reviewed October 22, 2026). Primary documentation for required status checks and bypass permissions.
Agentic engineering & agent instructions
- Agent Skills: Overview and specification (reviewed October 22, 2026). Primary format documentation for reusable instructions, skill descriptions, and loading skill content when relevant.
- InnerSource Commons: "What is InnerSource?" (reviewed October 21, 2026). Primary community definition of open-source collaboration practices applied within organizations.
- OpenRouter: "BYOK" (reviewed October 21, 2026). Primary vendor documentation illustrating user-supplied model-provider API keys.
- intentengineering.dev (reviewed October 21, 2026). Consulting site's definition of intent engineering through objectives, success criteria, constraints, and stop rules. Evidence of another usage of the phrase, rather than a standard definition.
- Don Johnson: "Intent-Driven Development: Define the System Before You Write the Code". DEV Community, December 4, 2025. Original practitioner account of specifying a system through events, RFCs, and acceptance criteria before implementation.
- Vishal Mysore: "What is Intent Driven Development?". Medium, March 9, 2026. Author's proposed framing of developers defining outcomes and constraints while agents handle implementation.
- intent-driven-development.com (reviewed October 21, 2026). Project site's definition of Intent-Driven Development and its
intent-cliworkflow. Its intent-above-implementation framing is the project's position. - AGENTS.md (reviewed October 21, 2026). Primary documentation for the instruction-file format and nested directory scope.
- GitHub Changelog: "Copilot coding agent now supports AGENTS.md custom instructions". August 28, 2025. Vendor announcement of Copilot coding agent support for
AGENTS.md. - OpenAI: ChatGPT and Codex documentation, Codex CLI, Codex IDE extension, features, Codex Cloud, "Build skills", and "Custom instructions with AGENTS.md" (reviewed October 21, 2026). Primary vendor documentation for the product surfaces and instruction mechanisms. These are the destinations of the former
developers.openai.com/codexdocumentation links. - OpenAI: Agents SDK documentation (reviewed October 21, 2026). Primary vendor documentation for the SDK's agent loop, tools, handoffs, guardrails, and tracing. The general agents guide distinguishes SDK and hosted runtime approaches.
- Anthropic: "Scaling Managed Agents: Decoupling the brain from the hands". April 8, 2026 (reviewed November 10, 2026). Primary vendor-authored architecture description distinguishing the model-call and tool-routing harness from session storage and execution environments, including context management.
- Anthropic: Claude Code overview and "How Claude remembers your project" (reviewed October 22, 2026). Primary vendor documentation for the coding agent, project instructions, and importing
AGENTS.mdfromCLAUDE.md. - OpenCode: Rules documentation (reviewed October 21, 2026). Primary project documentation for
AGENTS.mdand instruction precedence. - JetBrains: Junie documentation (reviewed October 21, 2026). Primary vendor documentation for Junie and project instructions stored in
AGENTS.md. - Model Context Protocol: introduction and "Architecture overview" (reviewed October 21, 2026). Versioned primary protocol documentation for tools, resources, prompts, and client-server roles.
- Thoughtworks: Technology Radar Vol. 34, release announcement, April 15, 2026, and report PDF, April 2026. Consultancy-authored assessment of cognitive debt, harness engineering, and SDD terminology. The cognitive-debt warning concerns developers' understanding of growing codebases.
- Birgitta Böckeler: "Harness engineering for coding agent users", April 2, 2026, and "Context Engineering for Coding Agents", February 5, 2026. Original practitioner framing of harness controls and context configuration. Published on martinfowler.com by a Thoughtworks engineer.
- Steve Yegge: "Revenge of the junior developer". Sourcegraph, March 22, 2025. Original practitioner essay proposing six overlapping waves of programming and agent use. The wave model is Yegge's forecast.
- Bill Doerrfeld: "AI doesn't create great developers, it amplifies them". LeadDev, January 20, 2026. Secondary reporting and commentary on developer experience and AI-assisted development. The amplification framing is an argument, not a universal measured effect.
- EPAM: "Agentic Development Lifecycle (ADLC): A New Model for AI Systems Beyond SDLC". February 5, 2026. Vendor-authored agent-product lifecycle framing, including governance and validation gates.
- AgentPatterns.ai: "AGENTS.md: Project-Level README for AI Coding Agents" (site review date September 19, 2026, checked October 21, 2026). Secondary commentary on project instructions, pointers, and context cost. The book's table-of-contents convention is an application of the pattern.
- AgentPatterns.ai: "Evaluating AGENTS.md: When Context Files Hurt More Than Help" (site review date October 4, 2026, checked October 21, 2026). Secondary synthesis of context-file evaluations. The article identifies minimal pointer files as an inference rather than a directly measured result.
- Andrej Karpathy: "+1 for context engineering over prompt engineering". X, June 25, 2025. Original terminology argument about the information supplied to a model.
- intent-engineering-for-coding-agents: companion CLI repository (reviewed October 21, 2026). Primary worked examples for the book's conventions. ADR-0004 records the design's broader BYOK usage. The
test-traceability,test-coverage,agents-size, andagents-linksimplementations at revision2491a62establish their actual checks and severity (reviewed October 23, 2026). - intent-engineering-for-coding-agents:
adr-formatimplementation at revision2491a62lists the accepted status prefixes for companion CLI checks (reviewed October 24, 2026). - Stephan Schwab: "AI as Your Legacy Code Archaeologist". Caimito, February 7, 2026. Consultancy-authored practitioner argument for extracting business rules from legacy code with domain-expert validation.
Site services
- intent-engineering-for-coding-agents: book site configuration and issue forms at revision
f4efc66(reviewed October 24, 2026). Primary repository evidence for the edit link, analytics script, and contribution routes. - GoatCounter: "Privacy policy" (reviewed October 24, 2026). Primary service documentation for traffic data, in-memory session handling, cookie-free site analytics, and the optional individual-pageview setting.
- GitHub: "General Privacy Statement" (effective April 27, 2026; reviewed October 24, 2026). Primary policy for GitHub services, including the site's hosting and contribution paths.
Security
- OWASP: "Cross-Site Request Forgery Prevention Cheat Sheet" (reviewed October 21, 2026). Primary guidance on CSRF, tokens, origin checks, and SameSite defense in depth.
- CVE Program: "About CVE" and "Terminology" (reviewed October 21, 2026). Official archived documentation defining the program, identifiers, and records.
- OWASP: foundation site and OWASP Top 10 (reviewed October 21, 2026). Primary security resources. The Top 10 project identifies 2025 as its current released edition and describes an awareness document about critical web application risks.
- OWASP: Top 10 for Large Language Model Applications (reviewed October 21, 2026). Primary project documentation for the 2025 risk list, including LLM01: Prompt Injection.
- Simon Willison: "Prompt injection attacks against GPT-3". September 12, 2022. Original proposal of the term "prompt injection", discussing Riley Goodside's attack examples.
Evidence-first verification sources
- Agile Alliance: "Acceptance Test Driven Development" (reviewed November 12, 2026). Practitioner-organization definition of collaboration and acceptance tests before implementation.
- Stryker: "Mutant states and metrics" (reviewed November 12, 2026). Primary tool documentation for mutant outcomes and mutation-score calculation.