claude

trowel

Lean spec-to-code build workflow: code-driven preflight and planning, builders that reuse what the project already has, each slice spec-checked as it lands, the project's real end-to-end check run in code, and at most two batched fix rounds. A separate plugin; forge and foundry are unchanged.

3 on GitHubby AlphaBravov0.2.2MITupdated 3 days agodevelopment
/

Plugin trowel from marketplace guild in alphabravo-oss/guild. Commands read from the repo's manifest — 3 days ago.

What it installs

Slash commands (2)

  • /trowel:build

    Build a spec with trowel: one builder, a code check and a spec-to-code check, capped fix rounds

  • /trowel:help

    Explain how trowel builds a spec and what its flags do

Subagents (3)

  • builder

    trowel builder. Implements a spec, or one slice of it, test-first from the spec text verbatim. Runs the integration check itself and reads its result before it reports. Commits through trowel's commit command.

  • fixer

    trowel fixer. Gets every code-check failure and every spec gap against a build (or one slice of it) in one batch and fixes them all in one pass. Each behavioural fix comes with a test that fails on the code before the fix and passes after it, which trowel re-runs in code.

  • spec-checker

    trowel spec-to-code checker. Old foundry's PROVE method, verbatim: read the spec before the code, form expectations and observable truths from the spec alone, then read the code and give every requirement a verdict with file:line evidence. Assumes the code is broken. Reports every gap in one pass, f

View source on GitHub

More from alphabravo-oss/guild

All 14 plugins →

foundry

claude

Autonomous build-verify-fix loop. Decomposes a spec into castings with pre-authored teammate prompts, validates them through an 11-dimension F0.9 gate (including F0.7 intent-carrier coverage), builds in parallel waves with server-side evidence re-execution and per-requirement-ID binding, runs up to 8 verification streams (TRACE, FLOW_TRACE, PROVE, RESEARCH_AUDIT, COVERAGE_DIFF, SIGHT, TEST/PROBE, TEST_OBSERVATIONS), grinds defects to zero, then assays the result with fresh-eyes verification. Brownfield runs consume a flow delta; greenfield and cosmetic runs use the end-state pipeline. Forge plans. Foundry builds.

4 skills · 7 commands · 15 agents · 1 MCP server · hooks

3

webster

claude

Production documentation for an app you built, in a fixed layout modelled on Harvester: subject-first directories and a Docusaurus site whose navigation is the filesystem. Every page declares both what it is and who it is for, with sections from The Good Docs Project and quality checks from the ISO/IEC/IEEE 26514 characteristics: type mixing, alt text, heading order, and reading grade measured against that page's own reader. Extracts the reference material, anchors every claim to a file and line, measures drift against a recorded manifest, and refuses to state what it could not check.

11 skills · 4 commands · 6 agents

3

adhoc

claude

Stops Claude from racing on ad-hoc work. Methodical-mode pre-response checklist injected every turn (Restate, Verified/Unverified assumptions, Read Floor, Approach Deliberation, Blast Radius, Stall Check, Competing Hypotheses, Goal-Driven Execution). Stop hook enforces four gates: file:line citation verifier, uncertainty-tell scanner, zero-tool-call grounding audit, and an iterative two-tier critic-dialog (Haiku fast-critic rounds 1-2, opus pre-stop-critic rounds 3-5, HARD block at round 5 until /adhoc:trust-me bypass). Each critic runs a 10-item rule compliance audit and sees the prior round's feedback to verify Claude actually addressed flagged issues. /adhoc:casual (one turn skip), /adhoc:trust-me (one-turn strict bypass), /adhoc:off (session disable). /adhoc:deep for heavier analysis, /adhoc:second-opinion for independent critique.

1 skill · 12 commands · 3 agents · hooks

3

crew

claude

Throw an AI dev at a problem and have it own the outcome. Five Opus agents (router, scout, worker, critic, fresh-eyes) collaborate to investigate, plan, execute, and verify — SSH into systems, spin up infra, edit code, ship features, debug deploys, get airgap bundles working. Worker self-switches between investigating, planning, executing, and verifying modes — one persistent persona, not five different ones. Bounded scout budget (25 tool calls / 5 min, doubled in --paranoid), multi-agent reflexion on stuck (N=2-3 parallel variants + judge — fixes Reflexion's degeneration-of-thought failure mode), critic and fresh-eyes both produce mandatory evidence ledgers of commands they actually ran. One checkpoint (plan approval) for side-effecting tasks, zero for pure investigation. Plan and debrief render in chat; state files exist in .crew/runs/ for resume. Production beats --yolo always. /crew:goal sets a completion condition and runs the worker→critic→fresh-eyes loop unattended — cycle after cycle until critic and fresh-eyes both return pass, or a cycle/time cap stops it — enforced by a Stop hook (goal-gate.py) that blocks the run from ending while the goal is unmet.

6 commands · 5 agents · hooks

3

tidy

claude

Careful low-risk codebase cleanup across 7 focused tracks: deduplication, type consolidation, dead code removal, circular dependency untangling, type strengthening, error-handling cleanup, and deprecated/AI-slop removal. Each track inspects in parallel (read-only), writes a critical assessment, ranks proposed changes by confidence (HIGH / MEDIUM / LOW / UNCERTAIN), and auto-applies ONLY HIGH-confidence LOW-risk changes per batch — running language-appropriate type checks, tests, and lints after each. MEDIUM and LOW changes get surfaced for explicit human decision. Atomic git commits per batch so any failing check is one revert away. Anti-pattern guardrails: never merges code that just LOOKS similar; never removes dynamically-imported / config-referenced / framework-convention / generated code; never strips legitimate boundary types (JSON parses, external APIs, FFI); never silences real error boundaries; never introduces new abstractions just to break a cycle; never uses comments as the source of truth. Refuses to run on a dirty working tree. Default mode is --dry-run (assess only); --apply is opt-in with a checkpoint before changes; --auto skips the checkpoint but never the HIGH-only confidence gate.

4 commands · 8 agents

3

e2e

claude

End-to-end test authoring and maintenance for web apps via Playwright + Playwright MCP. Claude drives a real browser, reads the accessibility tree, and emits *.spec.ts files that pass — then keeps them passing. /e2e:init scaffolds Playwright in the cwd and registers the MCP server. /e2e:write <flow> drives the browser to perform the flow and emits a green spec. /e2e:crawl discovers every route and generates a smoke spec per route. /e2e:matrix produces a routes × roles coverage suite with reused storageState. /e2e:audit runs the suite, reads trace.zip files, and triages failures by root cause. /e2e:record wraps playwright codegen for manual capture. The author skill enforces selector hygiene (getByRole over CSS), auto-wait discipline, and idempotent test design; the diagnose skill drives trace-driven flaky-test triage. The spec-writer subagent isolates MCP-driven spec authoring from the main context.

2 skills · 7 commands · 1 agent

3

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

pake

claudecodex

Package any website or local web build into a lightweight desktop app with Pake CLI.

1 skill

tw93/Pake 63,463

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

Maintain trowel?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins14 plugins