edpasetuplisted

# EDPA Setup — V2 Project Initialization ## What this does Bootstraps a local-first EDPA project. Everything EDPA-related lives under `.edpa/`; the engine is vendored as `.edpa/engine/` so CI and non-Claude-Code tools can run scripts directly without a per-run install. Resulting layout: ``` <project>/ ├── .edpa/ │ ├── engine/ ← vendored from ${CLAUDE_PLUGIN_ROOT}/edpa/ │ │ ├── scripts/ ← Python: backlog.py, engine.py, mcp_server.py, … │ │ ├── schemas/ ← JSON Schemas │ │ └── templates/ ← yaml + workflow templates │ ├── config/ │ │ ├── edpa.yaml ← project.name + governance metadata │ │ ├── people.yaml ← team registry │ │ └── id_counters.yaml ← local-first ID allocator state │ ├── backlog/ ← per-item .md files │ │ ├── initiatives/ epics/ features/ stories/ defects/ events/ risks/ │ ├── iterations/ ← per-iteration .yaml │ ├── reports/ ← timesheet + engine results │ └── snapshots/ ← frozen audit snapshots └── .github/workflows/ └── edpa-contribution-sync.yml ← PR signal materialization (optional) ``` ## Arguments `$ARGUMENTS` — optional flags: - `--with-ci` — copy `edpa-contribution-sync.yml` to `.github/workflows/`. Optional enhancement that materialises pr_reviewer / issue_comment signals (PR-thread-only events) from GitHub Acti