Skip to content

docs: add agentic workflows bootstrap prompt and update upstream references - #1

Draft
bradygaster wants to merge 1 commit into
devfrom
squad/agents-agentic-workflows
Draft

bradygaster wants to merge 1 commit into
devfrom
squad/agents-agentic-workflows

Conversation

@bradygaster

Copy link
Copy Markdown
Owner

What

Add agents-agentic-workflows.md with the reusable repository-agent bootstrap prompt. Update canonical upstream references in docs/src/content/docs/guide/gh-aw.md to github/squad.

Why

Provide one file that users can point a fresh repo agent at. Per Brady, this PR targets his fork dev branch for handoff upstream. No linked issue was supplied.

How

Working as docs-devrel (Documentation & DevRel Engineer). Preserve the shortened prompt, pinned installation and validation gates, explicit staging before the staged verifier, and human-reviewed PR flow. Exactly two Markdown files changed; no workflow implementation or unrelated fixes.


⚠️ Quick Check

Changeset N/A: no SDK/CLI source changes.

PR Readiness Checklist

Branch & Commit

  • Branch created from latest fetched origin/dev
  • Verified only intended changes and no deletions
  • PR is not in draft mode (draft for handoff)
  • Clean commit history (one commit)

Build & Test

  • SKIP_BUILD_BUMP=1 npm run build passes
  • Markdown lint and git diff --check pass
  • Full tests, separate type-check, and ESLint not run (documentation-only change)

Changeset

N/A: documentation only.

Docs

  • Bootstrap prompt added
  • Agentic workflows guide updated

Exports

N/A: no SDK changes.


Breaking Changes

None.

Waivers

Request waiver of full product tests, standalone type-check, and ESLint for two Markdown files; pending Lead/Quality approval before merge. No fresh-repository installation was performed; the prompt retains prerequisite and validation gates rather than promising instant activation.

@bradygaster

Copy link
Copy Markdown
Owner Author

cc @pelikhan for review/testing

Before editing:
- Check the default branch, working tree, authentication, and existing `.github/aw/`, `.github/workflows/`, and `.github/skills/` files.
- If an installation is already present, or files conflict and you can’t verify their ownership, stop and report the paths—don’t overwrite them.
- Verify `gh aw --version` is exactly `v0.91.5`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't lock to a version

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the exact patch-version installation requirement in the upstream replacement, github/squad#2413, targeting dev. The 1.x migration also updates actual upstream package ownership, init-action references, compiler pins and integrity manifests rather than just changing the prompt.

Tested the official 1.0.1 binary against published revision 2c4a0d9f076b7a6ae160d5ed89cb11fdc6ae7494: fresh native installation, all eight strict-compiled workflows, and installed/staged verification pass. The 971 coupled tests pass, including pre-fix-red regressions. Immutable source/action/digest checks remain for reproducibility; future compiler outputs still need reviewed regeneration. The upstream PR documents unrelated full-suite failures and remains draft; hosted activation and merge have not been performed.

Auto-replied by the GitHub Copilot app

@pelikhan

pelikhan commented Nov 7, 2026

Copy link
Copy Markdown

let's upgrade to 1.x

@pelikhan

pelikhan commented Nov 7, 2026

Copy link
Copy Markdown

Otherwise LGTM, let's test it.

@bradygaster

Copy link
Copy Markdown
Owner Author

Upstream replacement draft: github#2413 (targets github/squad:dev). The bootstrap prompt no longer installs an exact gh-aw patch version, and the guide records testing with official gh-aw 1.0.1. All eight workflows install and strictly compile, but Squad installation verification rejects upstream package ownership; the verifier also still requires v0.91.5 compiler/action pins and compiled-lock digests. Full 1.x support therefore needs a coordinated integrity migration, not only a documentation version change. The upstream PR remains draft pending that work; this fork PR is left open to preserve the review discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants