agentics-beyond-code: Skill for Codex

GitHub Workflow Builder

This skill implements an Agentics Beyond Code design on GitHub: selected GitHub Agentic Workflows, supporting documents, folder structure, policies, issue templates, labels, project boards, and adoption steps. It is the GitHub builder alongside claude-native-workflow-builder and productboard-agent-builder.

Installed plugin context

When installed as a plugin, resolve bundled repository paths from the package root (three directories above this SKILL.md), not the user's working folder. Resolve references/, prompts/, and assets/ relative to this skill folder. The package is reference material; create deliverables in the user's selected workspace and assess the user's artifacts, never the bundled demo data. For an explicitly supplied source checkout, read that checkout's current files. A checkout is the current working directory when it is this repository, or a path the user gives. Never search the file system for one (no find /, mdfind, or home-directory scans): that is slow and triggers operating-system privacy prompts. Use the pinned source index instead. The directory plugin does not bundle runtime workflows, helper scripts, or demo data. Before using a repository path outside this skill, read docs/source-access.md at the package root. It explains how to locate and fetch specific files from the recorded public source revision. If source access is unavailable, request a checkout or the relevant files; do not invent a workflow or say it was read. Blank templates and assessment references work offline. Installing these skills does not connect services, install gh/gh aw, or activate workflows or scheduled tasks. Check available tools before using them.

Core workflow

1. Start from a design. If the user or agentic-workflow-planner already produced one, use it. If not, and the user can't name the workflows they want, run the planner's Design mode (../agentic-workflow-planner/references/design.md) first, keeping it short. Confirm that GitHub really is the team's home; if it isn't, suggest claude-native-workflow-builder or productboard-agent-builder.
2. Confirm the GitHub-specific choices:
   • target repo and whether it already has content
   • whether they want GitHub Projects, labels, and issue templates set up
   • tolerance for automation creating issues, comments, or PRs
   • which AI provider the org already uses. Set every copied workflow's engine: to match. If the org has GitHub Copilot, suggest the Copilot engine: it needs no separate API key. Keep Codex only if they use OpenAI. Check current gh-aw engine docs rather than assuming names.
3. Read prompts/scaffold-github-setup.md for the scaffolding procedure.
4. Inspect this repo for reusable source material before creating anything:
   • .github/workflows/*.md
   • .github/policies/*.md
   • .github/ISSUE_TEMPLATE/*.yml
   • docs/how-it-works.md
5. Create or update a concrete setup in the target repo:
   • blank docs/strategy.md and docs/how-we-work.md
   • folders for decisions/, transcripts/, .github/policies/, .github/workflows/, and .github/ISSUE_TEMPLATE/
   • optional project board plan, label taxonomy, and generic issue templates
   • copied or adapted workflow .md files from Agentics Beyond Code
   • copied or adapted policy and issue-template files when the workflow needs them
6. For gh-aw authoring details (frontmatter, triggers, safe outputs, debugging), use the agentic-workflows skill when it is available: it is present in a checkout of this repo and in repos set up with gh aw init. Otherwise, fetch the instructions it routes to directly from github/gh-aw, starting with .github/aw/create-agentic-workflow.md. The Claude plugin does not include agentic-workflows.
7. Validate the setup with gh aw compile --strict when gh-aw is available.