a l vs Loc a l • Most people will think it is a “Product Requirements Document”. • But a ctu a lly it should be n a med a s beh a vior oriented a rtif a ct. Written in n a tur a l l a ngu a ge th a t express softw a re function a lity a nd serves a s guid a nce to AI coding a gents. • E a ch v a ri a nt of spec-driven development de f ines their a ppro a ch to a spec’s structure, level of det a il, a nd how these a rtif a cts a re org a nized within a project. • Context File: For these context, they a re mostly c a lled “memory b a nks”, for AI a gents to remember the b a ckground inform a tion of the project
• After c a pture the requirements of the fe a ture, you will st a rt to write det a ils • The spec f iles will include the det a ils on how to build the fe a tures • You h a ve to list out the t a sks, step by step, on how to a ccomplish. • The Spec will be diminished a fter the fe a ture is completed.
E ff ect of Use in Green f ield a nd Brown f ield codeb a ses is unknown • All a v a il a ble fr a mework is still Level 1 (only some p a rt a re Level 2 a nd 3) • Extr a E ff ort on con f irming both Specs content a nd the code gener a ted