Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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 Aufrufe • vor 9 Monaten •via X (Twitter)

15 Kommentare

Profilbild von Heikki Hämäläinen
Heikki Hämäläinenvor 9 Monaten

💯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

Profilbild von MM PROVIDES
MM PROVIDESvor 9 Monaten

👀🧠🔑📡

Profilbild von Love Web3 World
Love Web3 Worldvor 9 Monaten

So context is the key for agents?

Profilbild von Somi
Somivor 9 Monaten

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.

Profilbild von JOHN Z⚡
JOHN Z⚡vor 9 Monaten

Implementing specs may reduce future regressions.

Profilbild von Btc💰.Baller
Btc💰.Ballervor 9 Monaten

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 ?

Profilbild von Modelmetry
Modelmetryvor 9 Monaten

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

Profilbild von Max Informatiker
Max Informatikervor 9 Monaten

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.

Profilbild von Juan Carlos
Juan Carlosvor 9 Monaten

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

Profilbild von Techno Luis
Techno Luisvor 9 Monaten

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?

Profilbild von Esteban Puerta
Esteban Puertavor 9 Monaten

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

Profilbild von Biggiefx.stx
Biggiefx.stxvor 9 Monaten

When mobile browser extension @googledevs

Profilbild von Cloud Quick Labs
Cloud Quick Labsvor 9 Monaten

Enroll my Udemy course on GCP DevOps

Profilbild von Syed Mohammad Ali
Syed Mohammad Alivor 9 Monaten

This makes so much sense

Profilbild von 👑 ✨Dharkpearl 💎
👑 ✨Dharkpearl 💎vor 9 Monaten

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

Ähnliche Videos

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 Aufrufe • vor 1 Jahr