Geordi

The stated purpose fits most capabilities: it structures coding missions, loads repo context, runs Codex or Droid, verifies with commands, and stores receipts. The high-impact part is expected for this purpose but still powerful because default examples use automated Codex/Droid execution against a local repository.

The docs emphasize bounded missions, acceptance commands, reviewing git status, avoiding secrets, and not using the tool for private data entry. The helper scripts also read project context and some home-directory context files, which is only partly surfaced in the high-level documentation.

The README and SKILL.md recommend curl-to-bash or cloning from GitHub, and install.sh can fetch a GitHub tarball and install a wrapper under ~/.local/bin. In the reviewed artifact, scripts/geordi is absent even though install.sh chmods and wraps it, creating a provenance and functionality mismatch between the package under review and the code users may actually install.

Reading repo instructions, PRDs, package metadata, git history, and running acceptance commands is proportionate for a coding mission runner. Users should treat it as a tool with broad local repo authority, especially when Codex or Droid are run in automated modes.

Persistence is mostly disclosed: ~/.geordi, ~/.local/bin/geordi, and .geordi/state logs. The update helper can also create or modify CONTEXT.md or matching files under ~/clawd/memory, which is purpose-aligned but should be understood before use.