agentics-beyond-code: Skill for Codex

Claude-Native Workflow Builder

This skill turns a plain-language process problem into an always-on automation built with Claude Routines and Claude Scheduled Tasks: which one to use per step, what triggers it, where the human interpretation gate lives, and what org governance applies. It is one of five platform builders, alongside github-workflow-builder, productboard-agent-builder, atlassian-agent-builder, and google-workspace-agent-builder: same philosophy (living documents, artifacts over roles, the PM/owner decides), different execution engine. Choosing which workflows to adopt, and whether Claude is the right platform, belongs to agentic-workflow-planner.

Use this skill instead of github-workflow-builder when the user's system of record isn't GitHub, when they explicitly don't want a GitHub Actions/gh-aw dependency, or when they want to see that the pattern this repo teaches isn't tied to GitHub at all. Use github-workflow-builder when GitHub Issues/Projects/Discussions are the team's actual home. Use atlassian-agent-builder when the team wants the automation to run inside Jira or Confluence as a Rovo agent rather than as a Claude Routine, and google-workspace-agent-builder when it should run inside Google Workspace as a Workspace Studio flow or skill.

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. Read the bundled references from this skill's own folder before concluding that they are missing. For a named workflow, use the source index to fetch its recorded public source and necessary dependencies automatically with available read-only tools. A drafting request includes these reads; do not first ask to attach a repository, connect GitHub, or choose a retrieval method. Request specific files or a checkout only after the available retrieval path fails or no read tool is available, and name the missing path and observed limitation. 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.