anoopkansupada aff14a72df feat(plan-eng-review): add Step 0.5 — existing-capability check before new substrate code ... When a plan touches a knowledge-graph or agent-runtime substrate (gbrain, OpenClaw, Hermes), run a 60-second check before designing new infrastructure: ssh <host> 'gbrain integrations list && launchctl list | grep -i gbrain' Most recipe-driven substrates already ship a senses + reflexes system that IS the signal-detector / autopilot / ingest pattern. Configure or extend existing recipes (markdown files) instead of building parallel ops/ infrastructure. Why: 2026-05-17 in hash-lemma, /plan-eng-review accepted a plan to extract a JSONL queue lib + producer + consumer bin + LaunchAgent + OAuth-DCR migration to wire "signal-detector on every Slack message" — when gbrain's `integrations` system already shipped the pattern (11 senses + 1 reflex, recipe-based). The 60-second check would have flagged the wrong-buildout at scope-lock, saving ~3-5 days of misdirected code. Substrates with no equivalent capability surface (pure web apps, libraries, CLIs) skip the step. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-18 10:32:00 -04:00
..
SKILL.md	feat(plan-eng-review): add Step 0.5 — existing-capability check before new substrate code	2026-05-18 10:32:00 -04:00
SKILL.md.tmpl	feat(plan-eng-review): add Step 0.5 — existing-capability check before new substrate code	2026-05-18 10:32:00 -04:00