@dezkareid/osddt 1.3.1 → 1.3.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +9 -7
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -192,19 +192,21 @@ Run the following command to write the feature specification:
|
|
|
192
192
|
- If it does not exist, proceed using only the requirements provided in ${args}.
|
|
193
193
|
2. Analyze the requirements provided in ${args}
|
|
194
194
|
3. Identify the core problem being solved
|
|
195
|
-
4. Define the scope, constraints, and acceptance criteria
|
|
195
|
+
4. Define the scope, user-facing constraints, and acceptance criteria
|
|
196
196
|
5. Write the specification to \`osddt.spec.md\` in the working directory
|
|
197
197
|
|
|
198
198
|
## Specification Format
|
|
199
199
|
|
|
200
|
+
The spec should describe **what** the feature does and **why**, from a product and user perspective. Do **not** include implementation details, technology choices, or technical architecture — those belong in the plan.
|
|
201
|
+
|
|
200
202
|
The spec should include:
|
|
201
|
-
- **Overview**: What and why
|
|
202
|
-
- **Requirements**: Functional
|
|
203
|
-
- **Scope**: What is in and out of scope
|
|
204
|
-
- **Acceptance Criteria**: Clear, testable criteria
|
|
205
|
-
- **Open Questions**:
|
|
203
|
+
- **Overview**: What the feature is and why it is needed
|
|
204
|
+
- **Requirements**: Functional requirements only — what the system must do, expressed as user-observable behaviours
|
|
205
|
+
- **Scope**: What is in and out of scope, described in product terms
|
|
206
|
+
- **Acceptance Criteria**: Clear, testable criteria written from a user or business perspective
|
|
207
|
+
- **Open Questions**: Ambiguities about desired behaviour or product decisions to resolve
|
|
206
208
|
|
|
207
|
-
> If \`osddt.research.md\` was found, add a **Research Summary** section that briefly references the key insights and constraints it identified.
|
|
209
|
+
> If \`osddt.research.md\` was found, add a **Research Summary** section that briefly references the key insights and user-facing constraints it identified.
|
|
208
210
|
|
|
209
211
|
## Arguments
|
|
210
212
|
|