Done Blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
Install
npx skills add jeremybrasher/grokbot-skills --skill done-blockedgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/done-blocked ~/.claude/skills/done-blockedPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# DONE / BLOCKED Reporting Contract Terminal status is exactly two states, and BLOCKED requires specific evidence — not vague obstruction reports. ## The contract Every agent's final handoff line is one of: ``` DONE: <one-sentence summary of what shipped> artifact: <path to report/PR/commit> next: <who picks this up — pipeline stage, gate, or "pipeline continues"> ``` ``` BLOCKED: <one-sentence summary of the obstacle> tried: <what was attempted — file paths, commands, error signatures> failed_because: <concrete reason — not "unclear", not "complex"> need: <specific unblock — file access, missing config, CTO decision, another agent> ``` ## Hard rules 1. **No third state.** "Mostly done", "done with caveats", "almost there" → choose. If caveats exist, the caveat itself decides: - Caveat is cosmetic / P2+ → **DONE** (file a Beads bug, move on) - Caveat blocks the next pipeline stage → **BLOCKED** (do not pretend) 2. **BLOCKED requires three fields.** `tried` + `failed_because` + `need`. Missing any field → the verdict is rejected and the agent must re-report. No exceptions for "obvious" cases. 3. **Silence is not DONE.** If the agent stops producing output without a terminal line, the parent / next stage treats it as BLOCKED with `failed_because: silent — no terminal verdict written`. 4. **`failed_because` must be concrete.** These are rejected: - "environment issue" → say *which* command failed with *what* error
Details
- Skill name
done-blocked- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/done-blocked/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Done Blocked skill do?
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
How do I install the Done Blocked skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill done-blocked. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Done Blocked popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
Ecommerce SEO
38jeremybrasher/grokbot-skills
E-commerce SEO audit for online stores (WooCommerce, Shopify, Magento, custom). Covers the structural problems unique to commerce sites: category / product listing pages (PLP), product detail pages (PDP), faceted navigation and the crawl-budget / duplicate-content traps it creates, pagination, canonical handling for variants and filters, out-of-stock / discontinued product handling, internal linking and breadcrumbs, and Product / Offer / Review / AggregateRating / BreadcrumbList structured data for rich results. Use this skill whenever the user runs an online store and asks about e-commerce SE
Broken Link Checker
38jeremybrasher/grokbot-skills
Scans a website to find broken links (404s, 500s). Crawls internal pages, identifies broken outbound links, and reports source pages for easy fixing. Use this when the user asks to "check for broken links", "find 404s", "audit my links", or "is my site healthy".
Geo Optimizer
38jeremybrasher/grokbot-skills
Generative Engine Optimization (GEO) — make content rank in AI search answers from ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews. Audits existing content, rewrites for AI citation, and produces per-engine strategy. Use when asked to "optimize for AI search", "rank in ChatGPT", "GEO audit", "improve AI citations", "rank in Perplexity", "AI Overview optimization", "AI Overview ranking", "LLM SEO", "answer engine optimization", "AEO", "get cited by AI", "GEO", "generative engine optimization", "show up in ChatGPT", "appear in AI answers", "be cited by Perplexity", "SGE optimization
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.