Review, search, and manage workflow memories
Searches, reviews, and manages workflow memories to apply past learnings to current tasks.
/plugin marketplace add standardbeagle/standardbeagle-tools/plugin install workflow@standardbeagle-tools[search-query]Search, review, and manage memories saved from previous workflow loops.
Memories preserve valuable learnings from workflow execution:
This command helps you:
/workflow:review-memories
Shows all memories organized by category.
/workflow:review-memories authentication
/workflow:review-memories "rate limiting"
/workflow:review-memories security xss
Searches memory titles, tags, and content.
/workflow:review-memories --category=workflow_pattern
/workflow:review-memories --category=lesson
/workflow:review-memories --scope=project
/workflow:review-memories --scope=user
/workflow:review-memories --tags=security,authentication
/workflow:review-memories --tags=xss
From slop-mcp (if available):
# Use slop-mcp to fetch memories
slop-mcp memory list --scope=project
slop-mcp memory list --scope=user
From local storage (fallback):
# Read from .claude/memories/
ls -1 .claude/memories/*.md
# Parse YAML frontmatter and content
for file in .claude/memories/*.md; do
# Extract metadata and content
done
Apply filters:
Sort by:
Summary View:
Workflow Memories
=================
Found 12 memories
Workflow Patterns (4):
✓ Auth tasks require rate limiting verification
✓ UI tasks benefit from screenshot comparison
✓ Database migrations in refactor loop only
✓ API errors include correlation ID
Technical Decisions (3):
✓ JWT authentication with 24h expiry
✓ PostgreSQL over MongoDB for ACID
✓ bcrypt cost factor 12 for passwords
Lessons Learned (3):
⚠ XSS in user profile - always sanitize
⚠ Race condition in payments - use transactions
⚠ Memory leak from unclosed connections
Code Patterns (2):
✓ API pattern: /api/v1/{resource}/{action}
✓ Parameterized queries for SQL injection prevention
To view a memory: /workflow:view-memory <title>
Detailed View:
If specific query or only 1-3 results:
Memory: Auth tasks require rate limiting verification
=========================================================
Category: workflow_pattern
Scope: project
Tags: authentication, security, rate-limiting
Confidence: high
Created: 2026-01-14 10:23:15
Source: Task 2
## What
When implementing authentication endpoints, always include rate limiting
in the security verification phase.
## Why
Brute force vulnerabilities discovered in Task 2 could have been prevented
with upfront rate limiting verification.
## When
Apply to all authentication-related tasks:
- Login endpoints
- Password reset
- Registration
- 2FA verification
## How
Checklist for verification phase:
- [ ] Rate limit login endpoint (5 attempts/min/IP)
- [ ] Rate limit password reset (3 attempts/hour/email)
- [ ] Test with concurrent requests
- [ ] Verify 429 responses include Retry-After header
## Evidence
Security loop in Task 2 found brute force vulnerability.
After adding rate limiting, no further vulnerabilities found.
---
Related memories: 2
- JWT authentication with 24h expiry
- Rate limiting pattern: 5 attempts/min/IP for auth
After displaying memories, offer actions:
actions:
view_details: "Show full content of a memory"
apply_to_task: "Use memory in current task"
update_memory: "Edit memory content"
delete_memory: "Remove obsolete memory"
export_memories: "Export to file for sharing"
link_memories: "Connect related memories"
Interactive:
What would you like to do?
1. View details of a specific memory
2. Apply memory to current task
3. Update a memory
4. Delete a memory
5. Export memories to file
6. Nothing, just browsing
Show full memory with all fields:
/workflow:view-memory "Auth tasks require rate limiting"
Displays complete content with metadata.
Incorporate memory into current work:
Applying memory: "Auth tasks require rate limiting"
This memory suggests:
- Add rate limiting to authentication endpoints
- Test with concurrent requests
- Verify 429 responses
Should I:
1. Add this to current task checklist
2. Create a new task for rate limiting
3. Just keep it in mind
Modify existing memory:
Update memory: "XSS in user profile"
Current content:
[Shows current memory]
What would you like to change?
1. Update content (new learnings)
2. Add tags
3. Change confidence level
4. Update related memories
5. Cancel
Save updated version with timestamp.
Remove obsolete memory:
Delete memory: "Use Redux for state management"
This memory is from 3 months ago.
Has it become obsolete?
1. Yes, delete it (moved to Zustand)
2. No, keep it
3. Archive it (keep but mark obsolete)
Confirm before deletion, optionally archive instead.
Generate file for sharing:
Export memories
Options:
1. Export all memories (12 total)
2. Export by category (choose: workflow_pattern, lesson, etc.)
3. Export by scope (choose: project, user, global)
4. Export search results
Format:
1. Markdown (readable)
2. JSON (structured)
3. YAML (human-friendly structured)
Output:
1. File: .claude/memories-export-2026-01-14.md
2. Clipboard
3. Display inline
Semantic search if available:
Show overview stats:
Memory Statistics
=================
Total memories: 42
By category:
- Workflow patterns: 12
- Technical decisions: 8
- Code patterns: 7
- Lessons learned: 10
- Verification strategies: 5
By scope:
- Project: 28
- User: 12
- Global: 2
By confidence:
- High: 35
- Medium: 6
- Low: 1
Most used tags:
1. security (15 memories)
2. authentication (12)
3. testing (10)
4. api (8)
5. database (7)
Recent activity:
- 3 memories added this week
- 1 memory updated yesterday
- 0 memories deleted this month
Oldest memory: 3 months ago
Newest memory: 2 hours ago
Suggest relevant memories:
Starting task: "Add OAuth2 authentication"
Relevant memories found (3):
1. JWT authentication with 24h expiry
2. Auth tasks require rate limiting verification
3. XSS in user-generated content
Would you like to:
1. Review these memories before starting
2. Apply patterns from memories
3. Continue without reviewing
Alert if memory applies:
[During security verification phase]
💡 Memory reminder: "Auth tasks require rate limiting verification"
This task involves authentication. Don't forget to:
- [ ] Rate limit login endpoint
- [ ] Test with concurrent requests
- [ ] Verify 429 responses
View full memory: /workflow:view-memory "Auth tasks require rate limiting"
Check if memory was useful:
Task completed: "Add OAuth2 authentication"
You referenced memory: "JWT authentication with 24h expiry"
Was this memory helpful?
1. Yes, very helpful (increase confidence)
2. Somewhat helpful
3. Not helpful (needs update?)
4. Memory is now obsolete (archive?)
Periodically review memories:
Check for:
Memory Health Report
====================
Status: Good
Concerns:
⚠ 2 memories not accessed in 3 months (possibly obsolete)
⚠ 1 low-confidence memory (needs validation)
✓ No duplicate memories detected
✓ All memories properly tagged
Recommendations:
1. Review: "Old database pattern" (3 months old, not used)
2. Validate: "Experimental caching strategy" (low confidence)
3. Update: "API versioning" (new v2 API released)
/workflow:review-memories security
Found 5 memories:
1. XSS in user profile - always sanitize (lesson)
2. Auth tasks require rate limiting (workflow_pattern)
3. SQL injection prevention with parameterized queries (code_pattern)
4. JWT authentication with 24h expiry (technical_decision)
5. OWASP Top 10 verification checklist (verification)
/workflow:review-memories --category=lesson
Lessons Learned (10 memories):
1. XSS in user profile - always sanitize
2. Race condition in payments - use transactions
3. Memory leak from unclosed connections
4. N+1 query problem in user list endpoint
5. CORS misconfiguration exposed API
...
# Starting task: Add password reset
/workflow:review-memories password
Found 2 relevant memories:
1. Auth tasks require rate limiting verification
2. Password reset flow security checklist
Apply "Password reset flow security checklist" to current task?
1. Yes, add to task context
2. View full memory first
3. Skip
[User selects 1]
Applied to task. Checklist added:
- [ ] Rate limit: 3 attempts/hour/email
- [ ] Email token expires in 1 hour
- [ ] One-time use tokens
- [ ] Log all reset attempts
- [ ] Verify email ownership
.claude/memories/Memory review is successful when: