frankgpt/LEGACY.md
nathan f009b01af9 docs(v6): complete Phase 5 with README and legacy file documentation
Phase 5 Complete: Final Documentation and Legacy Mapping

Documentation Created:
- v6/README.md: Comprehensive 400+ line quick start guide
  * Quick start examples (4 loading options)
  * Architecture overview with 3-layer diagram
  * All 6 specialties documented with commands and use cases
  * VS Code integration methods (3 options)
  * Usage examples for common scenarios
  * Custom specialty creation guide
  * Migration guide from v4/v5
  * Troubleshooting section
  * Version history and roadmap

- LEGACY.md: Legacy file mapping and recommendations
  * Organized vs superseded vs deprecated files
  * v4/v5 to v6 migration matrix
  * Archive cleanup options (minimal, archive folder, aggressive)
  * Decision: Keep prompts/ at root (templates, not core)
  * Preservation rationale for each legacy artifact

Frank v6 Now Complete:
-  23 files in v6/ structure (1 core, 7 skills, 6 specialties, 6 knowledge, 3 docs)
-  ~6,800 lines of modular, portable content
-  Zero environment coupling
-  Multi-specialty composition support
-  Comprehensive documentation (README, ARCHITECTURE, copilot-instructions)
-  Custom specialty template for extensibility
-  All phases 1-5 complete

Design Achievements:
- Portability: Pick up v6/ folder and go - works anywhere
- Modularity: Load only what you need (core, skills, specialties)
- Composition: Combine multiple specialties seamlessly
- Documentation: 1000+ lines across README + ARCHITECTURE
- Extensibility: Template enables custom domain additions

Ref: Session plan completed in /memories/session/plan.md
2026-04-19 14:22:44 -04:00

5.8 KiB

Legacy Files - Frank v4/v5 Artifacts

This document identifies legacy files from previous Frank versions and their v6 equivalents or migration status.


Preserved & Organized

Frank/docx/

Status: Organized (moved from root to subdirectory in Phase 1)
Contents: DOCX exports of source markdown files
Action: Keep as archive - useful for Word-based workflows
v6 Equivalent: Source files now in v6/ structure

Frank/markdown/

Status: Preserved
Contents: Original v5 source markdown files
Action: Keep as reference - shows evolution to v6
v6 Equivalent:

  • Frank Meadows.agent.md → Extracted to v6/Frank.core.agent.md + multiple specialties
  • style.*.md → Copied to v6/skills/

🔄 Superseded Files (Consider Archiving)

copilot-instructions.md (root)

Status: 🔄 Superseded by v6/copilot-instructions.md
Version: v4/v5 artifact
v6 Equivalent: v6/copilot-instructions.md (fully rewritten for modular architecture)
Recommendation: Rename to copilot-instructions.v5.md or move to archive/ folder

agents/FrankGPT.consolidated-instructions.md

Status: 🔄 Superseded by v6 modular system
Version: v5 consolidated monolith
v6 Equivalent: Use v6/Frank.core.agent.md + relevant specialties
Recommendation: Rename to FrankGPT.consolidated-instructions.v5.md for reference

instructions/core.instructions.md

Status: 🔄 Superseded by v6 core
Version: v4 IT-focused core logic
v6 Equivalent:

  • General personality → v6/Frank.core.agent.md
  • IT-specific logic → v6/specialties/specialty.itil.instructions.md
    Recommendation: Keep for historical reference, note superseded status

instructions/style.markdown.instructions.md

Status: 🔄 Duplicate (canonical version in v6)
Version: v4/v5
v6 Equivalent: v6/skills/style.markdown.instructions.md
Recommendation: Delete or mark as deprecated (100% duplicate)


📦 Kept As-Is

agents/Data Analyst.agent.md

Status: 📦 Extracted to specialty
Version: v4/v5
v6 Equivalent: v6/specialties/specialty.data-analysis.instructions.md
Recommendation: Keep original for comparison, clearly superseded by v6

agents/SCCM Tutor.agent.md

Status: 📦 Extracted to specialty
Version: v4/v5
v6 Equivalent: v6/specialties/specialty.sccm.instructions.md
Recommendation: Keep original for comparison, clearly superseded by v6

knowledge/

Status: Copied to v6
Contents: Example files for reasoning techniques
v6 Equivalent: v6/knowledge/ (identical copies)
Recommendation: Keep both - root for reference, v6 for active use

prompts/

Status: Kept at root
Contents: Prompt templates (content2template, create-commit, md2html, etc.)
v6 Status: Independent templates, not core to Frank architecture
Recommendation: Keep at root - these are utilities, not agent definitions
Future Option: Could create specialty.prompt-templates.instructions.md if desired


Option A: Minimal (Safe)

Just add deprecation notices to superseded files:

# Add header to superseded files
echo "⚠️ DEPRECATED: This file is superseded by v6/copilot-instructions.md" | cat - copilot-instructions.md > temp && mv temp copilot-instructions.md

Option B: Archive Folder

Create archive/ folder for v4/v5 artifacts:

mkdir archive/
mv copilot-instructions.md archive/copilot-instructions.v5.md
mv agents/FrankGPT.consolidated-instructions.md archive/
mv instructions/core.instructions.md archive/core.instructions.v4.md
# Keep originals in _Frank_/markdown and agents/ for reference

Option C: Aggressive Cleanup

Delete duplicates, keep only v6 as canonical:

# Delete 100% duplicates
rm instructions/style.markdown.instructions.md

# Archive superseded files
mkdir archive/
mv copilot-instructions.md archive/
mv agents/FrankGPT.consolidated-instructions.md archive/
mv instructions/core.instructions.md archive/

# Keep _Frank_/, agents/, knowledge/, prompts/ as-is for reference

📊 Version Mapping

v4/v5 File Purpose v6 Equivalent
Frank Meadows.agent.md Monolithic agent Frank.core.agent.md + specialties
Data Analyst.agent.md Data analysis specialty.data-analysis.instructions.md
SCCM Tutor.agent.md Endpoint mgmt specialty.sccm.instructions.md
FrankGPT.consolidated.md v5 monolith Frank.core + specialties composition
core.instructions.md v4 core Frank.core + specialty.itil
copilot-instructions.md VS Code integration v6/copilot-instructions.md
instructions/style.*.md Style guides v6/skills/style.*.md
knowledge/*.md Examples v6/knowledge/*.md

🎯 Migration Decision Matrix

Keep if:

  • Original source for v6 content (Frank/markdown/)
  • Unique content not in v6 (prompts/)
  • Archive/reference value (agents/ originals)

Archive if:

  • 📦 Superseded by v6 but has historical value
  • 📦 Might be useful for rollback scenarios
  • 📦 Comparison/migration reference

Delete if:

  • 🗑️ 100% duplicate of v6 content
  • 🗑️ No historical value
  • 🗑️ Confusing to keep both versions

💡 Recommendation

Suggested approach: Option B (Archive Folder)

  1. Create archive/ folder
  2. Move superseded root files: copilot-instructions.md, agents/FrankGPT.consolidated-instructions.md
  3. Delete 100% duplicate: instructions/style.markdown.instructions.md
  4. Keep everything else as-is for reference
  5. Add note to root README pointing to v6/

This preserves history while making it clear v6 is canonical.


Last Updated: Phase 5 - April 2026
For Questions: See v6/ARCHITECTURE.md for v6 design philosophy