Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
Discuss with the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'discuss' trigger phrases.
Save task-relevant conversation and workspace context to a temporary Markdown file in docs/handoffs, then provide the exact prompt another agent should use to resume. Use when handing unfinished work to a new agent or session.
Implement a task plan from start to finish, including branching, incremental commits, tests, documentation lookup, review, and local integration. Use when the user asks to execute an existing task breakdown or work plan.
Turn a conversation or specification into linked task documents with bounded subtasks and progress checklists. Use when the user asks to plan work, break a spec into tasks, or create an implementation backlog.
Create and maintain the project's llmwiki using the Open Knowledge Format. Use when the user asks to create, update, consult, or organize a project wiki or durable project knowledge.
AGENTS.md instructions for beeltec/context-usage-mcp, covering agent guidelines, project wiki, when to consult it, when to update it and how to update it.
Claude Code instructions for beeltec/context-usage-mcp, a project described as: MCP server exposing a getcontextusage tool that reports the current session's raw token usage from its on-disk transcript/rollout. Works under Claude Code and Codex CLI.
MCP server exposing getcontextusage, reporting the current session's raw token usage from its transcript/rollout. Supports Claude Code and OpenAI Codex CLI. Runs locally from the @beeltec/context-usage-mcp npm package.