
report-keeping
by andreyvit
CLI tool that helps AI agents reliably manage task-based report files with automatic sequential numbering and consistent directory organization
SKILL.md
name: report-keeping description: Track task steps and write reports to preserve context across agent sessions and avoid forgetting user intentions. allowed-tools: Bash, Read, Write
Bureau helps you succeed by providing longer-term memory for (1) user requests and (2) plans, research and big-picture path taken.
LLMs suffer from drift (when mundanity overshadows the big things) and compaction (when details are simply lost). This is one of the leading causes of LLM coding failures requiring human interventions and killing productivity. We don't want that, do we?
Bureau assists in keeping a per-task directory with numbered report files. You create and read these files, Bureau only takes care of paths.
Run as scripts/bureau (relative to skill root) or just bureau (if installed globally).
THREE IMPORTANT CHANGES
-
Split your work into very clearly separated steps. Research, planning, reviewing plans, writing tests, writing implementation, reviewing code, updating docs, updating knowledge -- these should all be separate steps.
-
Before each step, re-read context from Bureau reports.
-
After each step, write a Bureau report file.
Before each step
-
Run bureau without args to check current task and existing reports.
-
If current task doesn't match your work, run with
-N <slug>to start a new task (or-S <name>to switch to an existing one IF user asked for that). -
If user provided input, save it -- run with
-n user-something(user-request, user-revision, user-feedback, etc.) and write their input VERBATIM, then append your interpretation. -
Re-read recent reports to restore context.
-
Planning and review steps: read AS MANY reports as possible.
-
Execution steps: read all user requests + recent plans + all execution reports after the most recent plan.
After each step
-
Run with
-n <suffix>to get next report filename (e.g., plan, impl, fix, research). -
Write a report including:
- What you did and why
- Decisions made and alternatives considered
- Problems encountered and solutions
- Open questions or blockers
- Facts future agents should know
Score
Total Score
Based on repository quality metrics
SKILL.mdファイルが含まれている
ライセンスが設定されている
100文字以上の説明がある
GitHub Stars 100以上
3ヶ月以内に更新がある
10回以上フォークされている
オープンIssueが50未満
プログラミング言語が設定されている
1つ以上のタグが設定されている
Reviews
Reviews coming soon