chore: upgrade aichaku to v0.28.0 and migrate to new structure

- Upgrade from v0.21.1 to v0.28.0
- Migrate completed zsh-cleanup project from .claude/output/ to docs/projects/done/
- Add behavioral guidelines and rules reminder
- Update CLAUDE.md with new aichaku reference
- Set up user customization directory

Author: RickCogley

.claude/aichaku/.aichaku-behavior

@@ -0,0 +1,24 @@
+# 🎯 Quick Reference for Claude Code
+
+## Before ANY work:
+1. Check docs/projects/active/ for existing project directories
+2. Create new YYYY-MM-DD-{name} directory for new work
+3. ALWAYS create STATUS.md first
+4. Read methodology guides from ~/.claude/aichaku/methodologies/
+
+## Key Behaviors:
+✅ Documents ALWAYS go in docs/projects/active/*/
+✅ Update STATUS.md after each work session
+✅ Create documents without asking permission
+✅ Move to docs/projects/done/ when complete
+
+❌ NEVER create documents in project root
+❌ NEVER use .claude/user/ for output
+❌ NEVER wait for permission to create standard docs
+❌ NEVER proceed with implementation without approval
+
+## Project Structure:
+- docs/projects/active/ → Work in progress
+- docs/projects/done/ → Completed work
+
+IMPORTANT: Creating proper structure is AUTOMATIC, not optional.

.claude/aichaku/RULES-REMINDER.md

@@ -0,0 +1,27 @@
+# 🚨 AICHAKU RULES REMINDER
+
+## Before creating ANY file, check:
+
+1. ✅ Is it going in `docs/projects/active/*/`?
+2. ✅ Does STATUS.md exist there?
+3. ✅ Have I updated STATUS.md recently?
+
+If any answer is NO → FIX IT FIRST!
+
+## Quick Fixes:
+
+### Wrong location?
+```bash
+mv [file] docs/projects/active/[current-project]/
+```
+
+### No STATUS.md?
+Create it immediately with project info.
+
+### Not sure where to put files?
+ALWAYS: `docs/projects/active/YYYY-MM-DD-{project-name}/`
+
+## Remember:
+- This is AUTOMATIC behavior
+- Users expect files in the right place
+- No asking, just doing

.claude/aichaku/aichaku.config.json

@@ -1,6 +1,8 @@
 {
-  "version": "0.21.1",
-  "installedAt": "2025-07-11T04:48:55.000Z",
-  "installationType": "local",
-  "lastUpgrade": "2025-07-11T04:49:17.028Z"
+  "version": "0.28.0",
+  "globalVersion": "0.28.0",
+  "createdAt": "2025-07-13T05:42:37.168Z",
+  "customizations": {
+    "userDir": "./user"
+  }
 }

.claude/aichaku/user/README.md

@@ -0,0 +1,112 @@
+# Aichaku Project Customizations
+
+This directory is yours to customize Aichaku's behavior. Files here are never modified during upgrades.
+
+## Directory Structure
+
+```
+user/
+├── prompts/      # Custom AI prompts
+├── templates/    # Custom document templates  
+└── methods/      # Custom methodology extensions
+```
+
+## How to Customize
+
+### 1. Custom Prompts (prompts/)
+
+Add files that extend or override default prompts:
+
+**Example: prompts/standup-casual.md**
+```markdown
+When conducting daily standups, use a more casual tone.
+Focus on blockers and collaboration opportunities.
+Keep updates brief and action-oriented.
+```
+
+### 2. Custom Templates (templates/)
+
+Add document templates for your organization:
+
+**Example: templates/change-control.md**
+```markdown
+# Change Control Document
+
+**Change ID**: CC-{date}-{number}
+**Requestor**: 
+**Date**: 
+**Impact**: Low | Medium | High
+
+## Change Description
+
+## Business Justification
+
+## Technical Details
+
+## Rollback Plan
+
+## Approvals
+- [ ] Technical Lead
+- [ ] Product Owner
+- [ ] Operations
+```
+
+### 3. Custom Methods (methods/)
+
+Extend methodologies with your practices:
+
+**Example: methods/code-review-checklist.md**
+```markdown
+## Code Review Checklist
+
+Before marking PR as ready:
+- [ ] Tests pass locally
+- [ ] Documentation updated
+- [ ] Security considerations noted
+- [ ] Performance impact assessed
+- [ ] Breaking changes documented
+```
+
+## Methodology Blending
+
+You can influence how Aichaku blends methodologies:
+
+**Example: methods/blending-preferences.md**
+```markdown
+## Our Methodology Preferences
+
+- Prefer Scrum terminology for ceremonies
+- Use Shape Up for feature planning
+- Apply XP practices for development
+- Kanban for operational work
+```
+
+## Organization-Specific Terms
+
+Define your organization's vocabulary:
+
+**Example: methods/vocabulary.md**
+```markdown
+## Our Terms
+
+- "Sprint" = 2-week iteration (not 3 weeks)
+- "Epic" = Major feature (3-6 sprints)
+- "Spike" = Research task (timeboxed)
+- "Ship It Day" = Our hack day (monthly)
+```
+
+## Tips
+
+1. **Start small** - Add customizations as needs arise
+2. **Document why** - Help future team members understand
+3. **Share patterns** - If something works well, document it
+4. **Iterate** - Refine based on what helps your team
+
+## Need Ideas?
+
+- Look at your team's recurring questions
+- Document decisions that keep coming up
+- Capture templates you use repeatedly
+- Note terminology that's unique to your org
+
+Remember: These customizations make Aichaku work better for YOUR team.

.claude/aichaku/user/methods/.gitkeep

@@ -27,15 +27,15 @@ Only create documents when user says:
 
 **Phase 3: CREATE NAMED PROJECT (After user signals readiness)**
 ✅ Confirm name: "🪴 Aichaku: Based on our discussion, creating project: [descriptive-name]"
-✅ Create ALL documents in: `.claude/output/active-YYYY-MM-DD-{descriptive-name}/`
+✅ Create ALL documents in: `docs/projects/active/YYYY-MM-DD-{descriptive-name}/`
 ✅ Create STATUS.md FIRST
 ✅ Create methodology-specific documents
 ✅ Read guides from `~/.claude/methodologies/`
 
 **YOU MUST NEVER:**
 ❌ Create documents in the project root directory
 ❌ Create documents in .claude/user/ (that's for customizations)
-❌ Ask where to put files (always use .claude/output/)
+❌ Ask where to put files (always use docs/projects/)
 ❌ Create folders before user is ready to formalize
 
 ### 2. CRITICAL: DISCUSSION FIRST, THEN CREATE WITHOUT ASKING
@@ -59,7 +59,7 @@ Only create documents when user says:
 
 When you hear these keywords, ENTER DISCUSSION MODE:
 
-**Planning Keywords** → Will create in `.claude/output/active-*/` (when ready):
+**Planning Keywords** → Will create in `docs/projects/active/*/` (when ready):
 - "shape"/"pitch" → Discuss Shape Up approach → Later: pitch.md
 - "sprint"/"scrum" → Discuss Scrum planning → Later: sprint-planning.md
 - "kanban"/"board" → Discuss Kanban flow → Later: kanban-board.md
@@ -148,7 +148,7 @@ gantt
 
 **Starting Work:**
 1. ⚠️ **CHECK TODAY'S DATE**: Look for "Today's date:" in the environment info
-2. Create: `.claude/output/active-YYYY-MM-DD-{descriptive-name}/`
+2. Create: `docs/projects/active/YYYY-MM-DD-{descriptive-name}/`
    - YYYY-MM-DD must be TODAY'S actual date from environment
    - Common mistake: Using 01 instead of current month
    - Example if today is 2025-07-10: `active-2025-07-10-project-name/`
@@ -177,7 +177,7 @@ gantt
 
 When work is confirmed complete:
 ```bash
-git add .claude/output/[current-project]/
+git add docs/projects/active/[current-project]/
 git commit -m "[type]: [description]
 
 - [what was done]
@@ -188,7 +188,7 @@ git push origin [current-branch]
 ### 8. Error Recovery
 
 If you accidentally create a file in the wrong location:
-1. Move it immediately: `mv [file] .claude/output/active-*/`
+1. Move it immediately: `mv [file] docs/projects/active/*/`
 2. Update STATUS.md noting the correction
 3. Continue without asking
 

.claude/aichaku/user/prompts/.gitkeep

@@ -0,0 +1,36 @@
+# Aichaku Project Documentation
+
+This directory contains all project documentation organized by status and date.
+
+## Structure
+
+- `active/` - Currently ongoing work
+- `done/` - Completed projects
+
+## Naming Convention
+
+`YYYY-MM-DD-[descriptive-kebab-case-name]`
+
+Examples:
+- active/2025-01-07-user-authentication
+- active/2025-01-07-fix-performance-issues
+- done/2025-01-06-global-project-redesign
+
+## What Goes Here
+
+Each project directory should contain:
+- STATUS.md - Current status and progress (ALWAYS create this first)
+- Planning documents (pitches, specs, backlogs)
+- Progress updates
+- Metrics and reviews
+- CHANGE-LOG.md - Summary when complete
+
+## For Claude Code
+
+When users discuss new work, IMMEDIATELY create a new active-* directory here.
+Don't wait to be asked. This is expected behavior.
+
+### Quick Reference
+- User says "let's shape X" → Create active-YYYY-MM-DD-shape-X/
+- User says "plan sprint" → Create active-YYYY-MM-DD-sprint-planning/
+- User says "fix bug" → Create active-YYYY-MM-DD-fix-[bug-description]/