- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
The paper introduces ReqWeaver, a method that helps with generation of repositories. It assigns to AI coding agents the requirements that they should implement at each step. It additionally removes context that is no longer required. The authors test ReqWeaver on two benchmarks with two LLMs and three runs. It appears that ReqWeaver increases the average test-pass rate.
Critical strengths
The problem of generating lengthy repositories while ensuring that the correct requirements are taken into consideration at each step seems important and the authors show that they have managed to improve test-pass rate. Additionally, the paper appears to have multiple experiments testing various components of ReqWeaver which gives more insights about its performance and limitations to the reader.
Critical weaknesses
The contribution appears to be a combination of some existing techniques and the novelty seams incremental. Also, the paper includes some formal definitions that appear to have no contribution on the technical aspect of the paper. These definitions and the excessive use of new terminology, which sometimes is not explained properly, make a very simple workflow unnecessarily hard to follow.
Questions for authors
No questions.
2 comments
Thank you for your response. After considering your rebuttal, I have decided to maintain my original score.
Reviewer 3 — Shzi | Novelty, formal definitions, and presentation
W1(a): Novelty
We disagree with the assessment that ReqWeaver's novelty is limited. The review identifies neither a prior method implementing the same mechanism nor the specific technical overlap.
The central contribution is to make bindings between exact requirement passages and development stages part of the execution plan. Before coding, the Scheduler establishes and freezes source-reference bindings. The controller delivers the corresponding text at stage entry, manages completed-stage context, and redelivers requirements needed by later stages. This makes the source constraints accompanying each stage, and their reuse across stages, inspectable.
Section 2 provides concrete comparisons with nearby work. RPG represents capabilities, files, data flows, and functions in a graph; PaperCoder produces architecture plans and file-level analyses; CodeSpec compiles functional chains into executable architecture and behavior specifications. ReqWeaver explicitly records which original requirement passages accompany each development stage and executes those delivery assignments through the controller. Section 3.3 and Appendix C.2.1 illustrate these operations. If the reviewer considers this mechanism already established, please identify the closest prior work and the corresponding mechanism so that we can make a specific comparison.
W1(b): Technical role of the formal definitions
We disagree that these definitions have no technical role. Method definitions specify the objects a system processes and the operations it performs; each definition need not constitute a separate algorithmic contribution.
The stage sequence and goals in §3.1 identify the work to which requirements are assigned. In §3.3, Mk and Ok distinguish automatically delivered required evidence from optional reading references, while Ek=ResolveU(Mk) specifies how references become source text. In §3.4, Πk(Hk) defines the history actually presented to the model. These objects are used in the subsequent method description and correspond to concrete evidence-delivery and context-processing operations.
We added plain-language explanations in §§3.2–3.4 and connected the notation to stage goals and source text through the existing example to make these definitions easier to follow.
W1(c): Terminology and readability
The comment that some terminology is insufficiently explained does not identify a specific term, definition, or passage, so it cannot yet be checked item by item.
We have distinguished the preprocessing Scheduler from the coding agent's Plan stage, standardized required/optional terminology in the text and Figure 2, and expanded the
xlrdassignment rationale and reuse example in §3.3 and Appendix C.2.1. These edits improve clarity. A need for clarification, however, does not itself establish a lack of technical contribution. Please identify any terms or passages that remain ambiguous so that we can examine and address them specifically.