AI Native DevCon 2026 New York — practical agent skills grounded in conference talks
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
This worksheet is Tessl's recommended application of Fowler's talk. Fill it with supplied evidence; use “unknown” for missing facts. It is an experiment design, not a claim that replacement has succeeded.
Name the smallest useful component and its callers. Describe why its blast radius is limited. List the interfaces, user experience, data ownership, and operational foundations that must remain stable. Name dependencies that are outside the visible code, including shared state and migrations. Explain why this component is replaceable rather than merely small.
| Asset | Required statement | Evidence or gap |
|---|---|---|
| Intent | What must remain true for users? | Original decision or requirement |
| Architecture | What boundary does the component uphold? | Contract and caller evidence |
| Evaluation | What observable result demonstrates the intent? | Check independent of implementation |
| Provenance | Why was this behavior chosen? | Person, decision, context |
Distinguish intended behavior from an implementation accident. Do not promote every current quirk into a permanent requirement without a reason.
Record the original and candidate implementations, the shared evaluation inputs, expected outputs, state compatibility, and comparison method. Include one ordinary case, one failure case, and one behavior that the current code knows but the written requirements omit. These case categories are suggested here, not universal requirements from the talk.
For each divergence, classify the cause and record the decision needed. A passing implementation-specific test does not establish rewrite equivalence. Keep a separate place for checks that cannot yet survive a language change.
Define the production observation, the assertion it measures, and the component allowed to change when it fails. Use the user's actual target instead of copying the talk's 300-millisecond example. State evidence required for replacement, rollback conditions, and what will remain a thought experiment. Finish with the smallest next action that reduces an identified uncertainty.
.tessl-plugin
skills
talk-arcolano-autonomy-and-trust
talk-aroussi-decision-context
talk-bevin-agent-assisted-instrument-design
talk-boeckeler-context-lifecycles
talk-braun-context-graphs
talk-carmont-evolving-agent-harnesses
talk-chanezon-gordon-agent-experience-evaluation
talk-cox-secure-agentic-workflows
talk-cunniffe-reusable-agent-platform
talk-davis-agent-tool-policies
talk-debois-concurrent-delivery
talk-dzialets-team-automation
talk-fahmy-harness-api-design
talk-finster-continuous-delivery
talk-fowler-regenerative-software
talk-gavrilescu-factory-architecture
talk-graciolli-amin-verification-aware-programming
talk-gruenbaum-reverse-graph-engineering
talk-hassan-agentic-engineering
talk-hossain-enterprise-agent-adoption
talk-huntley-patch-ready-factories
talk-jain-verifying-intent
talk-katsioloudes-montei-agentic-lifecycle
talk-knox-harness-engineering
talk-kovac-deterministic-memory
talk-lee-perkins-code-readiness
talk-lorenc-machine-speed-security
talk-lubken-software-of-one
talk-meijer-software-specialization
talk-meppiel-versioned-agent-contracts
talk-moss-concurrent-agent-risk
talk-myers-understanding-agent-generated-code
talk-ocytko-scaling-agentic-engineering
talk-oza-automating-design-quality
talk-panzica-agentic-sdlc
talk-pari-patel-agent-awareness
talk-podjarny-trustworthy-software-factories
talk-poulter-factory-improvement
talk-pratik-patel-refined-rag-data
talk-re-ferre-development-platforms
talk-sadogursky-factory-of-factories
talk-shah-training-agent-skills
talk-sharma-mohapatra-evolving-intent
talk-singhal-operating-agents-at-scale
talk-stack-incident-dossiers
talk-tyler-team-coding-benchmarks
talk-wotherspoon-agent-execution-environments
talk-yegge-ai-powered-factories
talk-zuber-leadership-through-coding