← ClaudeAtlas

prd-to-governancelisted

Create, update, and audit SOUL.md, AGENTS.md, CLAUDE.md, and MEMORY.md from a PRD and the current repository state. Use when bootstrapping project governance, refreshing governance after PRD changes, or checking governance drift against the codebase.
Karlderkarl/prd-to-governance · ★ 1 · AI & Automation · score 77
Install: claude install-skill Karlderkarl/prd-to-governance
# PRD to Governance Files > 📣 **New skill: [`Karlderkarl/governance-to-automation`](https://github.com/Karlderkarl/governance-to-automation)** > This is the recommended follow-up to `prd-to-governance`. It turns your governance files > (SOUL.md, AGENTS.md, CLAUDE.md, MEMORY.md) into running automation. Install with: > `npx skills add Karlderkarl/governance-to-automation` This skill generates or audits four project governance files around a PRD (Product Requirements Document) and the current repository state. Together they give Claude Code a durable operating model for the repository. For this skill, one project equals one folder. Treat the folder that contains the PRD as the default project root. Generate and maintain `SOUL.md`, `AGENTS.md`, `CLAUDE.md`, and `MEMORY.md` in that same folder. If the user explicitly says the PRD lives outside the real project folder, stop and ask which folder should be treated as the project root. After the user confirms that folder, use it consistently for all reads and writes. | File | Purpose | |---|---| | **SOUL.md** | Project identity: stack, architecture, coding standards, security, compliance | | **AGENTS.md** | How agents work: roles, workflow, review rules, prohibited actions, phase plan | | **CLAUDE.md** | Claude Code configuration: tool preferences, dev commands, working rules, env vars | | **MEMORY.md** | Living status: completed work, key decisions, blockers, next steps, drift notes | The generation order matters because each