Track task steps and write reports to preserve context across agent sessions and avoid forgetting user intentions.
Tracks task steps and writes reports to preserve context across agent sessions.
/plugin marketplace add andreyvit/rockstar/plugin install andreyvit-rockstar@andreyvit/rockstarThis skill is limited to using the following tools:
scripts/bureauscripts/bureau-selftest.shBureau 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).
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.
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.
Run with -n <suffix> to get next report filename (e.g., plan, impl, fix, research).
Write a report including:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.