Initial commit

commands/dev-docs-update.md

@@ -0,0 +1,55 @@
+---
+description: Update dev documentation before context compaction
+argument-hint: Optional - specific context or tasks to focus on (leave empty for comprehensive update)
+---
+
+We're approaching context limits. Please update the development documentation to ensure seamless continuation after context reset.
+
+## Required Updates
+
+### 1. Update Active Task Documentation
+For each task in `/dev/active/`:
+- Update `[task-name]-context.md` with:
+  - Current implementation state
+  - Key decisions made this session
+  - Files modified and why
+  - Any blockers or issues discovered
+  - Next immediate steps
+  - Last Updated timestamp
+
+- Update `[task-name]-tasks.md` with:
+  - Mark completed tasks as ✅ 
+  - Add any new tasks discovered
+  - Update in-progress tasks with current status
+  - Reorder priorities if needed
+
+### 2. Capture Session Context
+Include any relevant information about:
+- Complex problems solved
+- Architectural decisions made
+- Tricky bugs found and fixed
+- Integration points discovered
+- Testing approaches used
+- Performance optimizations made
+
+### 3. Update Memory (if applicable)
+- Store any new patterns or solutions in project memory/documentation
+- Update entity relationships discovered
+- Add observations about system behavior
+
+### 4. Document Unfinished Work
+- What was being worked on when context limit approached
+- Exact state of any partially completed features
+- Commands that need to be run on restart
+- Any temporary workarounds that need permanent fixes
+
+### 5. Create Handoff Notes
+If switching to a new conversation:
+- Exact file and line being edited
+- The goal of current changes
+- Any uncommitted changes that need attention
+- Test commands to verify work
+
+## Additional Context: $ARGUMENTS
+
+**Priority**: Focus on capturing information that would be hard to rediscover or reconstruct from code alone.

commands/dev-docs.md

@@ -0,0 +1,51 @@
+---
+description: Create a comprehensive strategic plan with structured task breakdown
+argument-hint: Describe what you need planned (e.g., "refactor authentication system", "implement microservices")
+---
+
+You are an elite strategic planning specialist. Create a comprehensive, actionable plan for: $ARGUMENTS
+
+## Instructions
+
+1. **Analyze the request** and determine the scope of planning needed
+2. **Examine relevant files** in the codebase to understand current state
+3. **Create a structured plan** with:
+   - Executive Summary
+   - Current State Analysis
+   - Proposed Future State
+   - Implementation Phases (broken into sections)
+   - Detailed Tasks (actionable items with clear acceptance criteria)
+   - Risk Assessment and Mitigation Strategies
+   - Success Metrics
+   - Required Resources and Dependencies
+   - Timeline Estimates
+
+4. **Task Breakdown Structure**:
+   - Each major section represents a phase or component
+   - Number and prioritize tasks within sections
+   - Include clear acceptance criteria for each task
+   - Specify dependencies between tasks
+   - Estimate effort levels (S/M/L/XL)
+
+5. **Create task management structure**:
+   - Create directory: `dev/active/[task-name]/` (relative to project root)
+   - Generate three files:
+     - `[task-name]-plan.md` - The comprehensive plan
+     - `[task-name]-context.md` - Key files, decisions, dependencies
+     - `[task-name]-tasks.md` - Checklist format for tracking progress
+   - Include "Last Updated: YYYY-MM-DD" in each file
+
+## Quality Standards
+- Plans must be self-contained with all necessary context
+- Use clear, actionable language
+- Include specific technical details where relevant
+- Consider both technical and business perspectives
+- Account for potential risks and edge cases
+
+## Context References
+- Check `PROJECT_KNOWLEDGE.md` for architecture overview (if exists)
+- Consult `BEST_PRACTICES.md` for coding standards (if exists)
+- Reference `TROUBLESHOOTING.md` for common issues to avoid (if exists)
+- Use `dev/README.md` for task management guidelines (if exists)
+
+**Note**: This command is ideal to use AFTER exiting plan mode when you have a clear vision of what needs to be done. It will create the persistent task structure that survives context resets.