crabshell-marketplace

Crabshell

Claude Code plugin that makes Claude remember, verify, and self-correct.

Three pillars:

1. Session memory — Auto-saves context across sessions. Delta extraction, Haiku summarization, token-based rotation. No manual setup.
2. Behavioral correction — Injects verification-first rules and interference pattern detection every prompt. Twelve guard hooks block sycophancy, scope reduction, overcorrection, and shortcuts at runtime.
3. Structured workflows — D/P/T/I/W document system with 17 skills for planning, investigating, iterative improvement (regressing), and light-workflow tracing.

All plugin output lives under .crabshell/ — gitignored, clean project root.

Installation

/plugin marketplace add ZipperBagCoffee/crabshell
/plugin install crabshell

After installation, you don't need to do anything. It works automatically.

How It Works

1. Session start - Loads saved content from previous sessions into Claude's context
2. During work - Auto-save triggers every 15 tool uses (configurable), Claude records decisions/patterns/issues directly
3. Session end - Full conversation backup + final save

What Gets Saved

Automatic (No action needed)

• logbook.md - Session summaries accumulate here (auto-rotates at 23,750 tokens)
• logbook_*.md - Rotated archives (L2)
• *.summary.json - L3 summaries (Haiku-generated)
• sessions/*.l1.jsonl - Detailed session transcripts (L1)

Manual Setup (Optional)

If there's information you want Claude to know every session, directly edit the files:

# Create/edit files in your project's .crabshell/memory/ folder
echo "React + TypeScript web app." > .crabshell/project.md

Or just ask Claude: "Save the project info to project.md"

With this setup, Claude starts every new session knowing this information.

Slash Commands

Works in any project where the plugin is installed:

Command	Description
/crabshell:save-memory	Save now (don't wait for auto-save)
/crabshell:load-memory	Reload memory (after manual edits)
/crabshell:search-memory query	Search past sessions
/crabshell:clear-memory old	Clean up files older than 30 days
/crabshell:discussing "topic"	Create/update a discussion document
/crabshell:planning "topic"	Create/update a plan document
/crabshell:ticketing P001 "topic"	Create/update a ticket tied to a plan
/crabshell:investigating "topic"	Multi-source multi-agent investigation
/crabshell:regressing "topic" N	Run N cycles of P→T wrapped by a single Discussion, with verification-based optimization
/crabshell:light-workflow	Run the 11-phase agent orchestration workflow (standalone tasks)
/crabshell:verifying	Create/run project-specific verification tools
/crabshell:lessons	Check/create project-specific lessons
/crabshell:status	Healthcheck of plugin state (memory, regressing, verification, version)

Document Management (5-Document System: D/P/T/I/W)

Track project work through structured, append-only documents:

Skill	ID Format	Statuses	Use For
/discussing	D001	open, concluded	Decisions, dialogues, conclusions
/planning	P001	draft, approved, in-progress, done	Implementation plans with steps
/ticketing	P001_T001	todo, in-progress, done, verified	Session-sized work units tied to plans
/investigating	I001	open, concluded	Multi-source investigations with cross-review
/light-workflow	W001	open, concluded	Light-workflow tracing (standalone tasks)

Each document type has its own folder under .crabshell/ with an INDEX.md for status tracking. Tickets inherit from plans and require verification-at-creation (TDD principle).

Agent Orchestration Workflow

For complex tasks, the light-workflow skill runs an 11-phase process with 3-layer architecture:

Work Agent     →  Analysis, planning, implementation
Review Agent   →  Verify, cite evidence, PASS/FAIL
Orchestrator   →  Intent guardian, meta-review, final authority

Key features:

• Intent Anchor - Non-negotiable requirements defined in Phase 1, enforced at every gate
• Cross-Review - When 2+ reviewers run in parallel, adversarial cross-examination is mandatory
• Runtime Verification - Mandatory runtime verification in Phase 8/9/10 (not just static checks)
• 1 Ticket = 1 Workflow - Each ticket gets its own independent workflow execution

Regressing (Iterative Optimization)

For tasks requiring multiple improvement cycles, /regressing "topic" N runs N cycles of Plan→Ticket→Verify: