Hi all, I’m still pretty new to SDD, but I’ve been experimenting with an idea Sergey Chugunov shared in a private discussion: looking at our tests and using them to figure out what the product actually guarantees.
Here’s what I have for now: https://dpavlov.gitverse.site/ignite-product-spec/ I’ve gone through about 15% of the tests so far, and the model limits are disappearing surprisingly fast :) Please take a look! I’d like to hear what you think - especially how we could make use of these specs afterward. Thanks! чт, 3 сент. 2026 г. в 09:35, Vladislav Pyatkov <[email protected]>: > Hi Dmitriy, > > I’d like to clarify what these specs are expected to look like. Are they > meant to become part of the end-user documentation, or are they > developer-only specs? > > My concern is that overly detailed specs may create more complexity than > clarity and give a false sense of safety. Even detailed documentation can > be interpreted differently and may give a misleading picture of how the > code actually behaves. > > Vladislav Pyatkov > > On Wed, Sep 2, 2026, 10:55 PM Dmitry Werner <[email protected]> wrote: > > > I see a clear role for both approaches: > > - IEP – still valuable for major architectural changes and strategic > > decisions. > > - SDD (spec‑driven development) – a lightweight, fast, and AI‑friendly > > alternative for day‑to‑day design tasks, feature specs, and API > contracts. > > > > They can comfortably coexist. > > > > For storage, I’d suggest keeping the specs right in the main Ignite > > repository, under a specs/ folder. That keeps them version‑aligned with > the > > code. > > > > On Wed, Sep 2, 2026 at 10:52 PM Anton Vinogradov <[email protected]> wrote: > > > > > Great idea again, but instruction needed as well. > > > Could you lead this? > > > > > > On Wed, Sep 2, 2026 at 8:50 PM Dmitriy Pavlov <[email protected]> > > wrote: > > > > > > > Hi Igniters, > > > > > > > > Writing detailed design proposals takes effort, while many of us > > already > > > > use AI assistants to explore designs and produce code. > > > > > > > > Could lightweight Markdown specifications make spec-driven > development > > > > practical for Ignite 2? > > > > > > > > Would you use or contribute to them? Where should they live, and > which > > > > feature should we try first? > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > > >
