chore:remove stale label references (#1826)

Author: tyler-dane

.agents/skills/bug-capture/SKILL.md

@@ -63,10 +63,7 @@ label.
 ### 4. Prepare GitHub
 
 - Use GitHub Issues through `gh`, inferred from the current repo remote.
-- Ensure a `bug` label exists; create it if missing.
-- Normal capture: apply `bug` and `needs-triage`.
-- Incomplete capture: apply `bug` and `needs more info`. If an obvious equivalent
-  already exists use it instead of creating a  duplicate.
+- Apply the `bug` type to the issue (do NOT create a `bug` label)
 
 ### 5. Dedupe
 

.agents/skills/to-issues/SKILL.md

@@ -51,8 +51,6 @@ Iterate until the user approves the breakdown.
 
 ### 5. Publish the issues to the issue tracker
 
-For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. Apply the `needs-triage` triage label so each issue enters the normal triage flow.
-
 Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
 
 <issue-template>

.agents/skills/to-prd/SKILL.md

@@ -17,7 +17,7 @@ A deep module (as opposed to a shallow module) is one which encapsulates a lot o
 
 Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
 
-3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `needs-triage` triage label so it enters the normal triage flow.
+3. Write the PRD using the template below, then publish it to the project issue tracker.
 
 <prd-template>