fix: update stale task terminology to skill after format conversion

Address review findings from PR #1857: replace remaining "task"
references with "skill" in workflow steps and test documentation.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

src/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md

@@ -1,13 +1,13 @@
 ---
 name: 'step-05-adversarial-review'
-description: 'Construct diff and invoke adversarial review task'
+description: 'Construct diff and invoke adversarial review skill'
 
 nextStepFile: './step-06-resolve-findings.md'
 ---
 
 # Step 5: Adversarial Code Review
 
-**Goal:** Construct diff of all changes, invoke adversarial review task, present findings.
+**Goal:** Construct diff of all changes, invoke adversarial review skill, present findings.
 
 ---
 
@@ -65,7 +65,7 @@ Pass `{diff_output}` as the content to review. The skill should return a list of
 
 ### 3. Process Findings
 
-Capture the findings from the task output.
+Capture the findings from the skill output.
 **If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance.
 Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided).
 DO NOT exclude findings based on severity or validity unless explicitly asked to do so.
@@ -85,7 +85,7 @@ With findings in hand, read fully and follow: `{project-root}/_bmad/bmm/workflow
 
 - Diff constructed from baseline_commit
 - New files included in diff
-- Task invoked with diff as input
+- Skill invoked with diff as input
 - Findings received
 - Findings processed into TODOs or table and presented to user
 
@@ -93,6 +93,6 @@ With findings in hand, read fully and follow: `{project-root}/_bmad/bmm/workflow
 
 - Missing baseline_commit (can't construct accurate diff)
 - Not including new untracked files in diff
-- Invoking task without providing diff input
+- Invoking skill without providing diff input
 - Accepting zero findings without questioning
-- Presenting fewer findings than the review task returned without explicit instruction to do so
+- Presenting fewer findings than the review skill returned without explicit instruction to do so

src/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md

@@ -156,7 +156,7 @@ b) **HALT and wait for user selection.**
        > Pass `{finalFile}` as the content to review. The skill should return a list of findings.
 
     2. **Process Findings**:
-       > Capture the findings from the task output.
+       > Capture the findings from the skill output.
        > **If zero findings:** HALT - this is suspicious. Re-analyze or request user guidance.
        > Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undecided).
        > DO NOT exclude findings based on severity or validity unless explicitly asked to do so.

test/adversarial-review-tests/README.md

@@ -1,6 +1,6 @@
 # Adversarial Review Test Suite
 
-Tests for the `also_consider` optional input in `review-adversarial-general.xml`.
+Tests for the `also_consider` optional input in the `bmad-review-adversarial-general` skill.
 
 ## Purpose
 
@@ -19,12 +19,12 @@ All tests use `sample-content.md` - a deliberately imperfect User Authentication
 
 ## Running Tests
 
-For each test case in `test-cases.yaml`, invoke the adversarial review task.
+For each test case in `test-cases.yaml`, invoke the adversarial review skill.
 
 ### Manual Test Invocation
 
 ```
-Review this content using the adversarial review task:
+Review this content using the adversarial review skill:
 
 <content>
 [paste sample-content.md]

test/adversarial-review-tests/test-cases.yaml

@@ -1,9 +1,9 @@
-# Test Cases for review-adversarial-general.xml with also_consider input
+# Test Cases for bmad-review-adversarial-general skill with also_consider input
 #
 # Purpose: Evaluate how the optional also_consider input influences review findings
 # Content: All tests use sample-content.md (User Authentication API docs)
 #
-# To run: Manually invoke the task with each configuration and compare outputs
+# To run: Manually invoke the skill with each configuration and compare outputs
 
 test_cases:
   # BASELINE - No also_consider