clay-good

Retrieve relevant functions, callers, spec sections, and insertion points from OpenLore before reading source files. Use when starting work that needs structural orientation in an existing codebase.

Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.

Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.

Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.

Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.

Author a new OpenSpec domain specification from deterministic OpenLore MCP evidence. Use when asked to reverse-engineer, generate, or document a specification for existing code.

Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.

Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.

Code implementation specialist. Spawns to implement a specific feature, module, or function.

Codebase exploration and analysis specialist. Fast research before implementation.

Security and code quality reviewer. Read-only deep review for vulnerabilities and quality issues.

Test runner and fixer. Spawns to run the full test suite, diagnose failures, and fix them.

Run the project linter and formatter, fix all violations.

Run the full test suite, diagnose any failures, fix them, and re-run until green.

Update .codelicious/STATE.md with accurate current status.

Run all quality checks — tests, lint, format, security scan.

Code implementation specialist. Spawns to implement a specific feature, module, or function.

Run all quality checks — tests, lint, format, security scan.

Screen a mechanical or structural part against cited engineering checks with Anvilate, and report the result the way an engineer would. Use when asked to size, check, or validate a part, joint, member, or vessel, or to interpret an Anvilate scorecard.