OpenSpec v1.13.2: Write specifications first and then code, and put an "anti-deviation" constraint on AI programmingOpenSpec v1.13.2：先写规格再写代码，给 AI 编程上个「防跑偏」约束

If you directly say to the AI, "Help me add an export function," it may interpret it as ten different things, so you go back and forth to clarify, and the more you change, the further you go.

OpenSpec solidifies "what needs to be done and what the acceptance criteria are" into a structured specification document and writes it into the code warehouse: after that, AI will work according to this specification every time, and people can review, compare, and roll back at any time. Requirement changes are no longer chat records, but diffable files in the warehouse.

The first step is to let AI generate a change proposal according to the template, clearly stating the motivation, impact and trade-offs; it will only continue after you confirm it.

The second step is to expand the proposal into formal specifications: each requirement comes with a verifiable scenario description, which serves as the only basis for subsequent acceptance.

In the third step, the specifications are broken down into a task list, and AI implements them one by one and ticks them off; any changes that deviate from the specifications will be seen at a glance during the review.

The download button provides the v1.13.2 complete source code package (about 3.3 MB, including documents, official website source code and specification catalog template, with Chinese instructions attached).

Node.js version 18 and above is required. The source code package does not contain dependencies. The first run requires online installation; the official website documentation and warehouse install.md have detailed steps to get started.

This article is compiled from public sources and ships with the matching resource. Product features and pricing are subject to the official page. Resources are for learning and exchange only — please respect the original license.