hippo-feature

Implements one memory mechanic from RESEARCH.md using a tiered micro-eval TDD loop.

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill hippo-feature-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hippo-feature
Source: https://github.com/kitfunso/claude-config/tree/main/skills/hippo-feature
Command: npx skills add https://github.com/kitfunso/claude-config --skill hippo-feature-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building new memory features for the hippo system without a disciplined evaluation loop leads to regressions and wasted hours on expensive LoCoMo benchmark runs. This Skill enforces a strict eval pyramid so every feature is proven on fast micro fixtures before touching slower benchmarks. ## Core Features & Use Cases - Tiered eval pyramid: Runs a ~30s micro benchmark on every change, a 5-10 minute stratified LoCoMo smoke test before PRs, and reserves the full LoCoMo run as a release gate only. - RED-GREEN TDD loop: Writes a failing micro fixture first, implements the smallest diff to pass it, then checks all existing fixtures for regressions. - Proactive branch and review management: Handles dirty WIP safely, creates feature branches, and spawns a senior-code-reviewer sub-agent for plan review on non-trivial features. - Use Case: You want to add the ACC EVC-adaptive recall mechanic from RESEARCH.md. The Skill picks the feature, writes a failing fixture, implements it, validates against micro and LoCoMo smoke benchmarks, and commits one logical change. ## Quick Start Run the hippo-feature skill with a feature name like acc-evc to build that memory mechanic from RESEARCH.md through the micro-eval TDD loop.

Frequently Asked Questions about hippo-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new memory feature to the hippo system?▼

Pick a feature from the RESEARCH.md PFC priority table, write a failing micro fixture at benchmarks/micro/fixtures/<feature>.json first, then implement the smallest diff that makes it pass. Verify no existing fixtures regress before running the LoCoMo smoke test.

What is the eval pyramid for hippo feature development?▼

The eval pyramid has three tiers: Tier 1 micro benchmarks (~30s) run on every code change, Tier 2 stratified LoCoMo smoke tests (~5-10 min) run before opening a PR, and Tier 3 full LoCoMo runs only as an explicit release gate.

When should I run the full LoCoMo benchmark?▼

Run the full LoCoMo benchmark only on explicit user request as a release gate. It takes roughly 85 minutes in evidence mode or 6 hours with a judge, so a green Tier 2 smoke test is sufficient for normal feature work.

Why must the micro fixture fail before implementing a feature?▼

The fixture must encode behavior the current system cannot satisfy, proving the test actually exercises the new mechanic. If it passes on main today, the fixture is wrong and must be made harder before writing any implementation code.

Can I bundle multiple PFC features into one branch?▼

No, the hard rule is one feature at a time. Do not bundle ACC and vmPFC work into one branch even if RESEARCH.md groups them, and each feature gets one logical commit containing code, fixture, and result baseline.

What are the constraints on salience gate changes?▼

Any salience work must be default-off and must prove a positive delta on the Tier 2 LoCoMo smoke test before being enabled. The v1 60% lexical-overlap gate previously destroyed LoCoMo scores from 0.28 to 0.02.