docs: hyphenate Ops pattern slugs and update cross-references

.github/aw/create-agentic-workflow.md

@@ -313,7 +313,7 @@ These resources contain workflow patterns, best practices, safe outputs, and per
    - Need to trigger workflows in other repos (use separate workflow in target repo)
 
    **Documentation Reference:**
-   - Full guide: https://github.github.com/gh-aw/patterns/multirepoops/
+   - Full guide: https://github.github.com/gh-aw/patterns/multi-repo-ops/
    - Safe Outputs Reference: https://github.github.com/gh-aw/reference/safe-outputs/
    - GitHub Tools: https://github.github.com/gh-aw/reference/tools/#github-tools-github
 
@@ -668,7 +668,7 @@ When you identify issues requiring tracking:
 ```
 
 **Reference Documentation:**
-- https://github.github.com/gh-aw/patterns/multirepoops/
+- https://github.github.com/gh-aw/patterns/multi-repo-ops/
 
 ### Step 3: Create the Workflow File
 

docs/astro.config.mjs

@@ -181,20 +181,20 @@ export default defineConfig({
 				{
 					label: 'Design Patterns',
 					items: [
-						{ label: 'ChatOps', link: '/patterns/chatops/' },
-						{ label: 'DailyOps', link: '/patterns/dailyops/' },
-						{ label: 'DataOps', link: '/patterns/dataops/' },
-						{ label: 'DispatchOps', link: '/patterns/dispatchops/' },
-						{ label: 'IssueOps', link: '/patterns/issueops/' },
-						{ label: 'LabelOps', link: '/patterns/labelops/' },
-						{ label: 'MultiRepoOps', link: '/patterns/multirepoops/' },
+						{ label: 'ChatOps', link: '/patterns/chat-ops/' },
+						{ label: 'DailyOps', link: '/patterns/daily-ops/' },
+						{ label: 'DataOps', link: '/patterns/data-ops/' },
+						{ label: 'DispatchOps', link: '/patterns/dispatch-ops/' },
+						{ label: 'IssueOps', link: '/patterns/issue-ops/' },
+						{ label: 'LabelOps', link: '/patterns/label-ops/' },
+						{ label: 'MultiRepoOps', link: '/patterns/multi-repo-ops/' },
 						{ label: 'Monitoring', link: '/patterns/monitoring/' },
 						{ label: 'Orchestration', link: '/patterns/orchestration/' },
-						{ label: 'ProjectOps', link: '/patterns/projectops/' },
-						{ label: 'SideRepoOps', link: '/patterns/siderepoops/' },
-						{ label: 'SpecOps', link: '/patterns/specops/' },
-						{ label: 'TaskOps', link: '/patterns/taskops/' },
-						{ label: 'TrialOps', link: '/patterns/trialops/' },
+						{ label: 'ProjectOps', link: '/patterns/project-ops/' },
+						{ label: 'SideRepoOps', link: '/patterns/side-repo-ops/' },
+						{ label: 'SpecOps', link: '/patterns/spec-ops/' },
+						{ label: 'TaskOps', link: '/patterns/task-ops/' },
+						{ label: 'TrialOps', link: '/patterns/trial-ops/' },
 					],
 				},
 				{

docs/src/content/docs/blog/2026-01-13-meet-the-workflows-continuous-improvement.md

@@ -41,7 +41,7 @@ This ensures recently updated modules get reviewed first since new features migh
 
 For each module, Go Module Usage Expert researches the repository (releases, docs, best practices), analyzes actual usage patterns using Serena, and generates actionable recommendations. It saves summaries under `scratchpad/mods/` and opens GitHub Discussions.
 
-The output of Go Module Usage Expert is a discussion, which is then often "task mined" for actionable tasks using the [TaskOps](https://github.github.com/gh-aw/patterns/taskops/) design pattern.
+The output of Go Module Usage Expert is a discussion, which is then often "task mined" for actionable tasks using the [TaskOps](https://github.github.com/gh-aw/patterns/task-ops/) design pattern.
 
 Let's take a look at an example of how this works:
 
@@ -60,7 +60,7 @@ Typist looks for untyped usages: `interface{}` or `any` where specific types wou
 
 Using grep patterns and Serena's semantic analysis, it discovers type definitions, identifies semantic duplicates, analyzes untyped usage patterns, and generates refactoring recommendations.
 
-Typist also uses the [TaskOps](https://github.github.com/gh-aw/patterns/taskops/) pattern. This means the job of Typist is not to fix code, but to analyze code and recommend possible improvements.
+Typist also uses the [TaskOps](https://github.github.com/gh-aw/patterns/task-ops/) pattern. This means the job of Typist is not to fix code, but to analyze code and recommend possible improvements.
 
 Let's take a look at an example of this in practice:
 

docs/src/content/docs/blog/2026-01-27-operational-patterns.md

@@ -76,7 +76,7 @@ Here are our tips!
 - Add help text for `/command help`
 - Use cache-memory to track command history
 
-**Learn more**: [ChatOps Examples](https://github.github.com/gh-aw/patterns/chatops/)
+**Learn more**: [ChatOps Examples](https://github.github.com/gh-aw/patterns/chat-ops/)
 
 ---
 
@@ -124,7 +124,7 @@ Here are our tips!
 - Include progress reports in PR descriptions
 - Allow human intervention at any phase
 
-**Learn more**: [DailyOps Examples](https://github.github.com/gh-aw/patterns/dailyops/)
+**Learn more**: [DailyOps Examples](https://github.github.com/gh-aw/patterns/daily-ops/)
 
 ---
 
@@ -175,7 +175,7 @@ Here are our tips!
 - Update classification rules based on feedback
 - **For public repos**: Consider if you need to [disable lockdown mode](/gh-aw/reference/faq/#what-is-github-lockdown-mode-and-when-is-it-enabled) to process issues from all users (this is one of the rare safe use cases - see [Lockdown Mode](/gh-aw/reference/lockdown-mode/) for security guidance)
 
-**Learn more**: [IssueOps Examples](https://github.github.com/gh-aw/patterns/issueops/)
+**Learn more**: [IssueOps Examples](https://github.github.com/gh-aw/patterns/issue-ops/)
 
 ---
 
@@ -224,7 +224,7 @@ Here are our tips!
 - Avoid label proliferation
 - Use label descriptions
 
-**Learn more**: [LabelOps Examples](https://github.github.com/gh-aw/patterns/labelops/)
+**Learn more**: [LabelOps Examples](https://github.github.com/gh-aw/patterns/label-ops/)
 
 ---
 
@@ -274,7 +274,7 @@ Here are our tips!
 - Allow manual overrides
 - Track automation accuracy
 
-**Learn more**: [ProjectOps Examples](https://github.github.com/gh-aw/patterns/projectops/)
+**Learn more**: [ProjectOps Examples](https://github.github.com/gh-aw/patterns/project-ops/)
 
 ---
 
@@ -337,7 +337,7 @@ Here are our tips!
 - Include acceptance criteria
 - Review and iterate
 
-**Learn more**: [TaskOps](https://github.github.com/gh-aw/patterns/taskops/)
+**Learn more**: [TaskOps](https://github.github.com/gh-aw/patterns/task-ops/)
 
 ---
 
@@ -388,7 +388,7 @@ Here are our tips!
 - Batch operations efficiently
 - Monitor cross-repo dependencies
 
-**Learn more**: [MultiRepoOps](https://github.github.com/gh-aw/patterns/multirepoops/)
+**Learn more**: [MultiRepoOps](https://github.github.com/gh-aw/patterns/multi-repo-ops/)
 
 ---
 
@@ -427,7 +427,7 @@ Here are our tips!
 - Set up appropriate notifications
 - Plan for eventual migration if successful
 
-**Learn more**: [SideRepoOps](https://github.github.com/gh-aw/patterns/siderepoops/)
+**Learn more**: [SideRepoOps](https://github.github.com/gh-aw/patterns/side-repo-ops/)
 
 ---
 
@@ -452,7 +452,7 @@ These workflows do the following:
 5. Capture and validate outputs
 6. Delete trial repo or keep for reference
 
-**Learn more**: [TrialOps](https://github.github.com/gh-aw/patterns/trialops/)
+**Learn more**: [TrialOps](https://github.github.com/gh-aw/patterns/trial-ops/)
 
 ---
 

docs/src/content/docs/examples/comment-triggered.md

@@ -16,7 +16,7 @@ Comment-triggered workflows respond to slash commands typed in GitHub conversati
 
 ## Patterns in This Section
 
-- **[ChatOps](/gh-aw/patterns/chatops/)** - Build interactive automation with command triggers
+- **[ChatOps](/gh-aw/patterns/chat-ops/)** - Build interactive automation with command triggers
 
 ## Example Command Triggers
 

docs/src/content/docs/examples/issue-pr-events.md

@@ -16,9 +16,9 @@ Issue and PR event workflows run automatically when specific GitHub events occur
 
 ## Patterns in This Section
 
-- **[IssueOps](/gh-aw/patterns/issueops/)** - Automate issue triage and management
-- **[LabelOps](/gh-aw/patterns/labelops/)** - Use labels as workflow triggers
-- **[ProjectOps](/gh-aw/patterns/projectops/)** - Automate project board management
+- **[IssueOps](/gh-aw/patterns/issue-ops/)** - Automate issue triage and management
+- **[LabelOps](/gh-aw/patterns/label-ops/)** - Use labels as workflow triggers
+- **[ProjectOps](/gh-aw/patterns/project-ops/)** - Automate project board management
 - **[Triage & Analysis](/gh-aw/examples/issue-pr-events/triage-analysis/)** - Intelligent triage and problem investigation
 - **[Coding & Development](/gh-aw/examples/issue-pr-events/coding-development/)** - PR assistance and code improvements
 - **[Quality & Testing](/gh-aw/examples/issue-pr-events/quality-testing/)** - Automated quality checks

docs/src/content/docs/examples/multi-repo.md

@@ -153,7 +153,7 @@ For organization-wide workflows, use organization-level secrets, configure GitHu
 
 For comprehensive documentation on the MultiRepoOps design pattern, see:
 
-[MultiRepoOps Design Pattern](/gh-aw/patterns/multirepoops/)
+[MultiRepoOps Design Pattern](/gh-aw/patterns/multi-repo-ops/)
 
 ## Related Documentation
 

docs/src/content/docs/examples/multi-repo/feature-sync.md

@@ -269,7 +269,7 @@ For enhanced security, use GitHub App installation tokens. See [GitHub App for S
 
 ## Related Documentation
 
-- [MultiRepoOps Design Pattern](/gh-aw/patterns/multirepoops/) - Complete multi-repo overview
+- [MultiRepoOps Design Pattern](/gh-aw/patterns/multi-repo-ops/) - Complete multi-repo overview
 - [Cross-Repo Issue Tracking](/gh-aw/examples/multi-repo/issue-tracking/) - Issue management patterns
 - [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - Pull request configuration
 - [GitHub Tools](/gh-aw/reference/tools/#github-tools-github) - Repository access tools

docs/src/content/docs/examples/multi-repo/issue-tracking.md

@@ -298,7 +298,7 @@ For enhanced security, use GitHub App installation tokens. See [GitHub App for S
 
 ## Related Documentation
 
-- [MultiRepoOps Design Pattern](/gh-aw/patterns/multirepoops/) - Complete multi-repo overview
+- [MultiRepoOps Design Pattern](/gh-aw/patterns/multi-repo-ops/) - Complete multi-repo overview
 - [Feature Synchronization](/gh-aw/examples/multi-repo/feature-sync/) - Code sync patterns
 - [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - Issue creation configuration
 - [GitHub Tools](/gh-aw/reference/tools/#github-tools-github) - API access configuration

docs/src/content/docs/examples/scheduled.md

@@ -16,7 +16,7 @@ Scheduled workflows run automatically at specified times using cron expressions.
 
 ## Patterns in This Section
 
-- **[DailyOps](/gh-aw/patterns/dailyops/)** - Make incremental improvements through small daily changes
+- **[DailyOps](/gh-aw/patterns/daily-ops/)** - Make incremental improvements through small daily changes
 - **[Research & Planning](/gh-aw/examples/scheduled/research-planning/)** - Automated research, status reports, and planning
 
 ## Example Schedule Triggers

docs/src/content/docs/guides/ephemerals.md

@@ -170,7 +170,7 @@ See [Safe Outputs Reference](/gh-aw/reference/safe-outputs/#hide-older-comments)
 
 Run agentic workflows from a separate "side" repository that targets your main codebase. This isolates AI-generated issues, comments, and workflow runs from your main repository, keeping automation infrastructure separate from production code.
 
-See [SideRepoOps](/gh-aw/patterns/siderepoops/) for complete setup and usage documentation.
+See [SideRepoOps](/gh-aw/patterns/side-repo-ops/) for complete setup and usage documentation.
 
 ### Text Sanitization
 
@@ -237,6 +237,6 @@ This configuration ensures:
 
 - [Triggers Reference](/gh-aw/reference/triggers/) - Complete trigger configuration including `stop-after`
 - [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - All safe output types and expiration options
-- [SideRepoOps](/gh-aw/patterns/siderepoops/) - Complete setup for side repository operations
+- [SideRepoOps](/gh-aw/patterns/side-repo-ops/) - Complete setup for side repository operations
 - [Authentication](/gh-aw/reference/auth/) - Authentication and security considerations
 - [Orchestration](/gh-aw/patterns/orchestration/) - Orchestrating multi-workflow initiatives

docs/src/content/docs/patterns/centralrepoops.mdx → docs/src/content/docs/patterns/central-repo-ops.mdx

@@ -6,7 +6,7 @@ description: Operate and roll out changes across many repositories from a single
 > [!WARNING]
 > **Experimental:** CentralRepoOps is still experimental! Things may break, change, or be removed without deprecation at any time.
 
-CentralRepoOps is a [MultiRepoOps](/gh-aw/patterns/multirepoops/) deployment variant where a single private repository acts as a control plane for large-scale operations across many repositories.
+CentralRepoOps is a [MultiRepoOps](/gh-aw/patterns/multi-repo-ops/) deployment variant where a single private repository acts as a control plane for large-scale operations across many repositories.
 
 Use this pattern when you need to coordinate rollouts, policy updates, and tracking across tens or hundreds of repositories from a private central location, using cross-repository safe outputs and secure authentication to deliver consistency, control, and auditability.
 
@@ -266,6 +266,6 @@ After the setup is complete, you can run the orchestrator with `workflow_dispatc
 
 ## Related Patterns
 
-- **[MultiRepoOps](/gh-aw/patterns/multirepoops/)** - Cross-repository automation capability
+- **[MultiRepoOps](/gh-aw/patterns/multi-repo-ops/)** - Cross-repository automation capability
 - **[Orchestration](/gh-aw/patterns/orchestration/)** - Generic orchestrator/worker dispatch pattern
-- **[SideRepoOps](/gh-aw/patterns/siderepoops/)** - Isolated control-plane setup
+- **[SideRepoOps](/gh-aw/patterns/side-repo-ops/)** - Isolated control-plane setup

docs/src/content/docs/patterns/dataops.md → docs/src/content/docs/patterns/data-ops.md

@@ -246,4 +246,4 @@ Analyze the combined data at `/tmp/gh-aw/combined.json` covering:
 - [Steps Reference](/gh-aw/reference/frontmatter/#custom-steps-steps) - Shell step configuration
 - [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - Validated GitHub operations
 - [Cache Memory](/gh-aw/reference/cache-memory/) - Caching data between runs
-- [DailyOps](/gh-aw/patterns/dailyops/) - Scheduled improvement workflows
+- [DailyOps](/gh-aw/patterns/daily-ops/) - Scheduled improvement workflows

docs/src/content/docs/patterns/dispatchops.md → docs/src/content/docs/patterns/dispatch-ops.md

@@ -333,7 +333,7 @@ gh aw run research --ref feature/improve-workflow
 gh pr create --title "Improve workflow"
 ```
 
-The workflow runs with your branch's code and state. Safe outputs (issues, PRs, comments) are created in your branch context. Use [trial mode](/gh-aw/patterns/trialops/) for completely isolated testing without affecting the production repository.
+The workflow runs with your branch's code and state. Safe outputs (issues, PRs, comments) are created in your branch context. Use [trial mode](/gh-aw/patterns/trial-ops/) for completely isolated testing without affecting the production repository.
 
 ## Common Use Cases
 
@@ -363,7 +363,7 @@ The workflow runs with your branch's code and state. Safe outputs (issues, PRs,
 
 - [Manual Workflows Example](/gh-aw/examples/manual/) - Example manual workflows
 - [Triggers Reference](/gh-aw/reference/triggers/) - Complete trigger syntax including workflow_dispatch
-- [TrialOps](/gh-aw/patterns/trialops/) - Testing workflows in isolation
+- [TrialOps](/gh-aw/patterns/trial-ops/) - Testing workflows in isolation
 - [CLI Commands](/gh-aw/setup/cli/) - Complete gh aw run command reference
 - [Templating](/gh-aw/reference/templating/) - Using expressions and conditionals
 - [Security Best Practices](/gh-aw/introduction/architecture/) - Securing workflow execution

docs/src/content/docs/patterns/labelops.md → docs/src/content/docs/patterns/label-ops.md

@@ -75,6 +75,6 @@ Address label explosion with AI-powered periodic audits for consolidation. Preve
 ## Additional Resources
 
 - [Trigger Events](/gh-aw/reference/triggers/) - Complete trigger configuration including label filtering
-- [IssueOps](/gh-aw/patterns/issueops/) - Learn about issue-triggered workflows
+- [IssueOps](/gh-aw/patterns/issue-ops/) - Learn about issue-triggered workflows
 - [Safe Outputs Reference](/gh-aw/reference/safe-outputs/) - Secure output handling
 - [Frontmatter Reference](/gh-aw/reference/frontmatter/) - Complete workflow configuration options

docs/src/content/docs/patterns/multirepoops.md → docs/src/content/docs/patterns/multi-repo-ops.md

@@ -250,8 +250,8 @@ For organization-wide workflows:
 
 ## Related Patterns
 
-- **[IssueOps](/gh-aw/patterns/issueops/)** - Single-repo issue automation
-- **[ChatOps](/gh-aw/patterns/chatops/)** - Command-driven workflows
+- **[IssueOps](/gh-aw/patterns/issue-ops/)** - Single-repo issue automation
+- **[ChatOps](/gh-aw/patterns/chat-ops/)** - Command-driven workflows
 - **[Orchestration](/gh-aw/patterns/orchestration/)** - Multi-issue initiative coordination
 
 ## Related Documentation

docs/src/content/docs/patterns/projectops.md → docs/src/content/docs/patterns/project-ops.md

@@ -154,5 +154,5 @@ ProjectOps complements [GitHub's built-in Projects automation](https://docs.gith
 - [Projects & Monitoring](/gh-aw/patterns/monitoring/) - Design pattern guide
 - [Orchestration](/gh-aw/patterns/orchestration/) - Design pattern guide
 - [Trigger Events](/gh-aw/reference/triggers/) - Event trigger configuration options
-- [IssueOps](/gh-aw/patterns/issueops/) - Related issue automation patterns
+- [IssueOps](/gh-aw/patterns/issue-ops/) - Related issue automation patterns
 - [Token Reference](/gh-aw/reference/auth/#gh_aw_project_github_token) - GitHub Projects token setup

docs/src/content/docs/patterns/siderepoops.mdx → docs/src/content/docs/patterns/side-repo-ops.mdx

@@ -24,7 +24,7 @@ Use SideRepoOps for workflow experimentation, creating a centralized automation
 
 ## How It Differs from MultiRepoOps
 
-While [MultiRepoOps](/gh-aw/patterns/multirepoops/) runs workflows **from** your main repository that create resources **in** other repositories, SideRepoOps inverts this pattern:
+While [MultiRepoOps](/gh-aw/patterns/multi-repo-ops/) runs workflows **from** your main repository that create resources **in** other repositories, SideRepoOps inverts this pattern:
 
 | Pattern | Workflow Location | Target Repository | Use Case |
 |---------|------------------|-------------------|----------|
@@ -48,7 +48,7 @@ In SideRepoOps, workflows run in GitHub Actions **on the side repository** but p
 
 > [!TIP]
 > Testing with TrialOps
-> Before deploying SideRepoOps workflows to production, use [TrialOps](/gh-aw/patterns/trialops/) to test them in isolated trial repositories. This lets you validate behavior and iterate on prompts without creating real issues in your repositories.
+> Before deploying SideRepoOps workflows to production, use [TrialOps](/gh-aw/patterns/trial-ops/) to test them in isolated trial repositories. This lets you validate behavior and iterate on prompts without creating real issues in your repositories.
 
 ## Setup Requirements
 
@@ -394,9 +394,9 @@ This creates a feedback loop where the side repository tracks automation effecti
 
 ## Related Patterns
 
-- **[MultiRepoOps](/gh-aw/patterns/multirepoops/)** - Coordinate work across multiple repositories from main repo
+- **[MultiRepoOps](/gh-aw/patterns/multi-repo-ops/)** - Coordinate work across multiple repositories from main repo
 - **[Orchestration](/gh-aw/patterns/orchestration/)** - Orchestrate multi-issue initiatives
-- **[IssueOps](/gh-aw/patterns/issueops/)** - Issue-driven automation patterns
+- **[IssueOps](/gh-aw/patterns/issue-ops/)** - Issue-driven automation patterns
 
 ## Related Documentation
 

docs/src/content/docs/patterns/specops.md → docs/src/content/docs/patterns/spec-ops.md

@@ -164,7 +164,7 @@ The [MCP Gateway Specification](/gh-aw/reference/mcp-gateway/) demonstrates Spec
 
 ## Related Patterns
 
-- **[MultiRepoOps](/gh-aw/patterns/multirepoops/)** - Cross-repository coordination
+- **[MultiRepoOps](/gh-aw/patterns/multi-repo-ops/)** - Cross-repository coordination
 
 ## References