claude-mem
claudecodexPersistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Your Project Intelligence Layer for AI Coding Agents. Professional agents with adaptive model routing on an evidence-backed project knowledge graph.
Plugin rmc from marketplace rm-context-marketplace in rmtemplate/rm-context. Commands read from the repo's manifest — 5 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
business-analysisBusiness Analyst playbook for RM Context — eliciting objectives, stakeholders, requirements, processes and rules, and producing BRD, FSD, SIPOC, process flows, stakeholder analysis, use cases, user stories, acceptance criteria, business rules catalog, gap analysis, scope and RTM with Confirmed/Assum
context-retrievalRetrieve the smallest relevant subset of .rmcontext knowledge for a task (rmc find / graph node / impact) and verify important facts against current source. Use before answering project questions or starting focused work in an initialized repository.
database-intelligenceDatabase and mobile architecture intelligence for RM Context. Use before any database, stored-procedure, schema, migration, Android, Flutter or React Native work in an initialized repository, and whenever a schema or procedure change is requested.
devops-infrastructureInfrastructure & DevOps playbook for RM Context — infrastructure assessment, deployment architecture, Docker, CI/CD, environments, network and reverse proxy, observability, backup/DR, security hardening, runbooks, rollback plans and incident reports, without ever exposing secrets.
documentation-engineHow RM Context documents are created, filled, validated, versioned, approved and exported (Markdown + Mermaid + JSON registry metadata, HTML/PDF/DOCX export). Use whenever creating or updating any professional document in .rmcontext/documents/.
project-analysisCore Intelligence — initialize or refresh a repository's .rmcontext knowledge base with the deterministic rmc scanner, then add evidence-backed architecture, convention and business-rule notes. Use for first-time analysis, refreshes after code changes, and repository understanding.
project-managementProject Manager playbook for RM Context — plan.json schema, WBS, Gantt, roadmap, sprint planning, RAID, RACI, status and health reports, release plans and change control, with progress measured from verified implementation evidence (never from elapsed time).
software-engineeringSenior Software Engineer playbook for RM Context — verifying existing code before proposing change, technical design, ADRs, implementation plans, implementation, code review, security and performance review, refactoring plans, technical debt register, test strategy and engineering standards.
system-analysisSystem Analyst playbook for RM Context — translating business requirements into system specifications, functional/technical flows, UML (use case, activity, sequence, class, state, context), ERD, API specification, data dictionary and integration specification grounded in source evidence.
team-workflowsRM Context team contract — shared rules, ID conventions, rmc CLI usage, hand-offs, model routing and the four collaboration workflows (discovery, feature development, existing-project assessment, change impact). Use when orchestrating or acting as any RM Context agent (BA, SA, PM, Senior Engineer, D
/rmc:adrGenerate Architecture Decision Record (adr) with the senior-engineer agent, using the RM Context template, graph evidence and validation
/rmc:architectureAnalyze the system architecture from evidence — layers, flows, integrations, data, conventions — and update context/architecture.md
/rmc:assessWorkflow C — existing project assessment: scan → BA (business functionality from evidence) → SA (behaviour, data, integrations) → Engineering review → DevOps assessment → PM progress from evidence
/rmc:baBusiness Analyst — clarify business objectives and requirements; produce BRD, FSD, SIPOC, process flows, stakeholder analysis, use cases, user stories, acceptance criteria, business rules, gap analysis, scope
/rmc:devopsInfrastructure & DevOps Engineer — assess infrastructure, Docker, CI/CD, environments, network, observability, backup/DR, security; produce infra docs, runbooks, checklists, rollback plans
/rmc:discoverWorkflow A — new project discovery: BA → SA → Senior Engineer → DevOps → PM, producing connected requirements, system design, feasibility, infrastructure needs and a plan
/rmc:documentGenerate any professional document from the RM Context template catalog (BA, SA, PM, engineering, DevOps) with the right owning agent
/rmc:engineeringSenior Engineer — technical design, ADRs, implementation plans, implementation, code review, refactoring, tech debt, test strategy, engineering standards
/rmc:erdGenerate Entity Relationship Diagram (erd) with the system-analyst agent, using the RM Context template, graph evidence and validation
/rmc:featureWorkflow B — feature development: BA → SA → Engineer plan → PM tasks → implementation → QA → docs → graph/RTM update
/rmc:findSearch project knowledge — graph nodes with evidence, documents and context notes
/rmc:fsdGenerate Functional Specification Document (fsd) with the business-analyst agent, using the RM Context template, graph evidence and validation
/rmc:ganttGenerate the project Gantt chart (SVG + interactive HTML with dependencies, milestones, today line, planned vs actual, critical path)
/rmc:graphBuild and open the interactive knowledge graph (business, system, code, infrastructure and delivery nodes)
/rmc:impactChange impact analysis — affected requirements, modules, APIs, tables, files, infrastructure, tasks and documents for a change
/rmc:initInitialize RM Context — scan the repository into .rmcontext/ (graph, stack, index, viewer) and write architecture notes
/rmc:linkRegister another RM Context-initialized repository as a reference project
/rmc:pmProject Manager — plan and track delivery from evidence; WBS, Gantt, roadmap, sprints, RAID, RACI, status and release plans, change log
/rmc:project-healthProject health report — RAG status from plan evidence, verified vs planned progress, traceability, code/test signals, documentation and knowledge freshness
/rmc:refreshIncrementally refresh RM Context after code changes (only changed files are re-read) and reconcile stale knowledge
/rmc:reviewEngineering review — Senior Engineer code/architecture review of a change set or area, with severity-ranked findings and checks run
/rmc:roadmapGenerate Project Roadmap (roadmap) with the project-manager agent, using the RM Context template, graph evidence and validation
/rmc:routingShow which model each RM Context agent uses (config/models.json + .rmcontext/config.json overrides)
/rmc:rtmRequirement Traceability Matrix — requirements → use cases → system elements → code → tests → tasks, derived from the graph
/rmc:runRun one task end to end as an RM Context workflow — plan the smallest sufficient sequence of specialist agents, run each stage in turn with its routed model and project knowledge, verify, write knowledge back, and return one result
/rmc:saSystem Analyst — translate requirements into system specs; produce SRS, system design, UML, ERD, API spec, data dictionary, integration spec
/rmc:sipocGenerate SIPOC (sipoc) with the business-analyst agent, using the RM Context template, graph evidence and validation
/rmc:srsGenerate System Requirement Specification (srs) with the system-analyst agent, using the RM Context template, graph evidence and validation
/rmc:statusShow RM Context knowledge status — freshness, graph coverage, documents, plan and validation
/rmc:viewerBuild and open the full RM Context project viewer (overview, file explorer, code/API/database explorers, graph views, documents, Gantt)
architectureCore Intelligence analyst — runs and interprets the rmc scanner, then writes evidence-backed overview, architecture, conventions and code-observed business-rule notes and records verified relationships the scanner cannot see. Use for initial repository analysis, large refreshes and deep "how does th
business-analystBusiness Analyst — elicits and analyses business objectives, stakeholders, processes, rules and requirements; produces BRD, FSD, SIPOC, process flows, stakeholder analysis, use cases, user stories, acceptance criteria, business rules catalog, gap analysis, scope and RTM. Use for requirement clarific
devops-engineerInfrastructure & DevOps Engineer — assesses infrastructure, deployment architecture, Docker, CI/CD, environments, network and reverse proxy, observability, backup/DR, security hardening, cost, reliability and scalability; produces infrastructure architecture, deployment diagram, CI/CD spec, environm
documentationDocumentation — keeps .rmcontext documents, context notes and graph metadata consistent after verified changes; revises affected documents, regenerates graph/plan-derived sections, and keeps traceability links current. Use after implementation or when rmc status reports documents needing review.
project-managerProject Manager — plans and tracks delivery in structured plan.json; produces project charter, scope, WBS, Gantt (SVG/HTML with critical path), roadmap, sprint plan and backlog, milestone tracking, RAID log, RACI, status and health reports, release plan and change request log. Progress is measured o
qaQA — independently verifies changes against requirements and acceptance criteria, finds regressions and edge-case failures, runs focused tests, and writes test cases. Read-only on source. Use after implementation or to review a change set.
quick-qaQuick Q&A — answers lightweight project questions, locates files/functions/APIs/tables, and retrieves documented facts from .rmcontext with minimal reading. Use for simple lookups; escalates broad investigations.
senior-engineerSenior Software Engineer — reviews architecture and code quality, designs maintainable solutions, implements features and fixes, refactors, reviews PRs and plans, finds security and performance issues, defines conventions, protects backward compatibility and validates implementation against requirem
system-analystSystem Analyst — translates business requirements into system specifications; analyses existing systems, flows, data structures, integrations, API contracts, edge cases and failure scenarios; produces SRS, system design spec, UML (use case/activity/sequence/class/state/context), ERD, API spec, data
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" session-start
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" prompt
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" pre-agent
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" pre-bash
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" post-tool
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" post-agent
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" post-agent
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" subagent-start
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" subagent-stop
node "${CLAUDE_PLUGIN_ROOT}/scripts/hooks.mjs" stop
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
AI-powered codebase understanding — analyze, visualize, and explain any project
9 skills · 10 agents · hooks
Knowledge graph construction — entity extraction, relation mapping, and pathfinder graph traversal
2 skills · 1 command · 1 agent
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
Product, legal, and business specialists - product strategy, licensing, project management, UX research
A Codex-native bridge to Basic Memory for durable engineering context, decisions, and resumable checkpoints.
8 skills · 1 MCP server · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.