Install Framework Files

CRITICAL TEST + LIMITATION DISCOVERY: This command tests framework file installation and highlights a plugin system gap.

⚠️ Plugin System Limitation Discovered

Expected: Framework files auto-install when plugin is installed Reality: No installHook or postInstall support in plugin manifest Workaround: Manual command execution required

This is a test to validate:

1. Can we copy files from plugin to project?
2. Should plugins support install lifecycle hooks?
3. Is there a better pattern we're missing?

Purpose

Tests the complete framework distribution workflow:

1. Read pre-written files from plugin's framework-files/ directory
2. Install them to project's .claude/ directory
3. Preserve directory structure
4. Report installation results

What Gets Installed

From plugin framework-files/ to project .claude/:

framework-files/CLAUDE.md → .claude/CLAUDE.md
framework-files/governance/*.md → .claude/governance/*.md
framework-files/docs/standards/*.md → .claude/docs/standards/*.md
framework-files/docs/architecture/*.md → .claude/docs/architecture/*.md
framework-files/templates/*.md → .claude/templates/*.md

Files Being Installed

1. CLAUDE.md - Framework overview
2. governance/AGENTS.md - Agent list and descriptions
3. governance/AGENT-GOVERNANCE.md - Decision authority matrix
4. docs/standards/code-standards.md - Coding standards
5. docs/architecture/adr-template.md - ADR template
6. templates/issue-template.md - GitHub issue template

Arguments

• --force: Overwrite existing files
• --dry-run: Show what would be installed without actually writing files

Execution

When invoked, this command will:

1. Create Directory Structure:

   mkdir -p .claude/{governance,docs/{standards,architecture},templates}
   

2. Copy Framework Files:

   • Read from: /home/paul/.claude/plugins/cache/sdlc-test-plugin/framework-files/
   • Write to: .claude/ in project directory

3. Installation Steps:

   • Create necessary directories
   • Read each framework file from plugin
   • Write to corresponding location in project
   • Report success/failure for each file

4. Generate Report:

   • List all installed files
   • Report any errors or conflicts
   • Show installation summary

Expected Output

Framework Installation Starting...
==================================

Creating directories:
✅ .claude/governance/
✅ .claude/docs/standards/
✅ .claude/docs/architecture/
✅ .claude/templates/

Installing framework files:
✅ CLAUDE.md
✅ governance/AGENTS.md
✅ governance/AGENT-GOVERNANCE.md
✅ docs/standards/code-standards.md
✅ docs/architecture/adr-template.md
✅ templates/issue-template.md

Installation Summary:
====================
Total files: 6
Successful: 6
Failed: 0
Skipped: 0

Framework installation COMPLETE!
Report saved to: framework-installation-report.txt

Test Validation

If successful:

• ✅ Pre-written framework content can be distributed via plugin
• ✅ Installation is automated (no manual file copying)
• ✅ Directory structure is preserved
• ✅ Framework updates can be distributed via plugin updates

If blocked:

• ❌ Files must be manually copied
• ❌ Plugin distribution not viable for content-heavy frameworks
• ❌ Need alternative installation method

Framework Impact

This is the MOST CRITICAL test for framework viability!

If this works, the entire SDLC framework (595+ assets) can be:

• Distributed via plugin
• Installed with a single command
• Updated via claude plugins update
• Versioned and managed through plugin system

Success Criteria

• All 6 framework files installed successfully
• Directory structure matches plugin structure
• Files are readable and contain correct content
• No permission or path errors
• Installation report generated

This test determines if plugin-based framework distribution is production-ready!