data_porter 0.1.0 → 0.2.0

data/.claude/commands/tm/to-deferred.md

@@ -1,50 +0,0 @@
-To Deferred
-
-Arguments: $ARGUMENTS
-Defer a task for later consideration.
-
-Arguments: $ARGUMENTS (task ID)
-
-## Deferring a Task
-
-This status indicates a task is valid but not currently actionable or prioritized.
-
-## Valid Reasons for Deferral
-
-- Waiting for external dependencies
-- Reprioritized for future sprint
-- Blocked by technical limitations
-- Resource constraints
-- Strategic timing considerations
-
-## Execution
-
-```bash
-task-master set-status --id=$ARGUMENTS --status=deferred
-```
-
-## Deferral Management
-
-When deferring:
-1. **Document Reason**
-   - Capture why it's being deferred
-   - Set reactivation criteria
-   - Note any partial work completed
-
-2. **Impact Analysis**
-   - Check dependent tasks
-   - Update project timeline
-   - Notify affected stakeholders
-
-3. **Future Planning**
-   - Set review reminders
-   - Tag for specific milestone
-   - Preserve context for reactivation
-   - Link to blocking issues
-
-## Smart Tracking
-
-- Monitor deferral duration
-- Alert when criteria met
-- Prevent scope creep
-- Regular review cycles

data/.claude/commands/tm/to-done.md

@@ -1,47 +0,0 @@
-To Done
-
-Arguments: $ARGUMENTS
-Mark a task as completed.
-
-Arguments: $ARGUMENTS (task ID)
-
-## Completing a Task
-
-This command validates task completion and updates project state intelligently.
-
-## Pre-Completion Checks
-
-1. Verify test strategy was followed
-2. Check if all subtasks are complete
-3. Validate acceptance criteria met
-4. Ensure code is committed
-
-## Execution
-
-```bash
-task-master set-status --id=$ARGUMENTS --status=done
-```
-
-## Post-Completion Actions
-
-1. **Update Dependencies**
-   - Identify newly unblocked tasks
-   - Update sprint progress
-   - Recalculate project timeline
-
-2. **Documentation**
-   - Generate completion summary
-   - Update CLAUDE.md with learnings
-   - Log implementation approach
-
-3. **Next Steps**
-   - Show newly available tasks
-   - Suggest logical next task
-   - Update velocity metrics
-
-## Celebration & Learning
-
-- Show impact of completion
-- Display unblocked work
-- Recognize achievement
-- Capture lessons learned

data/.claude/commands/tm/to-in-progress.md

@@ -1,39 +0,0 @@
-To In Progress
-
-Arguments: $ARGUMENTS
-Start working on a task by setting its status to in-progress.
-
-Arguments: $ARGUMENTS (task ID)
-
-## Starting Work on Task
-
-This command does more than just change status - it prepares your environment for productive work.
-
-## Pre-Start Checks
-
-1. Verify dependencies are met
-2. Check if another task is already in-progress
-3. Ensure task details are complete
-4. Validate test strategy exists
-
-## Execution
-
-```bash
-task-master set-status --id=$ARGUMENTS --status=in-progress
-```
-
-## Environment Setup
-
-After setting to in-progress:
-1. Create/checkout appropriate git branch
-2. Open relevant documentation
-3. Set up test watchers if applicable
-4. Display task details and acceptance criteria
-5. Show similar completed tasks for reference
-
-## Smart Suggestions
-
-- Estimated completion time based on complexity
-- Related files from similar tasks
-- Potential blockers to watch for
-- Recommended first steps

data/.claude/commands/tm/to-pending.md

@@ -1,35 +0,0 @@
-To Pending
-
-Arguments: $ARGUMENTS
-Set a task's status to pending.
-
-Arguments: $ARGUMENTS (task ID)
-
-## Setting Task to Pending
-
-This moves a task back to the pending state, useful for:
-- Resetting erroneously started tasks
-- Deferring work that was prematurely begun
-- Reorganizing sprint priorities
-
-## Execution
-
-```bash
-task-master set-status --id=$ARGUMENTS --status=pending
-```
-
-## Validation
-
-Before setting to pending:
-- Warn if task is currently in-progress
-- Check if this will block other tasks
-- Suggest documenting why it's being reset
-- Preserve any work already done
-
-## Smart Actions
-
-After setting to pending:
-- Update sprint planning if needed
-- Notify about freed resources
-- Suggest priority reassessment
-- Log the status change with context

data/.claude/commands/tm/to-review.md

@@ -1,43 +0,0 @@
-To Review
-
-Arguments: $ARGUMENTS
-Set a task's status to review.
-
-Arguments: $ARGUMENTS (task ID)
-
-## Marking Task for Review
-
-This status indicates work is complete but needs verification before final approval.
-
-## When to Use Review Status
-
-- Code complete but needs peer review
-- Implementation done but needs testing
-- Documentation written but needs proofreading
-- Design complete but needs stakeholder approval
-
-## Execution
-
-```bash
-task-master set-status --id=$ARGUMENTS --status=review
-```
-
-## Review Preparation
-
-When setting to review:
-1. **Generate Review Checklist**
-   - Link to PR/MR if applicable
-   - Highlight key changes
-   - Note areas needing attention
-   - Include test results
-
-2. **Documentation**
-   - Update task with review notes
-   - Link relevant artifacts
-   - Specify reviewers if known
-
-3. **Smart Actions**
-   - Create review reminders
-   - Track review duration
-   - Suggest reviewers based on expertise
-   - Prepare rollback plan if needed

data/.claude/commands/tm/update-single-task.md

@@ -1,122 +0,0 @@
-Update Single Task
-
-Arguments: $ARGUMENTS
-Update a single specific task with new information.
-
-Arguments: $ARGUMENTS
-
-Parse task ID and update details.
-
-## Single Task Update
-
-Precisely update one task with AI assistance to maintain consistency.
-
-## Argument Parsing
-
-Natural language updates:
-- "5: add caching requirement"
-- "update 5 to include error handling"
-- "task 5 needs rate limiting"
-- "5 change priority to high"
-
-## Execution
-
-```bash
-task-master update-task --id=<id> --prompt="<context>"
-```
-
-## Update Types
-
-### 1. **Content Updates**
-- Enhance description
-- Add requirements
-- Clarify details
-- Update acceptance criteria
-
-### 2. **Metadata Updates**
-- Change priority
-- Adjust time estimates
-- Update complexity
-- Modify dependencies
-
-### 3. **Strategic Updates**
-- Revise approach
-- Change test strategy
-- Update implementation notes
-- Adjust subtask needs
-
-## AI-Powered Updates
-
-The AI:
-1. **Understands Context**
-   - Reads current task state
-   - Identifies update intent
-   - Maintains consistency
-   - Preserves important info
-
-2. **Applies Changes**
-   - Updates relevant fields
-   - Keeps style consistent
-   - Adds without removing
-   - Enhances clarity
-
-3. **Validates Results**
-   - Checks coherence
-   - Verifies completeness
-   - Maintains relationships
-   - Suggests related updates
-
-## Example Updates
-
-```
-/taskmaster:update/single 5: add rate limiting
-→ Updating Task #5: "Implement API endpoints"
-
-Current: Basic CRUD endpoints
-Adding: Rate limiting requirements
-
-Updated sections:
-✓ Description: Added rate limiting mention
-✓ Details: Added specific limits (100/min)
-✓ Test Strategy: Added rate limit tests
-✓ Complexity: Increased from 5 to 6
-✓ Time Estimate: Increased by 2 hours
-
-Suggestion: Also update task #6 (API Gateway) for consistency?
-```
-
-## Smart Features
-
-1. **Incremental Updates**
-   - Adds without overwriting
-   - Preserves work history
-   - Tracks what changed
-   - Shows diff view
-
-2. **Consistency Checks**
-   - Related task alignment
-   - Subtask compatibility
-   - Dependency validity
-   - Timeline impact
-
-3. **Update History**
-   - Timestamp changes
-   - Track who/what updated
-   - Reason for update
-   - Previous versions
-
-## Field-Specific Updates
-
-Quick syntax for specific fields:
-- "5 priority:high" → Update priority only
-- "5 add-time:4h" → Add to time estimate
-- "5 status:review" → Change status
-- "5 depends:3,4" → Add dependencies
-
-## Post-Update
-
-- Show updated task
-- Highlight changes
-- Check related tasks
-- Update suggestions
-- Timeline adjustments

data/.claude/commands/tm/update-task.md

@@ -1,75 +0,0 @@
-Update Task
-
-Arguments: $ARGUMENTS
-Update tasks with intelligent field detection and bulk operations.
-
-Arguments: $ARGUMENTS
-
-## Intelligent Task Updates
-
-Parse arguments to determine update intent and execute smartly.
-
-### 1. **Natural Language Processing**
-
-Understand update requests like:
-- "mark 23 as done" → Update status to done
-- "increase priority of 45" → Set priority to high
-- "add dependency on 12 to task 34" → Add dependency
-- "tasks 20-25 need review" → Bulk status update
-- "all API tasks high priority" → Pattern-based update
-
-### 2. **Smart Field Detection**
-
-Automatically detect what to update:
-- Status keywords: done, complete, start, pause, review
-- Priority changes: urgent, high, low, deprioritize
-- Dependency updates: depends on, blocks, after
-- Assignment: assign to, owner, responsible
-- Time: estimate, spent, deadline
-
-### 3. **Bulk Operations**
-
-Support for multiple task updates:
-```
-Examples:
-- "complete tasks 12, 15, 18"
-- "all pending auth tasks to in-progress"
-- "increase priority for tasks blocking 45"
-- "defer all documentation tasks"
-```
-
-### 4. **Contextual Validation**
-
-Before updating, check:
-- Status transitions are valid
-- Dependencies don't create cycles
-- Priority changes make sense
-- Bulk updates won't break project flow
-
-Show preview:
-```
-Update Preview:
-─────────────────
-Tasks to update: #23, #24, #25
-Change: status → in-progress
-Impact: Will unblock tasks #30, #31
-Warning: Task #24 has unmet dependencies
-```
-
-### 5. **Smart Suggestions**
-
-Based on update:
-- Completing task? → Show newly unblocked tasks
-- Changing priority? → Show impact on sprint
-- Adding dependency? → Check for conflicts
-- Bulk update? → Show summary of changes
-
-### 6. **Workflow Integration**
-
-After updates:
-- Auto-update dependent task states
-- Trigger status recalculation
-- Update sprint/milestone progress
-- Log changes with context
-
-Result: Flexible, intelligent task updates with safety checks.

data/.claude/commands/tm/update-tasks-from-id.md

@@ -1,111 +0,0 @@
-Update Tasks From ID
-
-Arguments: $ARGUMENTS
-Update multiple tasks starting from a specific ID.
-
-Arguments: $ARGUMENTS
-
-Parse starting task ID and update context.
-
-## Bulk Task Updates
-
-Update multiple related tasks based on new requirements or context changes.
-
-## Argument Parsing
-
-- "from 5: add security requirements"
-- "5 onwards: update API endpoints"
-- "starting at 5: change to use new framework"
-
-## Execution
-
-```bash
-task-master update --from=<id> --prompt="<context>"
-```
-
-## Update Process
-
-### 1. **Task Selection**
-Starting from specified ID:
-- Include the task itself
-- Include all dependent tasks
-- Include related subtasks
-- Smart boundary detection
-
-### 2. **Context Application**
-AI analyzes the update context and:
-- Identifies what needs changing
-- Maintains consistency
-- Preserves completed work
-- Updates related information
-
-### 3. **Intelligent Updates**
-- Modify descriptions appropriately
-- Update test strategies
-- Adjust time estimates
-- Revise dependencies if needed
-
-## Smart Features
-
-1. **Scope Detection**
-   - Find natural task groupings
-   - Identify related features
-   - Stop at logical boundaries
-   - Avoid over-updating
-
-2. **Consistency Maintenance**
-   - Keep naming conventions
-   - Preserve relationships
-   - Update cross-references
-   - Maintain task flow
-
-3. **Change Preview**
-   ```
-   Bulk Update Preview
-   ━━━━━━━━━━━━━━━━━━
-   Starting from: Task #5
-   Tasks to update: 8 tasks + 12 subtasks
-
-   Context: "add security requirements"
-
-   Changes will include:
-   - Add security sections to descriptions
-   - Update test strategies for security
-   - Add security-related subtasks where needed
-   - Adjust time estimates (+20% average)
-
-   Continue? (y/n)
-   ```
-
-## Example Updates
-
-```
-/taskmaster:update-tasks-from-id 5: change database to PostgreSQL
-→ Analyzing impact starting from task #5
-→ Found 6 related tasks to update
-→ Updates will maintain consistency
-→ Preview changes? (y/n)
-
-Applied updates:
-✓ Task #5: Updated connection logic references
-✓ Task #6: Changed migration approach
-✓ Task #7: Updated query syntax notes
-✓ Task #8: Revised testing strategy
-✓ Task #9: Updated deployment steps
-✓ Task #12: Changed backup procedures
-```
-
-## Safety Features
-
-- Preview all changes
-- Selective confirmation
-- Rollback capability
-- Change logging
-- Validation checks
-
-## Post-Update
-
-- Summary of changes
-- Consistency verification
-- Suggest review tasks
-- Update timeline if needed

data/.claude/commands/tm/validate-dependencies.md

@@ -1,72 +0,0 @@
-Validate Dependencies
-Validate all task dependencies for issues.
-
-## Dependency Validation
-
-Comprehensive check for dependency problems across the entire project.
-
-## Execution
-
-```bash
-task-master validate-dependencies
-```
-
-## Validation Checks
-
-1. **Circular Dependencies**
-   - A depends on B, B depends on A
-   - Complex circular chains
-   - Self-dependencies
-
-2. **Missing Dependencies**
-   - References to non-existent tasks
-   - Deleted task references
-   - Invalid task IDs
-
-3. **Logical Issues**
-   - Completed tasks depending on pending
-   - Cancelled tasks in dependency chains
-   - Impossible sequences
-
-4. **Complexity Warnings**
-   - Over-complex dependency chains
-   - Too many dependencies per task
-   - Bottleneck tasks
-
-## Smart Analysis
-
-The validation provides:
-- Visual dependency graph
-- Critical path analysis
-- Bottleneck identification
-- Suggested optimizations
-
-## Report Format
-
-```
-Dependency Validation Report
-━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ No circular dependencies found
-⚠️  2 warnings found:
-   - Task #23 has 7 dependencies (consider breaking down)
-   - Task #45 blocks 5 other tasks (potential bottleneck)
-❌ 1 error found:
-   - Task #67 depends on deleted task #66
-
-Critical Path: #1 → #5 → #23 → #45 → #50 (15 days)
-```
-
-## Actionable Output
-
-For each issue found:
-- Clear description
-- Impact assessment
-- Suggested fix
-- Command to resolve
-
-## Next Steps
-
-After validation:
-- Run `/taskmaster:fix-dependencies` to auto-fix
-- Manually adjust problematic dependencies
-- Rerun to verify fixes

data/.claude/commands/tm/view-models.md

@@ -1,52 +0,0 @@
-View Models
-View current AI model configuration.
-
-## Model Configuration Display
-
-Shows the currently configured AI providers and models for Task Master.
-
-## Execution
-
-```bash
-task-master models
-```
-
-## Information Displayed
-
-1. **Main Provider**
-   - Model ID and name
-   - API key status (configured/missing)
-   - Usage: Primary task generation
-
-2. **Research Provider**
-   - Model ID and name
-   - API key status
-   - Usage: Enhanced research mode
-
-3. **Fallback Provider**
-   - Model ID and name
-   - API key status
-   - Usage: Backup when main fails
-
-## Visual Status
-
-```
-Task Master AI Model Configuration
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-Main:     ✅ claude-3-5-sonnet (configured)
-Research: ✅ perplexity-sonar (configured)
-Fallback: ⚠️  Not configured (optional)
-
-Available Models:
-- claude-3-5-sonnet
-- gpt-4-turbo
-- gpt-3.5-turbo
-- perplexity-sonar
-```
-
-## Next Actions
-
-Based on configuration:
-- If missing API keys → Suggest setup
-- If no research model → Explain benefits
-- If all configured → Show usage tips

data/.env.example

@@ -1,12 +0,0 @@
-# API Keys (Required to enable respective provider)
-ANTHROPIC_API_KEY="your_anthropic_api_key_here"       # Required: Format: sk-ant-api03-...
-PERPLEXITY_API_KEY="your_perplexity_api_key_here"     # Optional: Format: pplx-...
-OPENAI_API_KEY="your_openai_api_key_here"             # Optional, for OpenAI models. Format: sk-proj-...
-GOOGLE_API_KEY="your_google_api_key_here"             # Optional, for Google Gemini models.
-MISTRAL_API_KEY="your_mistral_key_here"               # Optional, for Mistral AI models.
-XAI_API_KEY="YOUR_XAI_KEY_HERE"                       # Optional, for xAI AI models.
-GROQ_API_KEY="YOUR_GROQ_KEY_HERE"                     # Optional, for Groq models.
-OPENROUTER_API_KEY="YOUR_OPENROUTER_KEY_HERE"         # Optional, for OpenRouter models.
-AZURE_OPENAI_API_KEY="your_azure_key_here"            # Optional, for Azure OpenAI models (requires endpoint in .taskmaster/config.json).
-OLLAMA_API_KEY="your_ollama_api_key_here"             # Optional: For remote Ollama servers that require authentication.
-GITHUB_API_KEY="your_github_api_key_here"             # Optional: For GitHub import/export features. Format: ghp_... or github_pat_...

data/.mcp.json

@@ -1,24 +0,0 @@
-{
-	"mcpServers": {
-		"task-master-ai": {
-			"type": "stdio",
-			"command": "npx",
-			"args": [
-				"-y",
-				"task-master-ai"
-			],
-			"env": {
-				"TASK_MASTER_TOOLS": "core",
-				"ANTHROPIC_API_KEY": "YOUR_ANTHROPIC_API_KEY_HERE",
-				"PERPLEXITY_API_KEY": "YOUR_PERPLEXITY_API_KEY_HERE",
-				"OPENAI_API_KEY": "YOUR_OPENAI_KEY_HERE",
-				"GOOGLE_API_KEY": "YOUR_GOOGLE_KEY_HERE",
-				"XAI_API_KEY": "YOUR_XAI_KEY_HERE",
-				"OPENROUTER_API_KEY": "YOUR_OPENROUTER_KEY_HERE",
-				"MISTRAL_API_KEY": "YOUR_MISTRAL_KEY_HERE",
-				"AZURE_OPENAI_API_KEY": "YOUR_AZURE_KEY_HERE",
-				"OLLAMA_API_KEY": "YOUR_OLLAMA_API_KEY_HERE"
-			}
-		}
-	}
-}