Skill

claude-augur

Use after writing or editing a plan file, after exiting plan mode, or when asked "why did you choose this?" — surfaces decisions, risks, and blind spots before implementation.

From claude-augur

Install

Run in your terminal

npx claudepluginhub vvkmnn/claude-emporium-beta --plugin claude-augur

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

ui-ux-pro-max

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

57.6k

context7-mcp

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

51.8k

market-sizing-analysis

2 files

Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.

startup-business-analyst

32.9k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

Tool

Purpose

augur_explain

Extract plan structure and return a template for inline rendering

Template Format

MCP pre-renders the header band (title + progress bar) and purpose. You fill 6 sections:

Decisions — ✓ chose X → reason / ~ uncertain / ? risky guess

Risks — ⚠ If X → Y plain English sentences

Discoveries — ★ things found during exploration not in the plan

Questions — ◆ questions the user needs to answer

Trade-offs — 3-column: + gain │ − lose │ · skip

Recommendations — → investigate, weak spots, quick wins, plan gaps

Mistake

Fix

Rendering in a code block

Include the template directly in your response text

Restating the plan

Surface what ISN'T in the plan

Silent rendering

Discuss recommendations and questions with the user after

Verbose text

One short line per item, minimal words

Claude Augur

Surface plan reasoning as scannable inline abstracts. Decisions, risks, discoveries, recommendations — visible at a glance.

When to Use

After writing or editing a plan file
When the user asks to explain or summarize a plan
When the user asks "why did you choose this approach?"
After plan mode exits with a new or updated plan

Quick Reference

Tool	Purpose
`augur_explain`	Extract plan structure and return a template for inline rendering

Workflow

Write or edit a plan file
augur_explain(plan_path: "/path/to/plan.md")
MCP returns a one-line summary + template with [FILL] markers
Render the filled template inline in your response (not in a code block)
Discuss your recommendations and questions with the user

Template Format

MCP pre-renders the header band (title + progress bar) and purpose. You fill 6 sections:

Decisions — ✓ chose X → reason / ~ uncertain / ? risky guess
Risks — ⚠ If X → Y plain English sentences
Discoveries — ★ things found during exploration not in the plan
Questions — ◆ questions the user needs to answer
Trade-offs — 3-column: + gain │ − lose │ · skip
Recommendations — → investigate, weak spots, quick wins, plan gaps

Rules

80 chars wide, ~25 lines total
Minimal words — plain English a child could read
Be ADVERSARIAL — surface doubts, not confidence
After rendering: discuss recommendations and questions as a conversation
Render inline, never in a code block

Common Mistakes

Mistake	Fix
Rendering in a code block	Include the template directly in your response text
Restating the plan	Surface what ISN'T in the plan
Silent rendering	Discuss recommendations and questions with the user after
Verbose text	One short line per item, minimal words