← ClaudeAtlas

aih-envlisted

Capture or update how the test environment, credentials, env access, and deploy work — persists to .aihaus/memory/workflows/environment.md, which every session and agent loads automatically. Run it once at setup, and again whenever new environment definitions surface during the project.
overdrive-dev/aihaus-flow · ★ 4 · AI & Automation · score 80
Install: claude install-skill overdrive-dev/aihaus-flow
## Task Interrogate and persist the project's **operational environment** so it is defined **once** and then loaded by every session, every agent, and after every `/compact` — never re-asked. The durable home is `.aihaus/memory/workflows/environment.md`, which `templates/claude/CLAUDE.md` `@`-imports on every session start (and which `context-inject.sh` carries to agents). This skill fills and **updates** that file (merge, never clobber) as definitions emerge during the life of the project. **Never store secret values** — only their *location* (Secrets Manager path, vault entry, env-var name, password-manager item). Writing a plaintext credential, token, or key is a hard error; capture where it lives, not what it is. $ARGUMENTS ## Phase 1 — Load what already exists - Read `.aihaus/memory/workflows/environment.md` — the durable env doc, marker block `AIHAUS:WORKFLOW-ENVIRONMENT-PROMPTS-START/END`. Note which fields are already filled; do **not** re-ask those unless the user wants to change them. - Read `.aihaus/.profile` (role profile) and `.aihaus/project.md` for stack + role context. Read `.aihaus/memory/local/environment-online.md` if present (the devops-scoped online environment). - `--show` → print the current resolved environment (durable, plus online only if the profile holds `devops`) and stop without asking anything. ## Phase 2 — Interrogate the gaps (one batch) Ask **only the unfilled or stale** dimensions, in a single message — restate anything alre