Your work is pure rock'n'roll. Let's make sure it is visible now.
Evidence-first engineering execution and traceability.
Epi Log is a tiny Agent Skills-format core that helps an agent leave useful visibility behind while doing ordinary engineering work. It makes intent, decisions, changes, evidence, outcomes, assumptions, blockers, and follow-up easier to find in the work’s existing artifacts.
It is designed to be ambient after installation: no separate daily command, diary, database, connector, or reporting ritual is required. Some activity metrics are useful signals but can misrepresent some work when viewed alone; Epi Log adds context and evidence rather than reducing engineering to a scorecard.
- Drives toward the real outcome and the highest-leverage next step.
- Keeps
intent → decision → change → evidence → outcometraceable in tickets, PRs, docs, reviews, tests, and handoffs. - Makes meaningful research, debugging, review, design, coordination, decisions, and blocked work visible when they produce a conclusion, risk reduction, unblock, or reusable artifact.
- Checks one level above for material work: validation, maintainability, reliability, security, rollout, rollback, monitoring, and reuse.
- Repairs genuine visibility gaps at the point of work when authorized, or supplies the smallest precise draft when it cannot act.
- Verifies before handoff and states facts, assumptions, uncertainty, blockers, and follow-up.
It does not create ceremony for trivial changes, duplicate a diary, invent evidence, or optimize for PR count, lines, hours, streaks, rankings, or other shallow proxies.
The core is plain Markdown with lightweight YAML front matter. It works with any harness that discovers SKILL.md; these are common locations:
| Harness | Skill location |
|---|---|
| Pi | ~/.pi/agent/skills/epi-log/SKILL.md |
| Claude Code | ~/.claude/skills/epi-log/SKILL.md or .claude/skills/epi-log/SKILL.md |
| OpenAI Codex | ~/.codex/skills/epi-log/SKILL.md or .codex/skills/epi-log/SKILL.md |
| OpenCode | ~/.config/opencode/skills/epi-log/SKILL.md or the project skill directory |
| Other harnesses | Their configured skills/epi-log/SKILL.md, or attach the file as instructions |
Skill activation is harness-dependent. For the strongest always-on behavior, load SKILL.md from the harness’s baseline/project instructions when that mechanism exists; a skill directory alone may mean “available when relevant,” not literally active on every turn.
Copy SKILL.md into the target harness’s skill directory as epi-log/SKILL.md, then enable it using that harness’s normal mechanism. If the harness has no skill system, tell the agent:
Read /path/to/epi-log/SKILL.md and follow it as an ambient engineering quality and traceability layer.
There is no runtime, SDK, vendor API, database, or mandatory connector list.
The core is the normal operating loop. For an explicit retrospective or visibility report, read references/audit-mode.md and ask for a daily or trailing-seven-day audit. This mode retains the detailed PR, review, ticket, decision, evidence-gap, and report guidance without making it part of every task.
- Use only authorized sources and existing team conventions.
- Read and write within the user’s permissions; do not merge, approve, comment, message, publish, or edit external artifacts without authorization.
- Separate observed facts, inferences, and
unknown; missing access is never evidence of “no work.” - Never claim completion, value, or human review without support.
- Never pad diffs, fragment work artificially, spam comments, fake or rubber-stamp reviews, or manufacture activity.
- Keep visibility focused on outcomes, context, and collaboration—not rankings or behavioral judgments about coworkers.
epi-log/
├── SKILL.md # tiny ambient core
├── references/audit-mode.md # optional explicit retrospective/report mode
├── assets/ # README banner
├── README.md
└── LICENSE