update docs and workflow

dsyme · dsyme · commit d3ff5177d6a4 · 2026-02-09T22:27:55.000Z
diff --git a/docs/ci-doctor.md b/docs/ci-doctor.md
@@ -11,17 +11,11 @@ The [CI Doctor workflow](../workflows/ci-doctor.md?plain=1) monitors your GitHub
 gh extension install github/gh-aw
 
 # Add the CI Doctor workflow to your repository
-gh aw add githubnext/agentics/ci-doctor
+gh aw add-wizard githubnext/agentics/ci-doctor
 ```
 
 This walks you through adding the workflow to your repository.
 
-After adding, the workflow will automatically trigger when monitored CI workflows fail. You cannot start this workflow manually as it responds to workflow failure events.
-
-**Mandatory Checklist**
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
 You can specify which workflows to monitor (currently monitors "Daily Perf Improver" and "Daily Test Improver") by editing the workflow directly.
diff --git a/docs/daily-accessibility-review.md b/docs/daily-accessibility-review.md
@@ -11,18 +11,14 @@ The [daily accessibility review workflow](../workflows/daily-accessibility-revie
 gh extension install github/gh-aw
 
 # Add the Daily Accessibility Review workflow to your repository
-gh aw add githubnext/agentics/daily-accessibility-review
+gh aw add-wizard githubnext/agentics/daily-accessibility-review
 ```
 
 This walks you through adding the workflow to your repository.
 
-**Mandatory Checklist**
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration 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`.
+This workflow requires no configuration and works out of the box.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-dependency-updates.md b/docs/daily-dependency-updates.md
@@ -11,7 +11,7 @@ The [daily dependency updater workflow](../workflows/daily-dependency-updates.md
 gh extension install github/gh-aw
 
 # Add the Daily Dependency Updater workflow to your repository
-gh aw add githubnext/agentics/daily-dependency-updates
+gh aw add-wizard githubnext/agentics/daily-dependency-updates
 ```
 
 This walks you through adding the workflow to your repository. After merging the PR and syncing to main, you can start a run of this workflow immediately by running:
@@ -20,31 +20,9 @@ This walks you through adding the workflow to your repository. After merging the
 gh aw run daily-dependency-updates
 ```
 
-❗IMPORTANT: GitHub Actions runs will **not** trigger on commits pushed by this workflow and will **not** tell you that CI has not been run unless you have enabled a specific custom check for this condition. **You must open/close the PR or hit "Update branch" if offered to trigger CI.Yes it's painful and yes it's just something you need to be aware of.
-
-**Mandatory Checklist**
-
-* [ ] I have read the notes on coding tasks in the [main README](../README.md) and understand the implications.
-
-* [ ] I am a repository admin or have sufficient permissions, and am happy for the safe-outputs portion of this workflow to push new branches to the repository.
-
-* [ ] I have enabled "Allow GitHub Actions to create and approve pull requests" in the repository settings under "Actions > General"
-
-* [ ] I have considered enabling "Always suggest updating pull request branches" in the repository settings
-
-* [ ] If in a fork, I have enabled "GitHub Actions" and "GitHub Issues" in the fork repository settings
-
-* [ ] I will review all pull requests very carefully, and carefully monitor the repository. 
-
-* [ ] I will operate this demonstrator for a time-limited period only (the default is 48h). 
-
-* [ ] I understand that GitHub Actions runs will **not** trigger on pull requests created by this workflow, see above.
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration to specify dependency management tools (npm, pip, maven, etc.), customize dependency update strategies and version constraints, configure which dependencies to include/exclude from automated updates. Local configuration can be done in `.github/workflows/agentics/daily-dependency-updates.config.md`.
-
-
+This workflow requires no configuration and works out of the box.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-perf-improver.md b/docs/daily-perf-improver.md
@@ -11,7 +11,7 @@ The [daily performance improver workflow](../workflows/daily-perf-improver.md?pl
 gh extension install github/gh-aw
 
 # Add the Daily Performance Improver workflow to your repository
-gh aw add githubnext/agentics/daily-perf-improver
+gh aw add-wizard githubnext/agentics/daily-perf-improver
 ```
 
 This walks you through adding the workflow to your repository and running the workflow for the first time.
@@ -28,20 +28,12 @@ To run repeatedly (at most one instance running at a time and sending a trigger
 gh aw run daily-perf-improver --repeat 180
 ```
 
-**Mandatory Checklist**
-
-* [ ] I understand that, by default, the agentic portion of this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
-
-* [ ] I will review all pull requests very carefully, and carefully monitor the repository. 
-
 ## Configuration
 
 1. The first run of the workflow will produce a pull request with inferred action pre-steps that need approval
 
 2. The first run of the workflow will also create an issue in the repository with a plan for improving performance. You can comment on this issue to provide feedback or adjustments to the plan. Comments will not be picked up until the next run.
 
-3. Use local configuration to specify performance testing tools and benchmarking frameworks, optimization targets, performance metrics, and profiling strategies. Local configuration can be done in `.github/workflows/agentics/daily-perf-improver.config.md`.
-
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
diff --git a/docs/daily-plan.md b/docs/daily-plan.md
@@ -11,18 +11,14 @@ The [daily plan workflow](../workflows/daily-plan.md?plain=1) will run daily to
 gh extension install github/gh-aw
 
 # Add the Daily Plan workflow to your repository
-gh aw add githubnext/agentics/daily-plan
+gh aw add-wizard githubnext/agentics/daily-plan
 ```
 
 This walks you through adding the workflow to your repository and running the workflow for the first time.
 
-**Mandatory Checklist**
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration to specify planning focus areas, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
+This workflow requires no configuration and works out of the box. 
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-progress.md b/docs/daily-progress.md
@@ -11,7 +11,7 @@ The [daily progress workflow](../workflows/daily-progress.md?plain=1) is an auto
 gh extension install github/gh-aw
 
 # Add the Daily Progress workflow to your repository
-gh aw add githubnext/agentics/daily-progress
+gh aw add-wizard githubnext/agentics/daily-progress
 ```
 
 This walks you through adding the workflow to your repository.
@@ -22,19 +22,9 @@ You can start a run of this workflow immediately by running:
 gh aw run daily-progress
 ```
 
-**Mandatory Checklist**
-
-* [ ] I understand that this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
-
-* [ ] I will review all pull requests and issues created by this workflow very carefully, and carefully monitor the repository.
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. **Local configuration**: Customize development focus areas, coding standards, and workflow behavior. Local configuration can be done in `.github/workflows/agentics/daily-progress.config.md`.
-
-2. **Build steps**: The workflow will automatically create a build configuration file at `.github/actions/daily-progress/build-steps/action.yml` to set up the development environment for feature work.
+The workflow will self-configure to create a build configuration file at `.github/actions/daily-progress/build-steps/action.yml` to set up the development environment for feature work.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-qa.md b/docs/daily-qa.md
@@ -11,7 +11,7 @@ The [daily Adhoc QA workflow](../workflows/daily-qa.md?plain=1) will perform adh
 gh extension install github/gh-aw
 
 # Add the Daily QA workflow to your repository
-gh aw add githubnext/agentics/daily-qa
+gh aw add-wizard githubnext/agentics/daily-qa
 ```
 
 This walks you through adding the workflow to your repository.
@@ -22,17 +22,9 @@ You can start a run of this workflow immediately by running:
 gh aw run daily-qa
 ```
 
-**Mandatory Checklist**
-
-* [ ] I understand that, by default, the agentic portion of this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration 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. You can edit it to specify QA tasks, testing scenarios, reporting format, and frequency.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-repo-status.md b/docs/daily-repo-status.md
@@ -11,7 +11,7 @@ The [daily repo status workflow](../workflows/daily-repo-status.md?plain=1) will
 gh extension install github/gh-aw
 
 # Add the Daily Repo Status workflow to your repository
-gh aw add githubnext/agentics/daily-repo-status
+gh aw add-wizard githubnext/agentics/daily-repo-status
 ```
 
 This walks you through adding the workflow to your repository.
diff --git a/docs/daily-test-improver.md b/docs/daily-test-improver.md
@@ -11,7 +11,7 @@ The [daily test coverage improver workflow](../workflows/daily-test-improver.md?
 gh extension install github/gh-aw
 
 # Add the Daily Test Coverage Improver workflow to your repository
-gh aw add githubnext/agentics/daily-test-improver
+gh aw add-wizard githubnext/agentics/daily-test-improver
 ```
 
 This walks you through adding the workflow to your repository.
@@ -22,20 +22,12 @@ You can start a run of this workflow immediately by running:
 gh aw run daily-test-improver
 ```
 
-**Mandatory Checklist**
-
-* [ ] I understand that, by default, the agentic portion of this workflow will generate and run bash commands in the confine of the GitHub Actions VM, with network access.
-
-* [ ] I will review all pull requests very carefully, and carefully monitor the repository. 
-
 ## Configuration
 
 1. The first run of the workflow will produce a pull request with inferred action pre-steps that need approval.
 
 2. The first run of the workflow will also create an issue in the repository with a plan for improving test coverage. You can comment on this issue to provide feedback or adjustments to the plan. Comments will not be picked up until the next run.
 
-3. Use local configuration or comment on the plan to specify test generation strategies, high-priority areas and coverage targets. Local configuration can be done in `.github/workflows/agentics/daily-test-improver.config.md`.
-
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
diff --git a/docs/issue-triage.md b/docs/issue-triage.md
@@ -11,7 +11,7 @@ The [issue triage workflow](../workflows/issue-triage.md?plain=1) will when issu
 gh extension install github/gh-aw
 
 # Add the Issue Triage workflow to your repository
-gh aw add githubnext/agentics/issue-triage
+gh aw add-wizard githubnext/agentics/issue-triage
 ```
 
 This walks you through adding the workflow to your repository.
@@ -20,15 +20,9 @@ You must also [choose a coding agent](https://github.github.com/gh-aw/reference/
 
 You can't start a run of this workflow directly as it is triggered in the context of an issue.
 
-**Mandatory Checklist**
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration 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
+This workflow requires no configuration and works out of the box. You can edit it to customize triage criteria, labeling logic, customize issue categorization, modify automated responses.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/pr-fix.md b/docs/pr-fix.md
@@ -2,17 +2,17 @@
 
 > For an overview of all available workflows, see the [main README](../README.md).
 
-The ["@pr-fix" workflow](../workflows/pr-fix.md?plain=1) is an alias workflow "@pr-fix" that will help you fix and complete pull requests. By default it will analyze failing CI checks in pull requests, identify root causes, and implement fixes to resolve issues and get PRs back to a passing state. 
+The ["pr-fix" workflow](../workflows/pr-fix.md?plain=1) is an alias workflow "/pr-fix" that will help you fix and complete pull requests. By default it will analyze failing CI checks in pull requests, identify root causes, and implement fixes to resolve issues and get PRs back to a passing state. 
 
 You can trigger the workflow in default mode by adding a comment to a pull request with the command:
 
-```
+```text
 /pr-fix
 ```
 
 or by writing a comment:
 
-```
+```text
 /pr-fix Please add more tests.
 ```
 
@@ -23,7 +23,7 @@ or by writing a comment:
 gh extension install github/gh-aw
 
 # Add the PR Fix workflow to your repository
-gh aw add githubnext/agentics/pr-fix
+gh aw add-wizard githubnext/agentics/pr-fix
 ```
 
 This walks you through adding the workflow to your repository.
@@ -36,15 +36,9 @@ To trigger the workflow on a specific pull request, add a comment with the comma
 /pr-fix
 ```
 
-**Mandatory Checklist**
-
-* [ ] I have read the notes on coding tasks in the [main README](../README.md) and understand the implications.
-
-* [ ] I will review all pull requests very carefully, and carefully monitor the repository. 
-
 ## Configuration
 
-This workflow requires no configuration and works out of the box. You can use local configuration to specify custom build commands, testing procedures, linting rules, and code formatting standards. Local configuration can be done in `.github/workflows/agentics/pr-fix.config.md`.
+This workflow requires no configuration and works out of the box. You can edit it to specify custom build commands, testing procedures, linting rules, and code formatting standards, or customize these for all agents in AGENTS.md in your repository.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/q.md b/docs/q.md
@@ -23,7 +23,7 @@ or by writing a comment with a specific request:
 gh extension install github/gh-aw
 
 # Add the Q workflow to your repository
-gh aw add githubnext/agentics/q
+gh aw add-wizard githubnext/agentics/q
 ```
 
 This walks you through adding the workflow to your repository.
@@ -36,10 +36,6 @@ To trigger the workflow on a specific issue or pull request, add a comment with
 /q [your optimization request here]
 ```
 
-**Mandatory Checklist**
-
-* [ ] I understand that this workflow will analyze workflows and create pull requests with optimizations.
-
 ## Configuration
 
 This workflow requires no configuration and works out of the box. You can customize optimization behavior and analysis scope if needed by editing the workflow file.
diff --git a/docs/repo-ask.md b/docs/repo-ask.md
@@ -6,13 +6,13 @@ The [repo-ask workflow](../workflows/repo-ask.md?plain=1) is a command-triggered
 
 You can trigger the workflow by adding a comment to any issue or pull request with the command:
 
-```
+```text
 /repo-ask
 ```
 
 or by writing a comment with a specific question:
 
-```
+```text
 /repo-ask How does the authentication system work in this project?
 ```
 
@@ -23,7 +23,7 @@ or by writing a comment with a specific question:
 gh extension install github/gh-aw
 
 # Add the Repo Ask workflow to your repository
-gh aw add githubnext/agentics/repo-ask
+gh aw add-wizard githubnext/agentics/repo-ask
 ```
 
 This walks you through adding the workflow to your repository.
diff --git a/docs/update-docs.md b/docs/update-docs.md
@@ -11,7 +11,7 @@ The [update documentation workflow](../workflows/update-docs.md?plain=1) will ru
 gh extension install github/gh-aw
 
 # Add the Update Docs workflow to your repository
-gh aw add githubnext/agentics/update-docs
+gh aw add-wizard githubnext/agentics/update-docs
 ```
 
 This walks you through adding the workflow to your repository.
@@ -22,10 +22,6 @@ You can start a run of this workflow immediately by running:
 gh aw run update-docs
 ```
 
-**Mandatory Checklist**
-
-* [ ] I will review all pull requests very carefully, and carefully monitor the repository. 
-
 ## Configuration
 
 This workflow requires no configuration and works out of the box. You can configure documentation frameworks, documentation structure, themes, files, directories by editing the workflow file.
diff --git a/docs/weekly-research.md b/docs/weekly-research.md
@@ -11,21 +11,11 @@ The [weekly research workflow](../workflows/weekly-research.md?plain=1) will run
 gh extension install github/gh-aw
 
 # Add the Weekly Research workflow to your repository
-gh aw add githubnext/agentics/weekly-research
+gh aw add-wizard githubnext/agentics/weekly-research
 ```
 
 This walks you through adding the workflow to your repository. 
 
-You can start a run of this workflow immediately by running:
-
-```bash
-gh aw run weekly-research
-```
-
-**Mandatory Checklist**
-
-* [ ] If in a fork, enable GitHub Actions and Issues in the fork settings
-
 ## Configuration
 
 This workflow requires no configuration and works out of the box. You customize output format, research topics, report length, focus areas or to adjust frequency or timing by editing the workflow file.
diff --git a/workflows/ci-doctor.md b/workflows/ci-doctor.md
