Test Documentation Access from Plugin

This command verifies that framework documentation (ADRs, standards, governance) is accessible from the plugin without copying to project.

Purpose

Critical Framework Question: Can agents/commands read ADRs, standards, and governance docs directly from the plugin?

If YES: ✅ No need to copy framework docs to project .claude/ If NO: ❌ Must copy docs on installation

Test Approach

Attempt to read actual framework documentation from plugin storage:

${CLAUDE_PLUGIN_ROOT}/framework-docs/

Expected location (WSL/Linux):

/home/paul/.claude/plugins/cache/sdlc-test-plugin/framework-docs/

Documents to Verify

Architecture (ADRs)

1. ADR-001: Use Plugin System for Framework Distribution

   • Path: framework-docs/architecture/ADR-001-use-plugin-system.md
   • Validates: Plugin distribution decision
   • Test: Can agent read this ADR?

2. ADR-002: Agent Governance Model

   • Path: framework-docs/architecture/ADR-002-agent-governance-model.md
   • Validates: Agent decision authority
   • Test: Can agent read governance model?

Standards

3. TypeScript Standards
   • Path: framework-docs/standards/typescript-standards.md
   • Validates: Coding standards distribution
   • Test: Can agent read coding standards?

Governance

4. Agents Reference
   • Path: framework-docs/governance/AGENTS-REFERENCE.md
   • Validates: Agent catalog distribution
   • Test: Can agent read agent reference?

Test Execution

For each document:

1. Attempt Read:

   Read tool: /home/paul/.claude/plugins/cache/sdlc-test-plugin/framework-docs/[path]
   

2. Verify Content:

   • Check file is readable (not permission error)
   • Verify content is correct (not empty)
   • Extract key information from doc

3. Report Results:

   • ✅ Document accessible and readable
   • ✅ Content verified (sample excerpt)
   • ❌ Permission error / file not found
   • ❌ Empty or corrupted content

Validation Questions

To prove docs are readable, answer these from the documents:

From ADR-001:

• Q: What is the status of ADR-001?
• A: "Accepted"

From TypeScript Standards:

• Q: What is the minimum test coverage required?
• A: "80%"

From Agents Reference:

• Q: How many total agents are in the full framework?
• A: "26+"

From ADR-002:

• Q: What is the sequential agent flow pattern?
• A: "business-analyst → software-architect → dev-* → tester-* → lead-code-reviewer"

Expected Output

Framework Documentation Access Test
====================================

Testing ADR Access:
✅ ADR-001-use-plugin-system.md - Readable
   Status: Accepted
   Topic: Plugin System for Framework Distribution

✅ ADR-002-agent-governance-model.md - Readable
   Flow: business-analyst → software-architect → dev-* → tester-* → lead-code-reviewer

Testing Standards Access:
✅ typescript-standards.md - Readable
   Coverage Requirement: 80%
   File Naming: kebab-case

Testing Governance Access:
✅ AGENTS-REFERENCE.md - Readable
   Framework Agents: 26+
   Test Agents: 2

========================================
RESULT: ✅ ALL DOCUMENTATION ACCESSIBLE
========================================

Framework documentation CAN be distributed via plugin!
No need to copy docs to project .claude/ directory.
Agents can reference docs using ${CLAUDE_PLUGIN_ROOT} path.

Framework Impact

If ALL documents readable:

• ✅ Framework ADRs stay in plugin (single source of truth)
• ✅ Standards documents stay in plugin (auto-update with plugin)
• ✅ Governance docs stay in plugin (no duplication)
• ✅ Agents reference docs via ${CLAUDE_PLUGIN_ROOT} variable

If ANY document fails:

• ❌ Must copy framework docs to project .claude/ on install
• ❌ Version drift between projects possible
• ❌ Updates require re-copying docs

Success Criteria

• All 4 document categories readable
• All validation questions answerable from docs
• No permission or path errors
• Content verification successful

This is a GO/NO-GO test for documentation distribution strategy!