pro-workflow

The Problem

You correct Claude the same way 50 times. You explain conventions every new session. Context compacts, learnings vanish, mistakes repeat. You research the same topic in three different sessions because there is nowhere durable for the answers to land.

Every Claude Code user hits this wall.

The Solution

Pro Workflow puts a single SQLite store underneath every session.

• Self-correction memory — every correction becomes a rule, FTS5-searchable, auto-loaded on session start.
• Knowledge plane — persistent research wikis on disk + FTS5 shadow index, queryable from any session, optionally grown by an auto-research loop.
• Quality gates — LLM-powered hooks, deterministic git/secret guards, compaction-aware state, cost tracking.

After 50 sessions you barely correct anything. After a week of auto-research, your wiki on a topic is denser than the curated lists you started from.

Session 1:  You → "Don't mock the database in tests"
            Claude → Proposes rule → You approve → Saved to SQLite

Session 2:  SessionStart loads all learnings + lists your wikis
            UserPromptSubmit auto-injects top wiki hits when relevant
            Claude writes integration tests, cites the right wiki page

Session 50: Correction rate near zero. Wiki has 200 cited claims.

Install

Pro Workflow is published in two places: the Claude Code plugin marketplace (native), and SkillKit (cross-agent translator). Other agents do not have first-class plugins yet — SkillKit translates the skill bundle into each agent's native skill format.

Claude Code (native)

/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflow

Cursor, Codex, Copilot CLI, Droid, Gemini CLI, OpenCode, and 26 more (via SkillKit)

SkillKit translates the 34 skills + 22 commands into each agent's native skill format and drops them in the right config directory.

npx skillkit install rohitg00/pro-workflow --agent <name> --force

Notes:

• Use rohitg00/pro-workflow (the GitHub form), not the bare name — skillkit install resolves providers from owner/repo, not marketplace slugs.
• --force is currently required: SkillKit's security scanner has open false positives on standard Node patterns (child_process imports, Bearer ${env} template literals) that block legit skills like survey-generator and safe-mode. Tracked at skillkit#129.

Supported <name> values: cursor, codex, gemini-cli, opencode, github-copilot, droid (factory), antigravity, amp, clawdbot, cline, codebuddy, commandcode, continue, crush, goose, kilo, kiro-cli, mcpjam, mux, neovate, openhands, pi, qoder, qwen, roo, trae, universal, vercel, windsurf, zencoder. Pass --agent universal for a portable bundle.

After install, run skillkit sync to register the skills with the target agent's config.

If neither path works for your setup, clone and copy the bundle directly. Adjust the destination to your agent's skill directory (e.g. ~/.cursor/rules/, ~/.gemini/extensions/, etc.).

git clone https://github.com/rohitg00/pro-workflow.git /tmp/pw
cd /tmp/pw && npm install && npm run build

cp -r /tmp/pw/templates/split-claude-md/* ./.claude/
cp -r /tmp/pw/skills    ~/.claude/skills/
cp -r /tmp/pw/commands  ~/.claude/commands/
cp    /tmp/pw/hooks/hooks.json ~/.claude/hooks.json

First-run smoke test

/doctor              # confirms SQLite store, hooks, skills load
/wrap-up             # runs the end-of-session ritual (no-op on fresh install)

If /doctor reports KB: missing, run cd ~/.claude/plugins/*/pro-workflow && npm install && npm run build — the SQLite components need a build step a handful of marketplaces skip.

What to type first

After install you have 34 auto-trigger skills and 22 slash commands. You don't need to memorize them; the agent picks the right skill from your prompt. The five commands below cover 80% of daily use:

Full list: commands/ · skills/ · /list inside any session.

60-second tour

# 1. Self-correction (existing)
/learn-rule          # capture a correction
/wrap-up             # end session, persist learnings, audit changes
/insights            # heatmaps, trends, productivity

# 2. Knowledge plane (v3.3, new)
/wiki init agent-memory --title "Agent Memory" --flavor research
/wiki page agent-memory wiki/concepts/episodic-memory.md --type concept
/wiki ask "what is episodic memory" --wiki agent-memory

# 3. Auto-research (budget-capped, opt-in)
/wiki seed agent-memory "memory consolidation in agents"
/wiki research agent-memory --max-pages 5 --budget-usd 0.50

# 4. Hybrid retrieval (BM25 + vector RRF, optional)
/wiki embed agent-memory                       # OPENAI_API_KEY or VOYAGE_API_KEY
/wiki hybrid "consolidation patterns" --wiki agent-memory

# 5. Multi-LLM deliberation (transcript persists as a wiki page)
/wiki council "should we adopt episodic memory?" --wiki agent-memory

# 6. Browse the wiki visually (single-file HTML, S3-shareable)
/wiki view agent-memory
open ~/.pro-workflow/wikis/agent-memory/derived/viewer.html

# Kill switch for any auto loop
touch ~/.pro-workflow/STOP

UserPromptSubmit auto-loads top-3 wiki hits when prompts mention indexed topics. SessionStart lists registered wikis and recent learnings.

What's new in v3.3

Persistent knowledge plane on top of self-correction memory.

Plus: /wiki command (now with view), learn-rule Wiki: <slug> scoping, schema additions (wikis, wiki_pages + FTS5, wiki_sources, wiki_claims, wiki_seeds, wiki_embeddings, learnings_wiki), reactive file-watcher seed enqueue, cron-tick driver, /doctor extended with KB + provider sections.

Comparison