qatools-cli 1.2.6 → 1.2.7
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/package.json +1 -1
- package/qatools.js +3 -2
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.7",
|
|
4
4
|
"description": "CLI for QA Tools — requirements, epics, sprints, sessions, App Context sync, project agenda. The companion to qa-tools.com.",
|
|
5
5
|
"scripts": {
|
|
6
6
|
"release": "npm version patch --no-git-tag-version && npm publish",
|
package/qatools.js
CHANGED
|
@@ -2689,13 +2689,14 @@ If the qa-tools MCP server (\`qatools mcp\`) is available, use its tools and the
|
|
|
2689
2689
|
Capacity: count how many requirements reached implemented/tested in each completed sprint (MCP: \`sprint_velocity\`). If there is no history, say so and propose a conservative number.
|
|
2690
2690
|
|
|
2691
2691
|
2. Draft a proposal:
|
|
2692
|
-
- Only approved requirements without a sprint are candidates.
|
|
2692
|
+
- Only approved, functional requirements without a sprint are candidates. Continuous (non-functional) requirements are never planned — they are checked against every sprint.
|
|
2693
2693
|
- Never touch completed sprints or requirements in one — the backend refuses.
|
|
2694
2694
|
- An epic's requirements never go before the requirements of the epics it dependsOn.
|
|
2695
2695
|
- Priority 1 first, then epic priority.
|
|
2696
|
+
- Per sprint: roughly the capacity average, counting requirements already in the sprint.
|
|
2696
2697
|
- If existing sprints don't fit, propose new ones (name + end date) — don't create them yet.
|
|
2697
2698
|
|
|
2698
|
-
3. Present the proposal and WAIT: a table of sprint | requirement key | title | reason (priority / epic dependency / capacity), plus what you left out and why. Change nothing until the user approves.
|
|
2699
|
+
3. Present the proposal and WAIT: a table of sprint | requirement key | title | reason (priority / epic dependency / capacity), plus what you left out and why, and any dependency conflicts. Change nothing until the user approves.
|
|
2699
2700
|
|
|
2700
2701
|
4. Apply after approval:
|
|
2701
2702
|
\`qatools sprint-create --name "Release 4.1" --end 2026-12-15\`
|