AI Native DevCon 2026 London — all conference sessions as interactive skills
71
89%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
outline.md to locate the relevant section, then read that section of transcript.md.transcript.md. Never put quotation marks around paraphrased content.transcript.md, say so explicitly — do not fabricate or present paraphrased content as a direct quote. It is fine to say "She doesn't appear to address this in the talk."transcript.md before answering, and note when the speaker addresses the topic in more than one place.For most questions, structure your response as:
transcript.md, introduced with a neutral phrase such as "In her words:" or "She puts it this way:".outline.md).Example
User: What does Böckeler mean by the "Opus 4.5 moment"?
Response: She uses "the Opus 4.5 moment" to mark a qualitative leap in model capability that changed what teams could realistically delegate to an AI coding assistant. In her words: [verbatim quote from transcript.md]. This comes up in the [section name] section of the talk.
transcript.md, say so clearly — e.g., "This doesn't appear to be covered in the talk." Do not speculate or fill the gap with outside knowledge unless the user explicitly asks for broader context beyond the talk.outline.md, check each candidate section in transcript.md before answering, and note which parts of the talk are relevant.transcript.md or the bundle. Do not retrieve or fabricate content from external URLs.quotes.md contains pre-extracted verbatim highlights from this talk, organised by theme. When formulating answers, check quotes.md first for strong citable evidence before searching the full transcript.md.
.tessl-plugin
talk-azriel-executable-specs-agentic-coding
talk-batey-building-product-teams-age-of-ai
talk-birgitta-closing-keynote
talk-cormack-tests-lie-observability-ai-honest
talk-debois-agent-enablement
talk-douglas-training-ai-on-your-own-code
talk-dubnov-merge-rate-ai-adoption
talk-farley-vibe-coding-best-we-can-do
talk-firtman-web-mcp-agentic-web
talk-foxwell-reinvention-dev-team
talk-graziano-spec-driven-development
talk-groetzinger-skills-everywhere
talk-jones-odevo-ai-native-transformation
talk-jourdan-pipelines-to-prompts
talk-katsioloudes-code-security-ai
talk-kerr-bipolar-disorder-dysregulation-ai
talk-lamis-context-engineering-dreaming
talk-lawson-agent-experience
talk-lopopolo-harness-engineering-humans-steer-agents-execute
talk-luebken-embedding-pi-coding-agent
talk-maleix-collective-intelligence
talk-marsden-agent-desktops
talk-martinelli-spec-driven-development
talk-moss-skills-team-workflow
talk-obstbaum-willoughby-evals-hard
talk-overweg-one-brain-no-filtering
talk-podjarny-skills-are-the-new-code
talk-roberts-ai-native-brownfield
talk-roberts-brownfield-ai-native
talk-scheire-artificial-intelligence
talk-selajev-docker-sandboxes-agents
talk-sloan-harness-engineering-beyond-code
talk-smith-connecting-context-future-transports
talk-stack-humans-architect-ai-writes-code
talk-stoneham-product-brain
talk-syme-agentic-repository-automation
talk-tal-skills-security
talk-thomas-ai-native-engineering
talk-trieloff-browser-agents
talk-walter-runtime-intelligence-agents
talk-wilson-cq-stack-overflow-for-agents
talk-wotherspoon-humans-vs-slop