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 is Tessl's recommended application of Myers's talk. Use it to redesign attention around one workflow or class of change, not to impose a universal amount of manual code reading.
State the user or business outcome. Record generated work, accepted delivery, review waiting, rework, and incidents where available. Explain why a growing PR queue is harmful in this context. Consider reducing unnecessary or oversized work before assuming that review must disappear.
| Concern | Current evidence | What automation can assist | What people still need to understand |
|---|---|---|---|
| Obvious defects | |||
| Design and maintainability | |||
| Operational consequences | |||
| Verification coverage |
Do not treat a green check as evidence that all concerns are covered. Record missing evidence separately from an observed defect.
Describe a contract, executable specification, domain language, or other high-leverage representation the team could inspect. State its scope, assumptions, hidden details, and how a broken assumption becomes visible. Explain which implementation details remain necessary for consequential decisions.
Choose one change and outline how an engineer could trace intended behavior through this abstraction to observable results. This walkthrough is a proposed verification exercise unless it has been performed.
Identify a failure that automation may leave to a person. Record the state, evidence, recovery controls, and relevant system understanding they would need. Explain how the interface will help them reason, rather than merely interrupting them.
Propose one reduction in repetitive review work and one measure that protects understanding or operational outcomes. Retain the organization's actual release authority. State an observation period, regression signal, and revision condition. Finish with the practical next step and the limits of the evidence; do not infer success from a higher PR count alone.
.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