Test Script Wrapper Command

This command tests the script wrapper pattern - critical for distributing the framework's 85 scripts via plugin system.

Purpose

Validate that:

• Plugins can include /scripts/ directory
• Commands can invoke plugin scripts via Bash tool
• Scripts have access to project environment
• Output from scripts is captured correctly

Pattern Being Tested

Plugin Structure:
  /scripts/test-script.sh         ← Script file in plugin
  /commands/test-script-wrapper.md ← Command that invokes script

Execution Flow:
  User: /test-script-wrapper
    → Claude Code loads command from plugin
      → Command uses Bash tool to execute script
        → Script runs in project context
          → Results returned to user

Execution

When this command is invoked:

1. Locate Script: Find the plugin script (may need to determine plugin installation path)
2. Execute Script: Use Bash tool to run scripts/test-script.sh
3. Capture Output: Display script output to user
4. Verify Results: Check that plugin-script-test-output.txt was created

Implementation

Since plugin scripts are bundled with the plugin, we need to execute the script. The challenge is determining the script's location within the plugin installation.

Approach 1 - Relative Path (if commands run from plugin root):

bash ./scripts/test-script.sh

Approach 2 - Project Copy (if scripts must be copied to project):

# Command first copies script to project, then executes
cp [plugin-path]/scripts/test-script.sh .claude/scripts/
bash .claude/scripts/test-script.sh

Approach 3 - Inline Execution (embed script logic in command):

# Execute script logic directly in command
bash -c "echo 'Script test'; date > output.txt"

For this test, try Approach 1 first. If that fails due to path issues, document the error and try alternative approaches.

Expected Output

===============================================
PLUGIN SCRIPT EXECUTION TEST
===============================================

Script: test-script.sh
Plugin: sdlc-test-plugin
Execution time: [timestamp]
Working directory: [project-path]

✅ SUCCESS: Plugin script executed successfully

This validates that:
- Scripts can be included in plugin packages
- Scripts can be invoked from plugin commands
- Scripts have access to project environment

Framework implication:
All 85 SDLC framework scripts can be distributed
via plugin and invoked through command wrappers

===============================================

Created: plugin-script-test-output.txt

Success Criteria

• Command executes without errors
• Script runs and produces output
• Output file plugin-script-test-output.txt is created
• Script has access to project working directory

Framework Impact

If successful, this proves:

• ✅ All 85 framework scripts can be distributed via plugin
• ✅ Commands can wrap scripts for user-friendly invocation
• ✅ Scripts maintain access to project environment
• ✅ No need for manual script installation

If unsuccessful, we need alternative approach:

• Installation hook that copies scripts to project
• MCP server pattern for script execution
• Embedded script logic in command markdown files