governance-to-automationlisted

# Governance to Automation This skill **generates the automation** that runs a project end to end. It is the execution counterpart to `prd-to-governance`: - `prd-to-governance` is a **separate skill** — [github.com/Karlderkarl/prd-to-governance](https://github.com/Karlderkarl/prd-to-governance) — that produces the four governance files (`SOUL.md`, `AGENTS.md`, `CLAUDE.md`, `MEMORY.md`) and defines **how and where memory is managed** (what goes into `MEMORY.md` vs `memory/completed-phases.md`, the status-line discipline, drift handling). **For the structure and update rules of `MEMORY.md` and the other governance files, see that skill.** - `governance-to-automation` (this skill) reads that governance and **emits the runnable pipeline** — primarily an `auto-develop.sh` script that processes tasks autonomously: implement → check → review → fix → refactor → re-review → commit → PR. The script *embodies* the memory rules the governance prescribes. The skill does **not** itself implement features. It writes the machinery that does, configured to one specific project's contract. For this skill, one project equals one folder. The project root is the folder that contains the governance files. Read and write only inside it unless the user says otherwise. ## What this skill produces | Artifact | Purpose | |---|---| | `auto-develop.sh` | The pipeline. Selects eligible tasks, runs implement/check/review/fix loop, then a senior-quality refactor pass re-validated by the reviewers, com