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 > > >
