Automated Dev Pipeline: How the Skill Works Diagram

Scripts decide, prompts judge

Yes/no checks are scripts with exit codes; the model writes, reviews, picks
A pre-check logs SKIPPED and exits 0 with no session when there is no work
Only PRs reach default branches, all through the one sweep
A status report gathers every repo's facts by script; the model only summarizes

Irreversible means human

Only a closed-as-Completed issue lets the script flip visibility
Merges to paths that deploy a public site are held for the owner
The security sweep reports leaked keys; only the owner rotates them

Feedback loop in the runner

Run history JSONL: a start with no end is a silent death
TRAP: and LESSON: lines are saved and prepended to later prompts
Prompt edits arrive as a PR the owner merges
A weekly improver proposes one fleet change; the owner's merge registers it

Single-repo variant

Stages are folders: ideas/, planning/, in-progress/, live/
No incubate or graduate; a held merge that deploys the site is the publish