qatools-cli 1.2.6 → 1.2.8

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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/qatools.js +21 -12
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "qatools-cli",
3
- "version": "1.2.6",
3
+ "version": "1.2.8",
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
@@ -1043,7 +1043,7 @@ program
1043
1043
  } else {
1044
1044
  console.log(`\n${reqs.length} requirement${reqs.length !== 1 ? 's' : ''}:\n`);
1045
1045
  for (const r of reqs) {
1046
- const badge = r.status === "rejected" ? "❌" : r.status === "approved" ? "✅" : r.status === "tested" ? "🟢" : r.status === "implemented" ? "🟡" : r.status === "superseded" ? "🗑" : "📝";
1046
+ const badge = r.status === "rejected" ? "❌" : r.status === "approved" ? "✅" : r.status === "in_progress" ? "🔨" : r.status === "tested" ? "🟢" : r.status === "implemented" ? "🟡" : r.status === "superseded" ? "🗑" : "📝";
1047
1047
  const epic = r.epicKey ? ` epic:${r.epicKey}` : ' (no epic)';
1048
1048
  console.log(` ${badge} [${r.key}]${epic} ${r.title} (${r.status})`);
1049
1049
  if (r.reviewComment) console.log(` 💬 ${r.reviewComment}`);
@@ -1457,7 +1457,8 @@ program
1457
1457
  .description("Update one or more requirements (by id, optionally from a JSON file). status=implemented/tested REQUIRES --evidence.")
1458
1458
  .option("-f, --file <path>", "JSON file with updates: { '<requirementId>': { status, epicKey, evidence, ... } }")
1459
1459
  .option("-i, --id <id>", "Single requirement ID to update")
1460
- .option("--status <status>", "New status (draft/approved/rejected/implemented/tested/superseded)")
1460
+ .option("--status <status>", "New status (draft/approved/in_progress/rejected/implemented/tested/superseded)")
1461
+ .option("--assigned <email>", "Set assignee: a member's email, 'me' (you, or the Claude account for an API key), or empty string to clear")
1461
1462
  .option("--evidence <text>", "REQUIRED when status=implemented or tested. Cite test output, file:line, expected vs actual, or 'no test applies because <reason>'.")
1462
1463
  .option("--attach <files...>", "Image file(s) as evidence (png/jpg/webp/gif, max 4 MB each)")
1463
1464
  .option("--epic <key>", "Set epicKey")
@@ -1489,6 +1490,7 @@ program
1489
1490
  } else if (options.id) {
1490
1491
  const u = {};
1491
1492
  if (options.status) u.status = options.status;
1493
+ if (options.assigned !== undefined) u.assignedTo = options.assigned;
1492
1494
  if (options.epic !== undefined) u.epicKey = options.epic;
1493
1495
  if (options.sprint !== undefined) u.sprintId = options.sprint;
1494
1496
  if (options.type) u.type = options.type;
@@ -2539,22 +2541,26 @@ App Context → Epics → Requirements → Sprint → Implementation → Test
2539
2541
  \`qatools context\`
2540
2542
  \`qatools requirements --status approved -o requirements.json\`
2541
2543
 
2542
- 2. Implement according to acceptanceCriteria AND negativeCriteria.
2544
+ 2. Before you start on a requirement, mark it in progress so others can see who works on it:
2545
+ \`qatools requirement-update -i <requirementId> --status in_progress --assigned me\`
2546
+
2547
+ 3. Implement according to acceptanceCriteria AND negativeCriteria.
2543
2548
  Every piece of code must be traceable to a requirementKey.
2549
+ When done and verified: \`--status implemented --evidence "<verification>"\`. If you stop without finishing, set it back to \`approved\` (clears the assignee).
2544
2550
 
2545
- 3. If you discover something unexpected during implementation:
2551
+ 4. If you discover something unexpected during implementation:
2546
2552
  - Behavior doesn't match a requirement → create AVV: \`qatools backlog-create -d "..." -t bug --requirement-key <key>\`
2547
2553
  - Requirement is missing or unclear → create GAP: \`qatools backlog-create -d "..." -t requirement_gap --requirement-key <key>\`
2548
2554
  - Technical issue (infra, runtime) → create DEF: \`qatools backlog-create -d "..." -t technical_defect\`
2549
2555
  - Improvement idea → create IMP: \`qatools backlog-create -d "..." -t improvement\`
2550
2556
 
2551
- 4. NEVER create requirements directly as backlog items. If a GAP needs to become a requirement, flag it — the user decides.
2557
+ 5. NEVER create requirements directly as backlog items. If a GAP needs to become a requirement, flag it — the user decides.
2552
2558
 
2553
- 5. Check for pending test sessions:
2559
+ 6. Check for pending test sessions:
2554
2560
  \`qatools pending\`
2555
2561
  \`qatools read-session -s <id> -o session.json\`
2556
2562
 
2557
- 6. If tests fail, analyze and fix:
2563
+ 7. If tests fail, analyze and fix:
2558
2564
  \`qatools upload-analysis -s <id> -f analysis.json\`
2559
2565
 
2560
2566
  ## Rules
@@ -2689,13 +2695,14 @@ If the qa-tools MCP server (\`qatools mcp\`) is available, use its tools and the
2689
2695
  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
2696
 
2691
2697
  2. Draft a proposal:
2692
- - Only approved requirements without a sprint are candidates.
2698
+ - Only approved, functional requirements without a sprint are candidates. Continuous (non-functional) requirements are never planned — they are checked against every sprint.
2693
2699
  - Never touch completed sprints or requirements in one — the backend refuses.
2694
2700
  - An epic's requirements never go before the requirements of the epics it dependsOn.
2695
2701
  - Priority 1 first, then epic priority.
2702
+ - Per sprint: roughly the capacity average, counting requirements already in the sprint.
2696
2703
  - If existing sprints don't fit, propose new ones (name + end date) — don't create them yet.
2697
2704
 
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.
2705
+ 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
2706
 
2700
2707
  4. Apply after approval:
2701
2708
  \`qatools sprint-create --name "Release 4.1" --end 2026-12-15\`
@@ -3507,6 +3514,7 @@ const MCP_INSTRUCTIONS = `qa-tools: requirements-driven QA. Rules that apply to
3507
3514
  - The backlog is signals (bug=AVV, requirement_gap=GAP, technical_defect=DEF, improvement=IMP), not a task list.
3508
3515
  - Backlog flow: open → in_progress → ready_for_test → resolved. Set ready_for_test when you believe a fix is done; resolved needs evidence (min 10 chars) and, except GAP, a prior ready_for_test.
3509
3516
  - Requirement status implemented/tested needs evidence: test output, file:line, expected vs actual, or "no test applies because <reason>".
3517
+ - Requirement flow: approved → in_progress → implemented → tested. When you start implementing an approved requirement, set status in_progress and assignedTo "me" (update_requirement); if you stop without finishing, set it back to approved.
3510
3518
  - Sprint planning: plan approved, functional requirements only (update_requirement sprintId), never backlog items; non-functional requirements are continuous and never go into sprints. Gather facts first (list_sprints, sprint_velocity, list_epics, list_requirements), respect epic dependsOn, present the plan as a table (sprint | requirement | reason) and change NOTHING until the user approves it in this conversation. If the user isn't here or wants to decide later, save it with propose_sprint_plan instead — they approve in qa-tools. Full procedure: prompt plan_sprints.
3511
3519
  - Every tool takes an optional projectId; without it the configured project (qatools setup) is used.`;
3512
3520
 
@@ -3515,7 +3523,7 @@ const mcpInt = (description, extra = {}) => ({ type: "integer", description, ...
3515
3523
  const mcpBool = (description) => ({ type: "boolean", description });
3516
3524
  const mcpStrArray = (description, items = { type: "string" }) => ({ type: "array", items, description });
3517
3525
  const MCP_PROJECT_PROP = { projectId: mcpStr("Project ID. Defaults to the configured project.") };
3518
- const MCP_REQ_STATUSES = ["draft", "approved", "rejected", "implemented", "tested", "superseded"];
3526
+ const MCP_REQ_STATUSES = ["draft", "approved", "in_progress", "rejected", "implemented", "tested", "superseded"];
3519
3527
  const MCP_BACKLOG_STATUSES = ["open", "in_progress", "ready_for_test", "resolved", "rejected"];
3520
3528
  const MCP_BACKLOG_TYPES = ["bug", "improvement", "requirement_gap", "technical_defect"];
3521
3529
  const MCP_PRIORITY = mcpInt("Priority: 1 (high), 2 (medium), 3 (low)", { enum: [1, 2, 3] });
@@ -3599,10 +3607,11 @@ const mcpTools = [
3599
3607
  },
3600
3608
  {
3601
3609
  name: "update_requirement",
3602
- description: "Update a requirement (status, epic, sprint, text). status implemented/tested REQUIRES evidence. Set sprintId to plan the requirement in a sprint, or empty string to unplan it.",
3610
+ description: "Update a requirement (status, assignee, epic, sprint, text). status implemented/tested REQUIRES evidence. When you start implementing an approved requirement, set status in_progress and assignedTo \"me\". Set sprintId to plan the requirement in a sprint, or empty string to unplan it.",
3603
3611
  inputSchema: mcpSchema({
3604
3612
  requirementId: mcpStr("Requirement document ID"),
3605
3613
  status: mcpStr("New status", { enum: MCP_REQ_STATUSES }),
3614
+ assignedTo: mcpStr("Assignee: a member's email, \"me\" (the Claude account), or empty string to clear. Setting status back to approved clears it."),
3606
3615
  evidence: mcpStr("Required for implemented/tested (min 10 chars): test output, file:line, expected vs actual, or 'no test applies because <reason>'"),
3607
3616
  epicKey: mcpStr("Epic key"),
3608
3617
  sprintId: mcpStr("Sprint ID (empty string clears)"),
@@ -3613,7 +3622,7 @@ const mcpTools = [
3613
3622
  attachments: mcpStrArray("Local image file paths (png/jpg/webp/gif, max 4 MB) to attach to the evidence, e.g. screenshots"),
3614
3623
  }, ["requirementId"]),
3615
3624
  run: async (a) => {
3616
- const updates = mcpPick(a, ["status", "epicKey", "sprintId", "type", "title", "description", "acceptanceCriteria"]);
3625
+ const updates = mcpPick(a, ["status", "assignedTo", "epicKey", "sprintId", "type", "title", "description", "acceptanceCriteria"]);
3617
3626
  if (Object.keys(updates).length === 0) throw new McpToolError("No fields to update.");
3618
3627
  const evidenceById = a.evidence ? { [a.requirementId]: a.evidence } : {};
3619
3628
  if (requirementEvidenceViolations({ [a.requirementId]: updates }, evidenceById).length > 0) {