References (verified) — draft v0.1

Compiled and web-verified Aug 2026. DOIs confirmed against ACM DL / IEEE-Crossref / arXiv. Flags at the bottom. Numbering is the working scheme used by 03-related-work.md.

[1] E. W. Dijkstra, “Letters to the editor: Go to statement considered harmful,” Communications of the ACM, vol. 11, no. 3, pp. 147–148, Mar. 1968, doi: 10.1145/362929.362947.

[2] R. C. Martin, Clean Architecture: A Craftsman’s Guide to Software Structure and Design. Boston, MA, USA: Prentice Hall, 2017.

[3] R. C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship. Upper Saddle River, NJ, USA: Prentice Hall, 2008.

[4] R. C. Martin, Agile Software Development: Principles, Patterns, and Practices. Upper Saddle River, NJ, USA: Prentice Hall, 2003.

[5] K. Beck, Test-Driven Development: By Example. Boston, MA, USA: Addison-Wesley, 2003.

[6] E. Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software. Boston, MA, USA: Addison-Wesley, 2003.

[7] C. A. R. Hoare, “An axiomatic basis for computer programming,” Communications of the ACM, vol. 12, no. 10, pp. 576–580, Oct. 1969, doi: 10.1145/363235.363259.

[8] B. Meyer, “Applying ‘design by contract’,” Computer, vol. 25, no. 10, pp. 40–51, Oct. 1992, doi: 10.1109/2.161279.

[9] GitHub, “Spec Kit: Toolkit to help you get started with Spec-Driven Development,” GitHub repository, 2024–2025. [Online]. Available: https://github.com/github/spec-kit (accessed Aug. 25, 2026).

[10] “Spec-driven development with AI: Get started with a new open source toolkit,” The GitHub Blog, Sep. 2025. [Online]. Available: https://github.blog/ai-and-ml/generative-ai/spec-driven-development-with-ai-get-started-with-a-new-open-source-toolkit/ (accessed Aug. 25, 2026).

[11] J. Jiang, F. Wang, J. Shen, S. Kim, and S. Kim, “A survey on large language models for code generation,” ACM Transactions on Software Engineering and Methodology, 2025, doi: 10.1145/3747588.

[12] X. Hou et al., “Large language models for software engineering: A systematic literature review,” ACM Transactions on Software Engineering and Methodology, vol. 33, no. 8, art. 220, Dec. 2024, doi: 10.1145/3695988.

[13] P. Sahoo, A. K. Singh, S. Saha, V. Jain, S. Mondal, and A. Chadha, “A systematic survey of prompt engineering in large language models: Techniques and applications,” arXiv:2402.07927, 2024.

Flags to resolve before final submission

  • [4] SOLID: no single peer-reviewed source exists; the acronym is community-coined over Martin’s principles. The 2000 originating article survives only via the Wayback Machine. Citing the book [4] is the clean choice.
  • [9]/[10] Spec Kit: a software artifact, no DOI. Confirm the blog byline on the post before final use; if unconfirmable, cite under “The GitHub Blog” (as done here).
  • [13] Sahoo et al.: arXiv preprint, not confirmed peer-reviewed. If the paper needs strictly peer-reviewed sources, lean on [11] and [12] and either drop [13] or keep the explicit “arXiv” designation. A strictly peer-reviewed prompt-engineering-for-code survey was not found.
  • Optional companion available if needed: B. Meyer, Object-Oriented Software Construction, 2nd ed. Prentice Hall, 1997 (ISBN 978-0-13-629155-8).