memory-ship

Deploys a designed memory architecture into a codebase through an 11-phase build workflow.

Updated May 16, 2026
One-click install
npx skills add https://github.com/RohanRaoCs/memory-architect --skill memory-ship-rohanraocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memory-ship
Source: https://github.com/RohanRaoCs/memory-architect/tree/main/skills/memory-ship
Command: npx skills add https://github.com/RohanRaoCs/memory-architect --skill memory-ship-rohanraocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an AI memory architecture document into working production code is error-prone: wiring retrieval and write paths, enforcing per-user isolation, handling dedup and retention, and validating everything takes days of manual effort. This Skill automates that deployment end-to-end with checkpoints and tests. ## Core Features & Use Cases - 11-Phase Autonomous Build: Runs doc preflight, codebase comprehension, drift checking, stack research, prerequisites, setup, wiring, quality, hardening, eval, and a readiness report with resumable checkpoints logged to .memory-ship/build-log.md. - Framework-Native Wiring with Safety Wrapper: Delegates retrieval, ranking, dedup, and classification to the chosen memory framework (Mem0, Zep, pgvector, Pinecone, etc.) while enforcing universal guarantees like user_id isolation, prompt-injection sanitization, token budgets, and GDPR forgetUser. - Verified Quality Gates: Every code-touching phase ends with step tests covering dedup, contradiction supersession, retention, leak tests, and degraded-mode behavior before the build is declared done. - Use Case: After running /memory-design to produce an architecture doc for a support chatbot, invoke /memory-ship to install packages, create migrations, wire memory into every LLM call site, and receive a readiness report with eval results. ## Quick Start Type /memory-ship in your AI assistant after generating an architecture doc with /memory-design to build the memory system into your project.

Frequently Asked Questions about memory-ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a memory architecture doc into my codebase?

Run /memory-ship after generating an architecture doc with /memory-design. It reads the doc, researches the chosen stack, then builds the memory system through 11 phases with checkpoints, ending in a readiness report.

What happens if /memory-ship is interrupted mid-build?

The build is resumable. Every checkpoint writes a phase marker to .memory-ship/build-log.md, and on restart the skill detects the last completed phase and resumes from the next one without redoing finished work.

Does memory-ship work with Mem0, Zep, and pgvector?

Yes. Phase 4 researches the chosen components and builds a capability matrix marking each concern as native or DIY. The wiring phase delegates to framework-native APIs first and only adds custom fallback logic where the framework lacks a feature.

When does memory-ship ask for user input during the build?

It runs autonomously except for Checkpoint 6, where it prompts for required secrets and migration approval. It also stops for hard blockers and a Phase 9 risk-accept gate if a hardening check fails.

How does memory-ship enforce per-user data isolation?

Phase 9 verifies every memory search and write carries a non-null user_id, checks RLS policies on Postgres or namespace filters on managed vector stores, and runs a leak test confirming one user cannot retrieve another user's memories.