ultra-implement

Files (2)

• SKILL.md
• workflow.js

SKILL.md (first lines)

`$ARGUMENTS` holds the parent issue. If it is empty, ask for it and stop.

Call the Workflow tool with `scriptPath` set to the absolute path of `workflow.js` in this skill's directory, and `args` set to `{ "parent": "<the parent issue>" }`. The tool loads a `scriptPath` only from a directory that the session can read, such as one with a `Read` allow rule for the skills directory. When it refuses the path, read `workflow.js` and pass its full contents as `script` instead. Typing this skill's command is the user's opt-in to the workflow.

The workflow needs a GitHub remote and the gh CLI. To explain how it works, or to debug a run, read `references/how-it-works.md`.

To resume a stopped or failed run in the same session, call the Workflow tool with the same `scriptPath`, or the one that the first call returned when it passed `script`, the same `args`, and `resumeFromRunId` set to its run id. Agents before the first one that failed or whose prompt changed return their saved results, and that one and every agent after it run again. Before a resume, remove that run's worktrees and local branches that have no changes, since old worktree paths block the new ones.

For an unattended run, start the session in auto permission mode, then send it to the background.

When the workflow returns, read `references/report.md` and report as it says.

From seanogdev/skills, MIT.

More from seanogdev/skills