Loading…
Use when choosing between named alternatives (libraries, tools, algorithms, schemas, approaches), when making an architectural decision that has lasting consequences, when the user asks "should we use X or Y", "which approach is better", or "why did we choose X", or when you pick one option over another for non-obvious reasons. Trigger whenever a choice is made that future work would need to understand. For progress logging of completed work (what was built, TODOs), use a project journal instead. This skill = decision rationale storage for lasting architectural choices.
decision-log is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. ## Hard Rules - **Only log decisions future work would need to understand.** Trivially reversible preferences (formatting, naming taste, one-off config values). As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding decision-log to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install SpencerGoss/agent-engineeringReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
## Hard Rules - **Only log decisions future work would need to understand.** Trivially reversible preferences (formatting, naming taste, one-off config values) do not get logged. A