StackMap
Subscribe

pro-workflow alternatives

Curated alternatives to pro-workflow — and why you'd switch.

claude-reflect

Claude Code plugin that learns from your corrections — hooks capture them in-session, /reflect syncs approved learnings to CLAUDE.md/AGENTS.md, /reflect-skills mines history into reusable commands.

Why switchSame core job — corrections that stick across Claude Code sessions. claude-reflect is the focused plugin (corrections → CLAUDE.md); pro-workflow builds a whole SQLite-backed memory-and-hooks platform around the idea.
Full comparison →
ECC

Cross-harness 'operating system' for coding agents — 268 skills, 66 agents, hooks, rules, memory persistence, instinct-based continuous learning and AgentShield security scanning. MIT.

Why switchSame job — a persistent operating layer under coding-agent sessions with hooks, learned rules and quality gates. pro-workflow is one SQLite store focused on Claude Code; ECC is the maximalist cross-harness system spanning 7+ harnesses with skills, agents and security tooling.
Full comparison →
opencode-mem

OpenCode plugin giving coding agents persistent cross-session memory — local SQLite + vector search, automatic memory capture, user-profile learning, and a web UI. Nothing leaves your machine.

Why switchSame job on rival harnesses: a persistent local store under every coding-agent session. pro-workflow puts SQLite + FTS5 rules under Claude Code; opencode-mem puts SQLite + vector recall with auto-capture under OpenCode.
Full comparison →