@prmichaelsen/remember-mcp 2.3.0 → 2.3.1

package/AGENT.md

@@ -1,7 +1,7 @@
 # Agent Context Protocol (ACP)
 
 **Also Known As**: The Agent Directory Pattern
-**Version**: 1.1.0
+**Version**: 1.2.0
 **Created**: 2026-02-11
 **Status**: Production Pattern
 
@@ -81,6 +81,14 @@ ACP solves these by:
 project-root/
 ├── AGENT.md                        # This file - ACP documentation
 ├── agent/                          # Agent directory (ACP structure)
+│   ├── commands/                   # Command system
+│   │   ├── .gitkeep
+│   │   ├── command.template.md     # Command template
+│   │   ├── acp.init.md             # @acp-init
+│   │   ├── acp.proceed.md          # @acp-proceed
+│   │   ├── acp.status.md           # @acp-status
+│   │   └── ...                     # More commands
+│   │
 │   ├── design/                     # Design documents
 │   │   ├── .gitkeep
 │   │   ├── requirements.md         # Core requirements
@@ -551,6 +559,91 @@ The Agent Pattern represents a **paradigm shift** in how we approach AI-assisted
 
 ---
 
+## ACP Commands
+
+ACP supports a command system for common workflows. Commands are file-based triggers that provide standardized, discoverable interfaces for ACP operations.
+
+### What are ACP Commands?
+
+Commands are markdown files in [`agent/commands/`](agent/commands/) that contain step-by-step instructions for AI agents. Instead of typing long prompts like "AGENT.md: Initialize", you can reference command files like `@acp.init` to trigger specific workflows.
+
+**Benefits**:
+- **Discoverable**: Browse [`agent/commands/`](agent/commands/) to see all available commands
+- **Consistent**: All commands follow the same structure
+- **Extensible**: Create custom commands for your project
+- **Self-Documenting**: Each command file contains complete documentation
+- **Autocomplete-Friendly**: Type `@acp.` to see all ACP commands
+
+### Core Commands
+
+Core ACP commands use the `acp.` prefix and are available in [`agent/commands/`](agent/commands/):
+
+- **[`@acp.init`](agent/commands/acp.init.md)** - Initialize agent context (replaces "AGENT.md: Initialize")
+- **[`@acp.proceed`](agent/commands/acp.proceed.md)** - Continue with next task (replaces "AGENT.md: Proceed")
+- **[`@acp.status`](agent/commands/acp.status.md)** - Display project status
+- **[`@acp.version-check`](agent/commands/acp.version-check.md)** - Show current ACP version
+- **[`@acp.version-check-for-updates`](agent/commands/acp.version-check-for-updates.md)** - Check for ACP updates
+- **[`@acp.version-update`](agent/commands/acp.version-update.md)** - Update ACP to latest version
+
+### Command Invocation
+
+Commands are invoked using the `@` syntax with dot notation:
+
+```
+@acp.init                    → agent/commands/acp.init.md
+@acp.proceed                 → agent/commands/acp.proceed.md
+@acp.status                  → agent/commands/acp.status.md
+@deploy.production           → agent/commands/deploy.production.md
+```
+
+**Format**: `@{namespace}.{action}` resolves to `agent/commands/{namespace}.{action}.md`
+
+### Creating Custom Commands
+
+To create custom commands for your project:
+
+1. **Choose a namespace** (e.g., `deploy`, `test`, `custom`)
+   - ⚠️ The `acp` namespace is reserved for core commands
+   - Use descriptive, single-word namespaces
+
+2. **Copy the command template**:
+   ```bash
+   cp agent/commands/command.template.md agent/commands/{namespace}.{action}.md
+   ```
+
+3. **Fill in the template sections**:
+   - Purpose and description
+   - Prerequisites
+   - Step-by-step instructions
+   - Verification checklist
+   - Examples and troubleshooting
+
+4. **Invoke your command**: `@{namespace}.{action}`
+
+**Example**: Creating a deployment command:
+```bash
+# Create the command file
+cp agent/commands/command.template.md agent/commands/deploy.production.md
+
+# Edit the file with your deployment steps
+# ...
+
+# Invoke it
+@deploy.production
+```
+
+### Command Template
+
+See [`agent/commands/command.template.md`](agent/commands/command.template.md) for the complete command template with all sections and examples.
+
+### Installing Third-Party Commands
+
+Use `@acp.install` to install command packages from git repositories (available in future release).
+
+**Security Note**: Third-party commands can instruct agents to modify files and execute scripts. Always review command files before installation.
+
+---
+
 ## Sample Prompts for Using ACP
 
 ### Initialize Prompt
@@ -882,7 +975,7 @@ This repository is actively maintained with improvements to the ACP methodology
 ./agent/scripts/update.sh
 
 # Or download and run directly
-curl -fsSL https://raw.githubusercontent.com/prmichaelsen/agent-context-protocol/mainlin./agent/scripts/update.sh | bash
+curl -fsSL https://raw.githubusercontent.com/prmichaelsen/agent-context-protocol/mainline/agent/scripts/update.sh | bash
 ```
 
 The update script will:

package/agent/commands/acp.package-install.md

@@ -0,0 +1,347 @@
+# Command: package-install
+
+> **🤖 Agent Directive**: If you are reading this file, the command `@acp.package-install` has been invoked. Follow the steps below to execute this command.
+
+**Namespace**: acp
+**Version**: 1.0.0
+**Created**: 2026-02-16
+**Last Updated**: 2026-02-16
+**Status**: Active
+
+---
+
+**Purpose**: Install third-party command packages from git repositories using the package-install script
+**Category**: Maintenance
+**Frequency**: As Needed
+
+---
+
+## What This Command Does
+
+This command installs third-party ACP packages from git repositories by running the `agent/scripts/package-install.sh` script. The script clones the repository and installs files from the `agent/` directory, including commands, patterns, and design documents.
+
+Use this command when you want to add community-created commands and patterns, install organization-specific ACP content, or share reusable components across multiple projects. It enables extending ACP with custom functionality, patterns, and documentation.
+
+⚠️ **SECURITY WARNING**: Third-party packages can instruct agents to modify files and execute scripts. Always review package contents before installation. You assume all risk when installing third-party packages.
+
+---
+
+## Prerequisites
+
+- [ ] ACP installed in project
+- [ ] Git installed and available
+- [ ] Internet connection available
+- [ ] `agent/scripts/package-install.sh` exists
+- [ ] You trust the source of the commands
+- [ ] You have reviewed the command repository
+
+---
+
+## Steps
+
+### 1. Run Package Install Script
+
+Execute the package installation script with the repository URL.
+
+**Actions**:
+- Verify `./agent/scripts/package-install.sh` exists
+- Run the script with repository URL as argument:
+  ```bash
+  # Interactive mode (asks for confirmation)
+  ./agent/scripts/package-install.sh <repository-url>
+  
+  # Auto-confirm mode (skips prompts)
+  ./agent/scripts/package-install.sh -y <repository-url>
+  ```
+- The script will:
+  - Validate the repository URL
+  - Clone the repository to a temporary location
+  - Scan agent/ directory for installable files (commands, patterns, design)
+  - Validate command files (agent directive, namespace check)
+  - Check for naming conflicts
+  - Ask for confirmation (unless -y flag used)
+  - Copy files to respective agent/ directories
+  - Clean up temporary files
+  - Report what was installed
+
+**Expected Outcome**: Script completes successfully and files are installed
+
+### 2. Review Installed Files
+
+Verify the files were installed correctly.
+
+**Actions**:
+- List files in `agent/commands/` to see new commands
+- List files in `agent/patterns/` to see new patterns
+- List files in `agent/design/` to see new designs
+- Read the installed files
+- Verify commands have agent directives
+- Check namespace is not `acp` (reserved for commands)
+- Ensure no malicious content
+
+**Expected Outcome**: Files verified safe and functional
+
+### 3. Test Installed Commands
+
+Try invoking one of the installed commands (if any).
+
+**Actions**:
+- Choose a simple command to test
+- Invoke it using `@{namespace}.{action}` syntax
+- Verify it works as expected
+- Check for any errors
+
+**Expected Outcome**: Commands work correctly
+
+### 4. Document Installation
+
+Update progress tracking with installation notes.
+
+**Actions**:
+- Add note to `agent/progress.yaml` about installed package
+- Document which package was installed
+- Note installation date
+- List installed files (commands, patterns, designs)
+
+**Expected Outcome**: Installation tracked in progress
+
+---
+
+## Verification
+
+- [ ] package-install.sh script exists
+- [ ] Script executed successfully
+- [ ] Files installed to appropriate agent/ directories
+- [ ] Installed commands reviewed for safety (if any)
+- [ ] Installed patterns reviewed (if any)
+- [ ] Installed designs reviewed (if any)
+- [ ] Commands tested and working (if any)
+- [ ] Installation documented in progress.yaml
+- [ ] No errors during installation
+
+---
+
+## Expected Output
+
+### Files Modified
+- `agent/commands/*.md` - Installed command files (if any)
+- `agent/patterns/*.md` - Installed pattern files (if any)
+- `agent/design/*.md` - Installed design files (if any)
+
+### Console Output
+```
+📦 ACP Package Installer
+========================================
+
+Repository: https://github.com/example/fullstack-package.git
+
+Cloning repository...
+✓ Repository cloned
+
+Scanning for installable files...
+
+📁 commands/ (3 file(s))
+  ✓ deploy.production.md
+  ✓ deploy.staging.md
+  ⚠  deploy.rollback.md (will overwrite existing)
+
+📁 patterns/ (2 file(s))
+  ✓ api-service.md
+  ✓ error-handling.md
+
+📁 design/ (1 file(s))
+  ✓ deployment-strategy.md
+
+Ready to install 6 file(s)
+
+Proceed with installation? (y/N) y
+
+Installing files...
+  ✓ Installed commands/deploy.production.md
+  ✓ Installed commands/deploy.staging.md
+  ✓ Installed commands/deploy.rollback.md
+  ✓ Installed patterns/api-service.md
+  ✓ Installed patterns/error-handling.md
+  ✓ Installed design/deployment-strategy.md
+
+✅ Installation complete!
+
+Installed 6 file(s) from:
+  https://github.com/example/fullstack-package.git
+
+Installed commands:
+  - @deploy.production
+  - @deploy.staging
+  - @deploy.rollback
+
+⚠️  Security Reminder:
+Review installed files before using them.
+Third-party files can instruct agents to modify files and execute scripts.
+
+Next steps:
+  1. Review installed files in agent/ directories
+  2. Test installed commands
+  3. Update progress.yaml with installation notes
+```
+
+### Status Update
+- Commands installed
+- Installation documented
+- Commands ready to use
+
+---
+
+## Examples
+
+### Example 1: Installing Deployment Commands
+
+**Context**: Want to add deployment commands from community
+
+**Invocation**: `@acp.package-install https://github.com/example/acp-deploy-package.git`
+
+**Result**: Script clones repo, installs 3 commands to agent/commands/, now can use @deploy.production
+
+### Example 2: Installing Patterns Package
+
+**Context**: Want to add TypeScript patterns from organization
+
+**Invocation**: `@acp.package-install https://github.com/myorg/typescript-patterns.git`
+
+**Result**: Script installs 5 pattern files to agent/patterns/, now have reusable TypeScript patterns
+
+### Example 3: Installing Complete Package
+
+**Context**: Installing package with commands, patterns, and designs
+
+**Invocation**: `@acp.package-install https://github.com/example/fullstack-package.git`
+
+**Result**: Script installs 3 commands, 4 patterns, 2 design docs across agent/ directories
+
+### Example 4: Installing with Conflicts
+
+**Context**: Installing package that conflicts with existing files
+
+**Invocation**: `@acp.package-install https://github.com/example/package.git`
+
+**Result**: Script detects conflicts, asks for confirmation, overwrites if approved
+
+---
+
+## Related Commands
+
+- [`@acp.validate`](acp.validate.md) - Validate installed commands
+- [`@acp.version-update`](acp.version-update.md) - Update core ACP commands
+- [`@acp.status`](acp.status.md) - View project status
+
+---
+
+## Troubleshooting
+
+### Issue 1: Git clone fails
+
+**Symptom**: Cannot clone repository
+
+**Cause**: Invalid URL, no internet, or private repository
+
+**Solution**: Verify URL is correct, check internet connection, ensure repository is public or you have access
+
+### Issue 2: No commands found
+
+**Symptom**: Repository cloned but no commands found
+
+**Cause**: Commands not in expected location or wrong structure
+
+**Solution**: Check repository structure, look for commands/ directory, verify files are .md format
+
+### Issue 3: Validation fails
+
+**Symptom**: Commands fail validation
+
+**Cause**: Commands don't follow ACP structure
+
+**Solution**: Review command files, ensure they have agent directive and required sections, contact command author
+
+### Issue 4: Namespace conflict
+
+**Symptom**: Command uses reserved namespace
+
+**Cause**: Command tries to use 'acp' namespace
+
+**Solution**: Cannot install - 'acp' namespace is reserved for core commands, contact command author to change namespace
+
+---
+
+## Security Considerations
+
+### ⚠️ CRITICAL SECURITY WARNING
+
+**Third-party packages can contain:**
+- **Commands** that instruct agents to modify files and execute scripts
+- **Patterns** that guide code implementation decisions
+- **Designs** that influence architecture and technical decisions
+
+**Third-party commands can:**
+- Modify any files in your project
+- Execute shell commands
+- Make network requests
+- Access environment variables
+- Read sensitive data
+
+**YOU ASSUME ALL RISK when installing third-party packages.**
+
+### Security Best Practices
+
+**Before Installing**:
+1. Review the repository and command files
+2. Check the author's reputation
+3. Read what each command does
+4. Verify no malicious content
+5. Test in a non-production environment first
+
+**After Installing**:
+1. Review installed command files
+2. Test commands in safe environment
+3. Monitor command behavior
+4. Remove if suspicious activity
+5. Keep installation records
+
+### File Access
+- **Reads**: Repository files, existing files in agent/ directories
+- **Writes**: `agent/commands/*.md`, `agent/patterns/*.md`, `agent/design/*.md`
+- **Executes**: `git clone` command, `./agent/scripts/package-install.sh`
+
+### Network Access
+- **APIs**: None directly
+- **Repositories**: Clones from specified git repository
+
+### Sensitive Data
+- **Secrets**: Does not access secrets
+- **Credentials**: May use git credentials for private repos
+
+---
+
+## Notes
+
+- Installs from all agent/ directories: commands, patterns, design
+- Only install packages from trusted sources
+- Review all files before installation (commands, patterns, designs)
+- Test in safe environment first
+- Keep record of installed packages
+- Update installed packages periodically
+- Remove unused files
+- Report security issues to package authors
+- Consider forking repositories for stability
+- Pin to specific versions/commits for reproducibility
+- Use `-y` flag for automated/scripted installations
+- Patterns and designs influence agent behavior just like commands
+
+---
+
+**Namespace**: acp
+**Command**: package-install
+**Version**: 1.0.0
+**Created**: 2026-02-16
+**Last Updated**: 2026-02-16
+**Status**: Active
+**Compatibility**: ACP 1.1.0+
+**Author**: ACP Project