Add complexity indicator to issue body template

.agents/skills/start/SKILL.md

@@ -115,12 +115,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a
 ## General Approach
 <high-level direction for the fix, in plain language>
 
+## Complexity
+**Verification / QA effort:** <trivial | moderate | significant | extensive>
+<one-line justification — what makes verification easy or hard for this specific change>
+
 ## Acceptance Criteria
 - <specific, verifiable outcome>
 - <another outcome>
 ```
 
-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 <number> --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.
-<!-- generated by CodeCannon/sync.sh | skill: start | adapter: codex | hash: c10aad5a | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: codex | hash: 82e58cdb | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.claude/commands/start.md

@@ -110,12 +110,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a
 ## General Approach
 <high-level direction for the fix, in plain language>
 
+## Complexity
+**Verification / QA effort:** <trivial | moderate | significant | extensive>
+<one-line justification — what makes verification easy or hard for this specific change>
+
 ## Acceptance Criteria
 - <specific, verifiable outcome>
 - <another outcome>
 ```
 
-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 <number> --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.
-<!-- generated by CodeCannon/sync.sh | skill: start | adapter: claude | hash: c3649e3f | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: claude | hash: fdee6966 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.cursor/rules/start.mdc

@@ -116,12 +116,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a
 ## General Approach
 <high-level direction for the fix, in plain language>
 
+## Complexity
+**Verification / QA effort:** <trivial | moderate | significant | extensive>
+<one-line justification — what makes verification easy or hard for this specific change>
+
 ## Acceptance Criteria
 - <specific, verifiable outcome>
 - <another outcome>
 ```
 
-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 <number> --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.
-<!-- generated by CodeCannon/sync.sh | skill: start | adapter: cursor | hash: 7481a231 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: cursor | hash: 2d9d7aa1 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

.gemini/skills/start/SKILL.md

@@ -115,12 +115,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a
 ## General Approach
 <high-level direction for the fix, in plain language>
 
+## Complexity
+**Verification / QA effort:** <trivial | moderate | significant | extensive>
+<one-line justification — what makes verification easy or hard for this specific change>
+
 ## Acceptance Criteria
 - <specific, verifiable outcome>
 - <another outcome>
 ```
 
-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 <number> --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.
-<!-- generated by CodeCannon/sync.sh | skill: start | adapter: gemini | hash: d632050d | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->
+<!-- generated by CodeCannon/sync.sh | skill: start | adapter: gemini | hash: 975ce0c7 | DO NOT EDIT — run CodeCannon/sync.sh to regenerate -->

skills/start.md

@@ -158,12 +158,22 @@ Resolve labels and milestone using the resolution steps in the Parsing section a
 ## General Approach
 <high-level direction for the fix, in plain language>
 
+## Complexity
+**Verification / QA effort:** <trivial | moderate | significant | extensive>
+<one-line justification — what makes verification easy or hard for this specific change>
+
 ## Acceptance Criteria
 - <specific, verifiable outcome>
 - <another outcome>
 ```
 
-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`