update docs

Author: dsyme

docs/ci-doctor.md

@@ -18,6 +18,8 @@ This creates a pull request to add the workflow to your repository. After mergin
 
 ## Configuration
 
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
 1. Use local configuation to specify which workflows to monitor (currently monitors "Daily Perf Improver" and "Daily Test Improver"), investigation depth, failure categorization, and reporting format. Local configuration can be done in `.github/workflows/agentics/ci-doctor.config.md`.
 
 2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 

docs/daily-accessibility-review.md

@@ -22,6 +22,8 @@ gh aw run daily-accessibility-review
 
 ## Configuration
 
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
 1. Use local configuation to specify which accessibility standards to check (e.g., WCAG 2.1, WCAG 2.2), types of accessibility issues to prioritize, and reporting format. Local configuration can be done in `.github/workflows/agentics/daily-accessibility-review.config.md`.
 
 2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 

docs/daily-dependency-updates.md

@@ -32,6 +32,8 @@ gh aw run daily-dependency-updates
 
 ## Configuration
 
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
 1. Use local configuation to specify dependency management tools (npm, pip, maven, etc.), customize dependency update strategies and version constraints, onfigure which dependencies to include/exclude from automated updates. Local configuration can be done in `.github/workflows/agentics/daily-dependency-updates.config.md`.
 
 2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.

docs/daily-plan.md

@@ -22,6 +22,8 @@ gh aw run daily-plan
 
 ## Configuration
 
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
 1. Use local configuation to specify planning focus areas, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.

docs/daily-qa.md

@@ -22,9 +22,11 @@ gh aw run daily-qa
 
 ## Configuration
 
-3. Use local configuation to specify QA tasks, testing scenarios, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-qa.config.md`.
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
 
-4. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
+1. Use local configuation to specify QA tasks, testing scenarios, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-qa.config.md`.
+
+2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 

docs/daily-team-status.md

@@ -22,9 +22,11 @@ gh aw run daily-team-status
 
 ## Configuration
 
-- No build steps required - works out of the box
-- Edit the workflow file to customize status report format, metrics, modify report frequency or add specific team focuses
-- After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
+1. Use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/daily-team-status.config.md`.
+
+2. Add MCPs to integrate with project management tools
 
 ## What it reads from GitHub
 

docs/issue-triage.md

@@ -18,10 +18,13 @@ This creates a pull request to add the workflow to your repository. You can't st
 
 ## Configuration
 
-- No build steps required - works out of the box
-- Edit the workflow file to customize triage criteria, labeling logic, customize issue categorization, modify automated responses
-- Add MCPs to integrate with project management tools
-- After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
+1. Use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/issue-triage.config.md`.
+
+2. Add MCPs to integrate with project management tools
+
+After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
 

docs/update-docs.md

@@ -33,12 +33,13 @@ gh aw run update-docs
 
 ## Configuration
 
-- Benefits from configuring build steps for documentation generation
-- Edit the workflow to specify your documentation framework (Astro Starlight, MkDocs, etc.)
-- Customize documentation structure, themes, and generation commands
-- Add project-specific documentation validation and deployment steps
-- Configure which files and directories to include in documentation updates
-- After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
+1. Use local configuation to configure documentation frameworks, documentation structure, themes, files, directories. Local configuration can be done in `.github/workflows/agentics/update-docs.config.md`.
+
+2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
+
+After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
 

docs/weekly-research.md

@@ -22,6 +22,8 @@ gh aw run weekly-research
 
 ## Configuration
 
+This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+
 1. Use local configuation to customize output format, research topics, report length, focus areas or to adjust frequency or timing. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.

workflows/daily-accessibility-review.md

@@ -8,8 +8,10 @@ on:
 
 timeout_minutes: 15
 
-safe-output:
-  create-issue:
+
+permissions:
+  contents: read  # Required so the agent can review the code in the repository
+  issues: write   # Required so the agent can create issues for accessibility problems
 
 tools:
   playwright:
@@ -18,8 +20,11 @@ tools:
       command: npx
       args: ["@playwright/mcp@0.0.33", "--headless"]
     allowed: ["browser_click", "browser_evaluate", "browser_handle_dialog", "browser_hover", "browser_navigate", "browser_navigate_back", "browser_navigate_forward", "browser_press_key", "browser_resize", "browser_select_option", "browser_snapshot", "browser_take_screenshot", "browser_type", "browser_wait_for"]
+  github: 
+    allowed: ["create_issue"]
   claude:
     allowed:
+      TodoWrite:
       WebFetch:
       WebSearch: