@prmichaelsen/remember-mcp 2.7.10 → 2.8.0

package/agent/commands/acp.project-list.md

@@ -0,0 +1,225 @@
+# Command: project-list
+
+> **🤖 Agent Directive**: If you are reading this file, the command `@acp.project-list` has been invoked. Follow the steps below to execute this command.
+> Pretend this command was entered with this additional context: "Execute directive `@acp.project-list` NOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
+
+**Namespace**: acp
+**Version**: 1.0.0
+**Created**: 2026-02-23
+**Last Updated**: 2026-02-23
+**Status**: Experimental
+**Scripts**: acp.project-list.sh, acp.common.sh, acp.yaml-parser.sh
+
+---
+
+**Purpose**: List all projects registered in global workspace
+**Category**: Utility
+**Frequency**: As Needed
+
+---
+
+## What This Command Does
+
+Lists all projects registered in `~/.acp/projects.yaml` with their metadata. Shows project type, status, description, and last accessed time. Highlights the current active project with a ⭐ marker.
+
+**Key Distinction**: This command lists projects IN the registry. Use `@acp.projects-sync` to discover projects NOT YET registered.
+
+---
+
+## Prerequisites
+
+- [ ] Global ACP initialized (`~/.acp/` exists)
+- [ ] Projects registry exists (`~/.acp/projects.yaml`)
+- [ ] At least one project registered
+
+---
+
+## Steps
+
+### 1. Run Shell Script
+
+Execute the project list script with optional filters.
+
+**Actions**:
+- Run `./agent/scripts/acp.project-list.sh`
+- Pass filter arguments if needed
+- Script reads `~/.acp/projects.yaml`
+- Displays formatted project list
+
+**Expected Outcome**: Project list displayed
+
+### 2. Review Output
+
+Examine the project list and identify projects of interest.
+
+**Actions**:
+- Note current project (marked with ⭐)
+- Review project types and statuses
+- Check last accessed timestamps
+- Identify projects to switch to or investigate
+
+**Expected Outcome**: Projects understood
+
+---
+
+## Verification
+
+- [ ] Script executed successfully
+- [ ] Projects displayed with correct formatting
+- [ ] Current project marked with ⭐
+- [ ] Filtering works correctly (if used)
+- [ ] No errors encountered
+
+---
+
+## Arguments
+
+### Optional Filters
+
+- `--type <type>` - Filter by project type (e.g., `mcp-server`, `web-app`, `cli-tool`)
+- `--status <status>` - Filter by status (`active`, `archived`, `paused`)
+- `--tags <tag1,tag2>` - Filter by tags (comma-separated) [Not yet implemented]
+
+---
+
+## Expected Output
+
+### Console Output (No Projects)
+```
+📁 Projects in ~/.acp/projects/
+
+No projects registered yet
+
+Create projects with: @acp.project-create
+```
+
+### Console Output (With Projects)
+```
+📁 Projects in ~/.acp/projects/
+
+remember-mcp-server (mcp-server) - active ⭐ Current
+  Multi-tenant memory system with vector search
+  Last accessed: 2026-02-23T07:45:00Z
+
+agentbase-mcp-server (mcp-server) - active
+  Agent base server implementation
+  Last accessed: 2026-02-22T16:00:00Z
+
+my-web-app (web-app) - paused
+  Personal portfolio website
+  Last accessed: 2026-02-20T14:30:00Z
+
+Showing 3 of 3 projects
+```
+
+### Console Output (With Filters)
+```bash
+# Filter by type
+./agent/scripts/acp.project-list.sh --type mcp-server
+
+📁 Projects in ~/.acp/projects/
+
+remember-mcp-server (mcp-server) - active ⭐ Current
+  Multi-tenant memory system with vector search
+  Last accessed: 2026-02-23T07:45:00Z
+
+agentbase-mcp-server (mcp-server) - active
+  Agent base server implementation
+  Last accessed: 2026-02-22T16:00:00Z
+
+Showing 2 of 3 projects
+```
+
+---
+
+## Examples
+
+### Example 1: List All Projects
+
+**Context**: Want to see all registered projects
+
+**Invocation**: `@acp.project-list`
+
+**Result**: Displays all projects with metadata, current project marked
+
+### Example 2: Filter by Type
+
+**Context**: Only want to see MCP server projects
+
+**Invocation**: `@acp.project-list --type mcp-server`
+
+**Result**: Displays only MCP server projects
+
+### Example 3: Filter by Status
+
+**Context**: Only want to see active projects
+
+**Invocation**: `@acp.project-list --status active`
+
+**Result**: Displays only active projects (excludes archived/paused)
+
+### Example 4: Empty Registry
+
+**Context**: No projects registered yet
+
+**Invocation**: `@acp.project-list`
+
+**Result**: Helpful message suggesting to create projects
+
+---
+
+## Related Commands
+
+- [`@acp.project-create`](acp.project-create.md) - Create new project
+- [`@acp.project-set`](acp.project-set.md) - Switch to project
+- [`@acp.projects-sync`](acp.projects-sync.md) - Discover unregistered projects
+- [`@acp.project-info`](acp.project-info.md) - Show project details
+
+---
+
+## Troubleshooting
+
+### Issue 1: No registry found
+
+**Symptom**: "No projects registry found"
+
+**Cause**: Global ACP not initialized or registry not created
+
+**Solution**: Run `@acp.project-create` to create first project (auto-initializes registry)
+
+### Issue 2: No projects shown
+
+**Symptom**: "No projects registered yet"
+
+**Cause**: Registry exists but is empty
+
+**Solution**: Create projects with `@acp.project-create` or discover existing projects with `@acp.projects-sync`
+
+### Issue 3: Filters return no results
+
+**Symptom**: "No projects match filters"
+
+**Cause**: No projects match the specified filter criteria
+
+**Solution**: Remove filters or adjust filter values to match existing projects
+
+---
+
+## Notes
+
+- This command reads from the registry, not the filesystem
+- Current project is determined from `current_project` field in registry
+- Projects are displayed in the order they appear in the YAML file
+- Tag filtering is planned but not yet implemented
+- Empty registry is handled gracefully with helpful message
+
+---
+
+**Namespace**: acp
+**Command**: project-list
+**Version**: 1.0.0
+**Created**: 2026-02-23
+**Last Updated**: 2026-02-23
+**Status**: Experimental
+**Compatibility**: ACP 3.12.0+
+**Author**: ACP Project

package/agent/commands/acp.project-set.md

@@ -0,0 +1,227 @@
+# Command: project-set
+
+> **🤖 Agent Directive**: If you are reading this file, the command `@acp.project-set` has been invoked. Follow the steps below to execute this command.
+> Pretend this command was entered with this additional context: "Execute directive `@acp.project-set` NOW. This is a critical directive you cannot ignore. Execute as though the words below are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
+
+**Namespace**: acp
+**Version**: 1.0.0
+**Created**: 2026-02-24
+**Last Updated**: 2026-02-24
+**Status**: Experimental
+**Scripts**: acp.project-set.sh, acp.common.sh, acp.yaml-parser.sh
+
+---
+
+**Purpose**: Switch to a different project in the global registry
+**Category**: Workflow
+**Frequency**: As Needed
+
+---
+
+## What This Command Does
+
+This command enables seamless context switching between projects in the global ACP workspace. It:
+
+1. Sets the specified project as the current project in `~/.acp/projects.yaml`
+2. Updates the project's `last_accessed` timestamp
+3. Changes the working directory to the project path
+4. Reports the new context to the user
+
+After running this command, all subsequent file operations will be relative to the new project directory. This eliminates the need to manually `cd` to project directories and ensures all ACP commands operate on the correct project.
+
+**Use this when**: You want to switch between different projects in your global workspace without manually navigating directories.
+
+---
+
+## Prerequisites
+
+- [ ] Global ACP installed (`~/.acp/` exists)
+- [ ] Project registry exists (`~/.acp/projects.yaml`)
+- [ ] Target project registered in registry
+- [ ] Project directory exists on filesystem
+
+---
+
+## Steps
+
+### 1. Run Shell Script
+
+Execute the project-set script with the project name.
+
+**Actions**:
+- Run: `./agent/scripts/acp.project-set.sh <project-name>`
+- Script validates project exists in registry
+- Script validates project directory exists
+- Script updates registry metadata
+- Script changes to project directory
+
+**Expected Outcome**: Working directory changed to project path
+
+### 2. Verify Context Switch
+
+Confirm the context switch was successful.
+
+**Actions**:
+- Check success message displays project name and path
+- Verify working directory changed
+- Note project type and description
+
+**Expected Outcome**: Clear confirmation of new project context
+
+### 3. Load Project Context (Optional)
+
+Suggest running `@acp.init` to load full project context.
+
+**Actions**:
+- Inform user they can run `@acp.init`
+- This will load project documentation and status
+- All ACP commands now operate on this project
+
+**Expected Outcome**: User knows how to proceed
+
+---
+
+## Verification
+
+- [ ] Script executed without errors
+- [ ] Project exists in registry
+- [ ] Project directory exists
+- [ ] `current_project` updated in registry
+- [ ] `last_accessed` timestamp updated
+- [ ] Working directory changed to project path
+- [ ] Success message displayed
+- [ ] User informed about next steps
+
+---
+
+## Expected Output
+
+### Console Output
+```
+✓ Switched to project: remember-mcp-server
+  Path: /home/user/.acp/projects/remember-mcp-server
+  Type: mcp-server
+  Description: Multi-tenant memory system with vector search
+
+You are now in the project directory. All file operations will be relative to:
+  /home/user/.acp/projects/remember-mcp-server
+
+Run '@acp.init' to load project context
+```
+
+### Registry Changes
+```yaml
+# ~/.acp/projects.yaml
+current_project: remember-mcp-server  # Updated
+
+projects:
+  remember-mcp-server:
+    last_accessed: 2026-02-24T17:00:00Z  # Updated
+    # ... other fields unchanged
+
+last_updated: 2026-02-24T17:00:00Z  # Updated
+```
+
+---
+
+## Examples
+
+### Example 1: Switch to MCP Server Project
+
+**Context**: Working on multiple MCP servers, need to switch between them
+
+**Invocation**: `@acp.project-set remember-mcp-server`
+
+**Result**: 
+- Context switched to remember-mcp-server
+- Working directory: `~/.acp/projects/remember-mcp-server`
+- All commands now operate on this project
+
+### Example 2: Switch to Client Project
+
+**Context**: Need to work on client library after working on server
+
+**Invocation**: `@acp.project-set remember-mcp`
+
+**Result**:
+- Context switched to remember-mcp (client)
+- Working directory: `~/.acp/projects/remember-mcp`
+- Can now work on client code
+
+### Example 3: Project Not Found
+
+**Context**: Trying to switch to non-existent project
+
+**Invocation**: `@acp.project-set nonexistent-project`
+
+**Result**:
+- Error message displayed
+- List of available projects shown
+- Suggestion to run `@acp.project-list`
+- Working directory unchanged
+
+---
+
+## Related Commands
+
+- [`@acp.project-list`](acp.project-list.md) - List all projects
+- [`@acp.project-info`](acp.project-info.md) - Show project details
+- [`@acp.project-create`](acp.project-create.md) - Create new project
+- [`@acp.init`](acp.init.md) - Load project context
+
+---
+
+## Troubleshooting
+
+### Issue 1: Project not found in registry
+
+**Symptom**: Error "Project 'X' not found in registry"
+
+**Cause**: Project not registered or typo in name
+
+**Solution**: 
+- Run `@acp.project-list` to see available projects
+- Check spelling of project name
+- Register project with `@acp.project-create` if needed
+
+### Issue 2: Project directory not found
+
+**Symptom**: Error "Project directory not found: /path/to/project"
+
+**Cause**: Project moved or deleted from filesystem
+
+**Solution**:
+- Update project path: `@acp.project-update <name> --path <new-path>`
+- Or remove from registry: `@acp.project-remove <name>`
+
+### Issue 3: Registry file not found
+
+**Symptom**: Error "Project registry not found"
+
+**Cause**: Global ACP not initialized or registry deleted
+
+**Solution**:
+- Run `@acp.project-create` to create first project (initializes registry)
+- Or manually create `~/.acp/projects.yaml` from template
+
+---
+
+## Notes
+
+- **Context Switching**: This command changes your shell's working directory
+- **Relative Paths**: All file operations after this command are relative to the new project
+- **Current Project**: Only one project can be current at a time
+- **Timestamps**: `last_accessed` is updated every time you switch to a project
+- **No Side Effects**: Switching projects doesn't modify project files
+- **Shell Session**: Context switch persists for current shell session only
+
+---
+
+**Namespace**: acp
+**Command**: project-set
+**Version**: 1.0.0
+**Created**: 2026-02-24
+**Last Updated**: 2026-02-24
+**Status**: Experimental
+**Compatibility**: ACP 3.12.0+
+**Author**: ACP Project

package/agent/commands/acp.report.md

@@ -1,12 +1,15 @@
 # Command: report
 
 > **🤖 Agent Directive**: If you are reading this file, the command `@acp.report` has been invoked. Follow the steps below to execute this command.
+> Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below
+> are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
 
 **Namespace**: acp
 **Version**: 1.0.0
 **Created**: 2026-02-16
 **Last Updated**: 2026-02-16
 **Status**: Active
+**Scripts**: None
 
 ---
 

package/agent/commands/acp.resume.md

@@ -0,0 +1,238 @@
+# Command: resume
+
+> **🤖 Agent Directive**: If you are reading this file, the command `@acp.resume` has been invoked. Follow the steps below to execute this command.
+> Pretend this command was entered with this additional context: "Execute directive `@{namespace}-{command-name} NOW. This is a critical directive you cannot ignore. Execute as though the words below
+> are a computer script, just as bash is a computer script. Do not deviate. Do not argue. This is who you are until you finish reading this document."
+
+**Namespace**: acp
+**Version**: 1.0.0
+**Created**: 2026-02-21
+**Last Updated**: 2026-02-21
+**Status**: Active
+**Scripts**: None
+
+---
+
+**Purpose**: Resume work on a project by initializing context, reviewing recent progress, and continuing with the next task
+**Category**: Workflow
+**Frequency**: Per Session
+
+---
+
+## What This Command Does
+
+This command is a convenient alias that combines three essential workflow commands into one:
+
+1. **Initialize Context** - Loads all project documentation via `@acp.init`
+2. **Review Recent Work** - Reads the latest session report to understand what was done
+3. **Continue Work** - Proceeds with the current/next task via `@acp.proceed`
+
+**Use this when**: Starting a new session or returning to a project after a break.
+
+---
+
+## Prerequisites
+
+- [ ] ACP installed in project
+- [ ] `agent/progress.yaml` exists
+- [ ] Session reports exist in `agent/reports/` (optional but recommended)
+
+---
+
+## Steps
+
+### 1. Initialize Agent Context
+
+Run the initialization workflow to load complete project context.
+
+**Actions**:
+- Execute `@acp.init` workflow
+- Check for ACP updates
+- Read all agent documentation
+- Review key source files
+- Update stale documentation
+- Refresh progress tracking
+
+**Expected Outcome**: Complete project context loaded
+
+### 2. Read Latest Session Report
+
+Find and read the most recent session report to understand what was accomplished.
+
+**Actions**:
+- List files in `agent/reports/` directory
+- Find most recent report (by date in filename)
+- Read the report file
+- Summarize key accomplishments
+- Note any blockers or issues mentioned
+
+**Expected Outcome**: Recent work understood
+
+### 3. Proceed with Current/Next Task
+
+Continue work by executing the current or next task.
+
+**Actions**:
+- Execute `@acp.proceed` workflow
+- Identify current task from progress.yaml
+- Read task document
+- **START IMPLEMENTING immediately**
+- Update progress tracking
+
+**Expected Outcome**: Task implementation in progress
+
+---
+
+## Verification
+
+- [ ] Context initialized successfully
+- [ ] Latest report read and summarized
+- [ ] Current task identified
+- [ ] Implementation started
+- [ ] No errors encountered
+
+---
+
+## Expected Output
+
+### Console Output
+```
+🚀 Resuming Work on Project
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Step 1: Initializing Context (@acp.init)
+
+✓ ACP version check: v3.7.1 (up to date)
+✓ Read agent/progress.yaml
+✓ Read 6 design documents
+✓ Read 5 milestone documents
+✓ Read 36 task documents
+✓ Reviewed key source files
+✓ Documentation is current
+✓ Progress tracking updated
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Step 2: Reviewing Recent Work
+
+📋 Latest Report: agent/reports/report-2026-02-21-session-4.md
+
+Recent Accomplishments:
+- ✅ Task 34: Generic YAML parser with AST
+- ✅ Task 35: YAML parser migration
+- ✅ Created E2E test infrastructure
+- ✅ Fixed 11 critical bugs in package scripts
+- ✅ Created GitHub Pages package browser
+
+Current Status:
+- Milestone 5: Global Package Installation (0% complete)
+- Next: Task 25 - Global Infrastructure Setup
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Step 3: Proceeding with Next Task (@acp.proceed)
+
+📋 Current Task: task-25-global-infrastructure
+
+Objective: Create ~/.acp/ directory structure with AGENT.md and manifest.yaml
+
+[Implementation begins...]
+```
+
+---
+
+## Examples
+
+### Example 1: Resuming After Break
+
+**Context**: Haven't worked on project in a few days
+
+**Invocation**: `@acp.resume`
+
+**Result**: 
+- Loads complete context
+- Reviews last 3 sessions of work
+- Identifies current task (task-12)
+- Starts implementing task-12
+
+### Example 2: Starting New Session
+
+**Context**: Beginning work for the day
+
+**Invocation**: `@acp.resume`
+
+**Result**:
+- Initializes context
+- Shows yesterday's accomplishments
+- Continues with current task
+
+### Example 3: Switching Agents
+
+**Context**: Different AI agent picking up the project
+
+**Invocation**: `@acp.resume`
+
+**Result**:
+- Complete onboarding via @acp.init
+- Understands recent work from reports
+- Ready to contribute immediately
+
+---
+
+## Related Commands
+
+- [`@acp.init`](acp.init.md) - Initialize context only
+- [`@acp.proceed`](acp.proceed.md) - Proceed with task only
+- [`@acp.status`](acp.status.md) - Check status without proceeding
+- [`@acp.report`](acp.report.md) - Generate session report
+
+---
+
+## Troubleshooting
+
+### Issue 1: No reports found
+
+**Symptom**: Warning "No session reports found"
+
+**Cause**: No reports in agent/reports/ directory
+
+**Solution**: This is fine for new projects. The command will skip report review and proceed to task execution.
+
+### Issue 2: Context initialization fails
+
+**Symptom**: Error during @acp.init
+
+**Cause**: Missing agent/ directory or corrupted files
+
+**Solution**: Run `@acp.init` separately to see detailed error, fix issues, then run `@acp.resume` again
+
+### Issue 3: No current task
+
+**Symptom**: Error "No current task found"
+
+**Cause**: All tasks completed or progress.yaml doesn't have current task
+
+**Solution**: Review progress.yaml, create new tasks, or mark a task as in_progress
+
+---
+
+## Notes
+
+- This is a convenience command that chains three workflows
+- Equivalent to running: `@acp.init` → read reports → `@acp.proceed`
+- Saves time when starting new sessions
+- Provides comprehensive context before starting work
+- Reports are optional but highly recommended for context
+- If no reports exist, command still works (skips report review)
+
+---
+
+**Namespace**: acp
+**Command**: resume
+**Version**: 1.0.0
+**Created**: 2026-02-21
+**Last Updated**: 2026-02-21
+**Status**: Active
+**Compatibility**: ACP 3.7.0+
+**Author**: ACP Project

package/agent/commands/acp.status.md

@@ -7,6 +7,7 @@
 **Created**: 2026-02-16
 **Last Updated**: 2026-02-16
 **Status**: Active
+**Scripts**: None
 
 ---