sdlc-test-plugin

Claude Code Plugin Test Harness

Comprehensive SDLC test plugin to validate Claude Code plugin system capabilities before converting the full framework.

Purpose

This plugin validates ALL critical plugin system features:

• ✅ Multiple agents loading and invocation
• ✅ Slash command distribution and execution
• ✅ Hook installation and triggering
• ✅ File system access (.claude folder permissions)
• ✅ Plugin updates and versioning
• ✅ Private marketplace integration

Structure

claude-plugin-test/
├── .claude-plugin/
│   └── plugin.json              # Plugin manifest (v0.2.0)
├── agents/
│   ├── test-agent.md            # Basic agent for status reporting
│   └── test-writer-agent.md     # Agent testing Write tool & file access
├── commands/
│   └── test-command.md          # Test slash command (/test-command)
├── hooks/
│   └── test-write-hook.json     # Hook to log Write tool usage
├── LEARNINGS.md                 # Comprehensive discoveries
└── README.md                    # This file

Installation & Testing

1. Add Private Marketplace

# Add local marketplace
claude plugins marketplace add E:\Development\claude-plugin-marketplace

# Or if using Git URL after pushing to GitHub:
# claude plugins marketplace add https://github.com/your-org/claude-plugin-marketplace

2. Install Test Plugin

# List available plugins
claude plugins list

# Install the test plugin
claude plugins install sdlc-test-plugin

# Verify installation
claude plugins info sdlc-test-plugin

3. Test Components (In Claude Code)

Test Multiple Agents:

"Use the test-agent to check plugin status, then use test-writer-agent to validate file creation"

Test Slash Command:

/test-command --verbose

Test Hook (automatic - triggers on Write tool usage):

# Hook should create plugin-hook-log.txt when any Write tool is used
"Create a test file using Write tool and check if the hook logged it"

Test .claude Folder Access:

"Use test-writer-agent to try writing to .claude/extensions/ folder"

What We're Testing

Phase 1: Core Plugin Mechanics ✅

• ✅ Plugin manifest format (plugin.json)
• ✅ Plugin installation from marketplace
• ✅ Single agent loading and invocation
• ✅ Agent tool access (Read/Write/Grep/Glob)
• ✅ DISCOVERY: Plugin agents are leaf nodes (no Task tool)

Phase 2: Comprehensive Features 🔄

• 🧪 Multiple agents in single plugin
• 🧪 Slash command loading and execution
• 🧪 Hook installation and triggering
• 🧪 File system permissions (.claude folder access)
• 🧪 Plugin updates (version 0.1.0 → 0.2.0)

Phase 3: Framework-Critical Features (v0.3.0) 🔄

• 🧪 .claude folder write access - CRITICAL GO/NO-GO test
• 🧪 Script wrapper pattern - Validate distribution of 85 scripts
• ⏳ Private repository authentication testing
• ⏳ Hook installation mechanism research
• ⏳ MCP server integration (future)
• ⏳ Custom configuration file generation (future)
• ⏳ User extension preservation during updates (future)

Phase 3 Testing Instructions

Test 1: .claude Folder Access (CRITICAL! 🚨)

This test determines if plugin-based framework distribution is viable.

Use test-writer-agent to test .claude folder write access

What it tests:

• Can plugin agents write to .claude/extensions/?
• Can plugin agents create .claude/ subdirectories?
• What are the file system permission boundaries?

Framework impact:

• MUST work for: .claude/.env.sdlc generation
• MUST work for: User extension preservation
• MUST work for: Configuration management

Test 2: Script Wrapper Pattern

Tests if 85 framework scripts can be distributed via plugin.

/test-script-wrapper

What it tests:

• Can plugins include /scripts/ directory?
• Can commands invoke plugin scripts?
• Do scripts have project environment access?

Framework impact:

• If successful: All 85 scripts can be distributed
• If blocked: Need alternative (MCP, inline, or copy-on-install)

Test 3: Private Repository Authentication

Make one or both repos private and test:

• Does marketplace access private repos?
• Does plugin installation work with private sources?
• What authentication mechanism is required?

Framework impact:

• Required for production use
• Client work requires private repositories
• Need to document authentication setup

Learnings

Document discoveries in LEARNINGS.md as we test.

Related Issues

• Issue #226: Build Micro SDLC Plugin Test Harness
• Epic #210: Evaluate Claude Code Plugin System for Framework Distribution