Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Spec-driven development is essential for AI agents. 📋 A clean spec ensures a clean context, helping agents achieve major improvements in code quality. It helps them reason cleanly instead of guessing. Have you tried using specs to guide your AI agents?

19,541 görüntüleme • 10 ay önce •via X (Twitter)

15 Yorum

Heikki Hämäläinen profil fotoğrafı
Heikki Hämäläinen10 ay önce

💯This is essential nothing beats highly detailed PRD to communicate your original Intent to AI Agents - and of course you csn use AI to build that

MM PROVIDES profil fotoğrafı
MM PROVIDES10 ay önce

👀🧠🔑📡

Love Web3 World profil fotoğrafı
Love Web3 World10 ay önce

So context is the key for agents?

Somi profil fotoğrafı
Somi10 ay önce

Yes, and the format matters more than I expected. Markdown specs that live alongside the code outperform external docs because the agent can reference them contextually. We saw fewer hallucinations and better goal persistence once we started treating specs as living documents that accumulate project knowledge.Yes, and the format matters more than I expected. Markdown specs that live alongside the code outperform external docs because the agent can reference them contextually. We saw fewer hallucinations and better goal persistence once we started treating specs as living documents that accumulate project knowledge.The format matters more than I expected. Markdown specs that live alongside the code outperform external docs because the agent can reference them contextually. We saw fewer hallucinations and better goal persistence once we started treating specs as living documents that accumulate project knowledge.xxThe format matters more than I expected. Markdown specs that live alongside the code outperform external docs because the agent can reference them contextually. We saw fewer hallucinations and better goal persistence once we started treating specs as living documents that accumulate project knowledge.

JOHN Z⚡ profil fotoğrafı
JOHN Z⚡10 ay önce

Implementing specs may reduce future regressions.

Btc💰.Baller profil fotoğrafı
Btc💰.Baller10 ay önce

Nice approach … One the multi agent tasking .. I’m just curious is it the embedded file that the management agent be clearing,updating and deleting irrelevant data..or the uploaded file if you’re using text + embeddings ?

Modelmetry profil fotoğrafı
Modelmetry10 ay önce

Works best with Markdown files as specs and must live within the repo.

Max Informatiker profil fotoğrafı
Max Informatiker10 ay önce

Specs are the cheat code for multi-agent stacks. Clear context is the only way to stop agents turning every task into a game of broken telephone.

Juan Carlos profil fotoğrafı
Juan Carlos10 ay önce

This video should be included in the Gemini usage agreement; it would prevent the unnecessary energy waste of running dumb agents.

Techno Luis profil fotoğrafı
Techno Luis10 ay önce

Totalmente de acuerdo, los specs claros en arquitectura multi-agente han mejorado la robustez de los sistemas con los que trabajo. ¿Has notado tú ese salto en calidad?

Esteban Puerta profil fotoğrafı
Esteban Puerta10 ay önce

specs as the primary artifact instead of code is a weird mental shift but it works

Biggiefx.stx profil fotoğrafı
Biggiefx.stx10 ay önce

When mobile browser extension @googledevs

Cloud Quick Labs profil fotoğrafı
Cloud Quick Labs10 ay önce

Enroll my Udemy course on GCP DevOps

Syed Mohammad Ali profil fotoğrafı
Syed Mohammad Ali10 ay önce

This makes so much sense

👑 ✨Dharkpearl 💎 profil fotoğrafı
👑 ✨Dharkpearl 💎10 ay önce

Clear specs reduce guesswork and give AI something solid to work with I’ve seen this matter a lot in chat systems, where context shape every response. That’s why what @thelooma_io is building is interesting. AI that will run product data, and real conversation inside chat apps

Benzer Videolar

I’m excited to launch Tessl's first products! Introducing the Tessl Framework and Tessl Spec Registry, which integrate into any agent to keep it on rails and well informed using Spec-Driven Development. More details in the launch post: It’s a big milestone in the journey towards AI Native Development🚩 I’m proud of our amazing team, and keen to get beta feedback from the community! ❤️ What’s the problem we’re solving? Agents are powerful, but they’re very unreliable. They hallucinate, claim false success and break things often enough that it’s hard - and tiring - to use them on production code. How are we helping? The Tessl Framework makes agents capture intent in specs before coding, aligning you and the agent on what to build. It adds tests as harder guardrails, and stores specs as long term memory of what your product should do. It’s available in private beta - visit our home page to request early access: The Tessl Spec Registry helps agents use open source better. It contains over 10,000 usage specs for using libraries, which you can add to your project like regular dependencies. It also lets you distribute your own guidance and policies to agents. It’s in open beta and free to use! Check it out here: Both products are just the beginning, and we’re committed to building them in the open. Check out the video or our launch blog post for more info: Looking forward to hearing your thoughts, in the thread or our community Discord!

Guy Podjarny

12,740 görüntüleme • 1 yıl önce