qatools-cli 1.2.8 → 1.2.10
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 +15 -6
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "qatools-cli",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.10",
|
|
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
|
@@ -2697,6 +2697,7 @@ If the qa-tools MCP server (\`qatools mcp\`) is available, use its tools and the
|
|
|
2697
2697
|
2. Draft a proposal:
|
|
2698
2698
|
- Only approved, functional requirements without a sprint are candidates. Continuous (non-functional) requirements are never planned — they are checked against every sprint.
|
|
2699
2699
|
- Never touch completed sprints or requirements in one — the backend refuses.
|
|
2700
|
+
- Carry-over: approved or in-progress requirements in an overdue sprint (end date passed, not completed) may be proposed for a move to an open sprint — they keep status and assignee. Never move requirements out of a sprint that has not passed its end date.
|
|
2700
2701
|
- An epic's requirements never go before the requirements of the epics it dependsOn.
|
|
2701
2702
|
- Priority 1 first, then epic priority.
|
|
2702
2703
|
- Per sprint: roughly the capacity average, counting requirements already in the sprint.
|
|
@@ -3688,7 +3689,7 @@ const mcpTools = [
|
|
|
3688
3689
|
},
|
|
3689
3690
|
{
|
|
3690
3691
|
name: "sprint_velocity",
|
|
3691
|
-
description: "Planning capacity: per completed sprint, how many
|
|
3692
|
+
description: "Planning capacity: per completed sprint, how many requirements were planned and done, plus what is already planned in each open sprint. Completed sprints use the numbers stored when they were completed (fromSnapshot true); older ones are counted from today's statuses (fromSnapshot false). averageCompletionRate = average share of planned requirements that got done.",
|
|
3692
3693
|
inputSchema: mcpSchema(),
|
|
3693
3694
|
run: async (a) => {
|
|
3694
3695
|
const [{ sprints }, { requirements }] = await Promise.all([
|
|
@@ -3698,15 +3699,22 @@ const mcpTools = [
|
|
|
3698
3699
|
const DONE = new Set(["implemented", "tested"]);
|
|
3699
3700
|
const active = requirements.filter(r => r.status !== "superseded" && r.status !== "rejected");
|
|
3700
3701
|
const row = (s) => {
|
|
3702
|
+
const base = { id: s.id, name: s.name, status: s.status, startDate: s.startDate || "", releaseDate: s.releaseDate || "" };
|
|
3703
|
+
// sprint.completion-snapshot: completing moves the unfinished out, so only the stored numbers show what was planned.
|
|
3704
|
+
if (s.status === "completed" && s.completionStats) {
|
|
3705
|
+
return { ...base, planned: s.completionStats.planned, done: s.completionStats.done, moved: s.completionStats.moved, fromSnapshot: true };
|
|
3706
|
+
}
|
|
3701
3707
|
const reqs = active.filter(r => r.sprintId === s.id);
|
|
3702
|
-
return {
|
|
3708
|
+
return { ...base, planned: reqs.length, done: reqs.filter(r => DONE.has(r.status)).length, ...(s.status === "completed" ? { fromSnapshot: false } : {}) };
|
|
3703
3709
|
};
|
|
3704
3710
|
const completed = sprints.filter(s => s.status === "completed").map(row);
|
|
3705
3711
|
const withWork = completed.filter(s => s.planned > 0);
|
|
3706
3712
|
const avg = withWork.length ? withWork.reduce((n, s) => n + s.done, 0) / withWork.length : null;
|
|
3713
|
+
const rate = withWork.length ? withWork.reduce((n, s) => n + s.done / s.planned, 0) / withWork.length : null;
|
|
3707
3714
|
return {
|
|
3708
3715
|
completedSprints: completed,
|
|
3709
3716
|
averageDonePerCompletedSprint: avg === null ? null : Math.round(avg * 10) / 10,
|
|
3717
|
+
averageCompletionRate: rate === null ? null : Math.round(rate * 100) / 100,
|
|
3710
3718
|
openSprints: sprints.filter(s => s.status !== "completed").map(row),
|
|
3711
3719
|
unplannedApprovedRequirements: active.filter(r => r.status === "approved" && !r.sprintId).length,
|
|
3712
3720
|
};
|
|
@@ -3714,7 +3722,7 @@ const mcpTools = [
|
|
|
3714
3722
|
},
|
|
3715
3723
|
{
|
|
3716
3724
|
name: "propose_sprint_plan",
|
|
3717
|
-
description: "Save a sprint plan as a PENDING proposal instead of applying it. A project member reviews it in qa-tools (Sprints → Plan proposals), selects rows and approves — Claude can never approve. Use when the user isn't in this conversation, or asks to decide later. Only approved,
|
|
3725
|
+
description: "Save a sprint plan as a PENDING proposal instead of applying it. A project member reviews it in qa-tools (Sprints → Plan proposals), selects rows and approves — Claude can never approve. Use when the user isn't in this conversation, or asks to decide later. Only functional requirements: approved ones without a sprint, or — as a move — approved or in-progress ones in an overdue sprint (they keep status and assignee). Each row targets an existing sprintId OR a newSprintRef from newSprints. The whole proposal is refused if any row can't be planned.",
|
|
3718
3726
|
inputSchema: mcpSchema({
|
|
3719
3727
|
goal: mcpStr("What the plan optimises for, e.g. 'Release 4.0 by Nov 18'"),
|
|
3720
3728
|
summary: mcpStr("Short rationale: capacity used, dependency order, risks"),
|
|
@@ -3974,12 +3982,13 @@ Follow these steps in order:
|
|
|
3974
3982
|
|
|
3975
3983
|
1. Gather facts, don't guess: list_sprints, sprint_velocity, list_epics, list_requirements (status approved, plus anything already planned in open sprints).
|
|
3976
3984
|
2. Draft a plan. Only requirements are planned — never create backlog items as tasks. Rules:
|
|
3977
|
-
- Only status=approved, functional requirements without a sprint are candidates. Non-functional (compliance) requirements are continuous — never plan them. Never touch completed sprints or requirements
|
|
3985
|
+
- Only status=approved, functional requirements without a sprint are candidates. Non-functional (compliance) requirements are continuous — never plan them. Never touch completed sprints or the requirements in them. Requirements in other sprints stay where they are, except carry-over from overdue sprints (below).
|
|
3978
3986
|
- An epic's requirements never go into an earlier sprint than the requirements of the epics it dependsOn.
|
|
3979
3987
|
- Order by priority (1 first), then epic priority.
|
|
3980
|
-
- Per sprint, plan roughly averageDonePerCompletedSprint requirements (from sprint_velocity), counting what is already planned there. If there is no history, say so and propose a conservative number.
|
|
3988
|
+
- Per sprint, plan roughly averageDonePerCompletedSprint requirements (from sprint_velocity), counting what is already planned there. If there is no history, say so and propose a conservative number. Mention averageCompletionRate (the share of planned requirements that usually gets done) in the proposal.
|
|
3989
|
+
- Carry-over: a sprint is overdue when its end date (releaseDate) is before today and it is not completed. Requirements in an overdue sprint that are approved or in progress are candidates to MOVE to an open sprint; they keep their status and assignee, and the reason names the overdue sprint. Never move requirements out of a sprint that has not passed its end date.
|
|
3981
3990
|
- If the requirements don't fit in the existing sprints, propose new sprints (name + end date) — don't create them yet.
|
|
3982
|
-
3. Present the proposal as a table: sprint | requirement key | title | reason (priority / epic dependency / capacity). Also list what you deliberately left out and why, and any dependency conflicts you found.
|
|
3991
|
+
3. Present the proposal as a table: sprint | requirement key | title | reason (priority / epic dependency / capacity). Show moves out of overdue sprints as their own rows, marked as moves, separate from newly planned requirements. Also list what you deliberately left out and why, and any dependency conflicts you found.
|
|
3983
3992
|
4. STOP and ask the user: approve here, or save it as a proposal to decide later in qa-tools? Change nothing before that. Apply any adjustments the user asks for and show the table again.
|
|
3984
3993
|
- If nobody is there to answer (an unattended run), or the user chooses "later": call propose_sprint_plan with the same rows, and report the result. Do not apply anything yourself.
|
|
3985
3994
|
5. After approval in this conversation: create_sprint for any new sprints, then update_requirement with sprintId for each planned requirement. Report each change and any refusal verbatim — never retry a refused change in a different way.
|