From b9ef018619b1e431488b0fe9de4699fa68253521 Mon Sep 17 00:00:00 2001 From: Sebastien Taggart Date: Fri, 10 Apr 2026 09:38:33 -0400 Subject: [PATCH] Add Verification / QA effort complexity indicator to issue body template --- .agents/skills/start/SKILL.md | 14 ++++++++++++-- .claude/commands/start.md | 14 ++++++++++++-- .cursor/rules/start.mdc | 14 ++++++++++++-- .gemini/skills/start/SKILL.md | 14 ++++++++++++-- skills/start.md | 12 +++++++++++- 5 files changed, 59 insertions(+), 9 deletions(-) diff --git a/.agents/skills/start/SKILL.md b/.agents/skills/start/SKILL.md index 740cfa5..92be2cc 100644 --- a/.agents/skills/start/SKILL.md +++ b/.agents/skills/start/SKILL.md @@ -115,12 +115,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a ## General Approach +## Complexity +**Verification / QA effort:** + + ## Acceptance Criteria - - ``` -All four sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). +All five sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). + +**Complexity scale guidance (for agent use only — do not include the scale definition in the issue body):** +- **trivial** — single obvious check (e.g. color change, label text, toggle visibility) +- **moderate** — a few scenarios to verify, minor setup needed (e.g. form validation, a new UI component with a couple of states) +- **significant** — many scenarios, data setup, or cross-feature impact (e.g. multi-step workflow, permission changes across roles) +- **extensive** — complex data flows, integration testing, or edge cases spanning multiple areas (e.g. data import/export mapping, API contract changes consumed by multiple clients) **Title rules:** - ✅ `Fix 'Contact Us' footer link pointing to 404 instead of /contact-us` @@ -244,4 +254,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit --remove-assignee @me`. - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`. - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation. - + diff --git a/.claude/commands/start.md b/.claude/commands/start.md index dc9d2b3..2bd19c1 100644 --- a/.claude/commands/start.md +++ b/.claude/commands/start.md @@ -110,12 +110,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a ## General Approach +## Complexity +**Verification / QA effort:** + + ## Acceptance Criteria - - ``` -All four sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). +All five sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). + +**Complexity scale guidance (for agent use only — do not include the scale definition in the issue body):** +- **trivial** — single obvious check (e.g. color change, label text, toggle visibility) +- **moderate** — a few scenarios to verify, minor setup needed (e.g. form validation, a new UI component with a couple of states) +- **significant** — many scenarios, data setup, or cross-feature impact (e.g. multi-step workflow, permission changes across roles) +- **extensive** — complex data flows, integration testing, or edge cases spanning multiple areas (e.g. data import/export mapping, API contract changes consumed by multiple clients) **Title rules:** - ✅ `Fix 'Contact Us' footer link pointing to 404 instead of /contact-us` @@ -239,4 +249,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit --remove-assignee @me`. - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`. - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation. - + diff --git a/.cursor/rules/start.mdc b/.cursor/rules/start.mdc index 56b6728..54ca08c 100644 --- a/.cursor/rules/start.mdc +++ b/.cursor/rules/start.mdc @@ -116,12 +116,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a ## General Approach +## Complexity +**Verification / QA effort:** + + ## Acceptance Criteria - - ``` -All four sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). +All five sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). + +**Complexity scale guidance (for agent use only — do not include the scale definition in the issue body):** +- **trivial** — single obvious check (e.g. color change, label text, toggle visibility) +- **moderate** — a few scenarios to verify, minor setup needed (e.g. form validation, a new UI component with a couple of states) +- **significant** — many scenarios, data setup, or cross-feature impact (e.g. multi-step workflow, permission changes across roles) +- **extensive** — complex data flows, integration testing, or edge cases spanning multiple areas (e.g. data import/export mapping, API contract changes consumed by multiple clients) **Title rules:** - ✅ `Fix 'Contact Us' footer link pointing to 404 instead of /contact-us` @@ -245,4 +255,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit --remove-assignee @me`. - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`. - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation. - + diff --git a/.gemini/skills/start/SKILL.md b/.gemini/skills/start/SKILL.md index 5ad7329..28593a4 100644 --- a/.gemini/skills/start/SKILL.md +++ b/.gemini/skills/start/SKILL.md @@ -115,12 +115,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a ## General Approach +## Complexity +**Verification / QA effort:** + + ## Acceptance Criteria - - ``` -All four sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). +All five sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). + +**Complexity scale guidance (for agent use only — do not include the scale definition in the issue body):** +- **trivial** — single obvious check (e.g. color change, label text, toggle visibility) +- **moderate** — a few scenarios to verify, minor setup needed (e.g. form validation, a new UI component with a couple of states) +- **significant** — many scenarios, data setup, or cross-feature impact (e.g. multi-step workflow, permission changes across roles) +- **extensive** — complex data flows, integration testing, or edge cases spanning multiple areas (e.g. data import/export mapping, API contract changes consumed by multiple clients) **Title rules:** - ✅ `Fix 'Contact Us' footer link pointing to 404 instead of /contact-us` @@ -244,4 +254,4 @@ When done, say: **"The code is ready for review. Please run `make dev` and test - The issue is assigned to `@me` at creation. If you are creating a ticket on someone else's behalf, remove the assignee after creation with `gh issue edit --remove-assignee @me`. - Apply resolved labels and milestone to every new issue. Label resolution order: per-invocation flag → pool selection from `bug, documentation, enhancement, chore` → omit `--label` entirely. Never apply a label outside `bug, documentation, enhancement, chore`. - Milestone resolution order: per-invocation flag → auto-detected from GitHub open milestones. Never prompt for a milestone more than once per invocation. - + diff --git a/skills/start.md b/skills/start.md index 0f72dc6..19d448f 100644 --- a/skills/start.md +++ b/skills/start.md @@ -158,12 +158,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a ## General Approach +## Complexity +**Verification / QA effort:** + + ## Acceptance Criteria - - ``` -All four sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). +All five sections are required. Write for a non-developer audience — no code, no file paths. Acceptance Criteria must be concrete and verifiable (not vague goals). + +**Complexity scale guidance (for agent use only — do not include the scale definition in the issue body):** +- **trivial** — single obvious check (e.g. color change, label text, toggle visibility) +- **moderate** — a few scenarios to verify, minor setup needed (e.g. form validation, a new UI component with a couple of states) +- **significant** — many scenarios, data setup, or cross-feature impact (e.g. multi-step workflow, permission changes across roles) +- **extensive** — complex data flows, integration testing, or edge cases spanning multiple areas (e.g. data import/export mapping, API contract changes consumed by multiple clients) **Title rules:** - ✅ `Fix 'Contact Us' footer link pointing to 404 instead of /contact-us`