Trim centralized autonomous-workflow sections from CLAUDE.md

.github/workflows/analysis.yml

@@ -5,16 +5,8 @@ name: Code Analysis
 on:
   push:
     branches: [ "main" ]
-    paths-ignore:
-      - '**.md'
-      - 'LICENSE'
-      - 'docs/**'
   pull_request:
     branches: [ "main" ]
-    paths-ignore:
-      - '**.md'
-      - 'LICENSE'
-      - 'docs/**'
 
 permissions:
   contents: read

CLAUDE.md

@@ -46,30 +46,10 @@ When planning tasks, provide concrete implementation steps without time estimate
 - "Implementation involves: parsing new environment variable, updating repository selection logic, and adding tests"
 - Focus on technical scope and complexity, not duration
 
-## Track issues and blockers
-
-* When blocked in your development because you're missing some capability (e.g. MCP server or access to a specific development tool in your environment), create an issue in this Github repository to describe what's missing
-* The issue title should contain `[Claude]` as a prefix. e.g. `[Claude] Missing tool: <some_tool>`
-* Check beforehand that a similar issue does not exist. If one does exist, consider adding additional context and information based on the current task at hand
-* Avoid duplicate content in the Github issue as this will be read by humans. Consider editing existing comments to refine the explanations rather than adding new comments
-* Do not apply the `claude` tag to the issue yourself
-* Remember to use the same footer as for other discussions to indicate that the issue content or comment was generated by Claude
-
 ## Clean-up changes
 
 * When removing logic, don't leave comments about it. If things don't exist, we don't need to mention them
 
-## Work Control
-
-Only work on issues with the `claude` label and no open dependencies. The `find-work` skill handles task detection and priority routing.
-
-* NEVER add the `claude` label on a Github issue yourself unless it's requested explicitly
-* NEVER work on an issue that depends on functionality added by another open issue
-
-## Issue Dependencies
-
-* Never use GitHub's sub-issue/parent-issue feature (addSubIssue/removeSubIssue). Use native blocked-by dependencies exclusively.
-
 ## Skill Creation
 
 When creating skills, invoke both `/skill-development` and `/skill-creator` for comprehensive coverage. They provide complementary guidance: `/skill-creator` covers core design principles and conciseness, while `/skill-development` covers writing style rules, trigger descriptions, and validation.