Update specialty.home-cooking.instructions.md to define local-profile precedence and keep embedded YAML as reference examples
Add .gitignore rule to prevent local home-cooking profile YAML files from being committed
Align home-cooking specialty behavior with the current session intent: move sensitive household configuration to local-only files while preserving future-reference examples in tracked docs
Notes:
No session snapshot file was found in documentation/project-history, so Why context was derived from the active task request and staged diff.
No TODO or RESTART NOTE markers were found in the staged files.
No BREAKING CHANGE detected (no compose port or volume path modifications).
- Extract troubleshooting guide to TROUBLESHOOTING.md
- Move usage examples to USAGE_EXAMPLES.md for better discoverability
- Add custom specialty creation guide to CONTRIBUTIONS.md
- Create semantic commit message generator prompt in prompts/
- Streamline README.md by removing 200+ lines of content now in dedicated files
- Improve documentation navigation with clearer separation of concerns
Corrections:
- File count: 22 → 23 files (actual count verified)
- Line count: ~6,200 → ~5,600 lines (verified with wc -l)
- Version history: Listed all 6 specialties explicitly (itil, devops, prompt-engineering, data-analysis, sccm, TEMPLATE)
- Added LEGACY.md to full documentation list
All metrics now reflect actual v6 system state.
Phase 1-4 Complete: Setup, Core Extraction, ITIL Specialty, Documentation
- Created v6/ folder with 3-layer architecture (core + skills + specialties)
- Extracted Frank.core.agent.md with universal personas and base commands
- Copied 7 skill modules (CRAFT, CoT, ToT, RAG, Markdown, Mermaid, Advanced Reasoning)
- Created specialty.itil.instructions.md for IT Service Management (ITIL v4)
- Added comprehensive ARCHITECTURE.md with usage patterns and migration guide
- Created v6/copilot-instructions.md for VS Code integration
- Organized legacy DOCX files into _Frank_/docx/ subdirectory
- Updated all cross-references to use v6 relative paths
Design Principles:
- Portability first: zero environment-specific paths
- Modular composition: load only what you need
- Multi-specialty support: combine domain experts
- Version compatibility: all files tagged v6.0
Ref: Session plan in /memories/session/plan.md
Next: Phase 3 (remaining specialties: devops, prompt-engineering, data-analysis, sccm)
