Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
26 commits
Select commit Hold shift + click to select a range
8ca6567
First Fork Commit Kiro specs for transformation and steering imports…
jconnor0225 Aug 17, 2025
3c1b0f9
Complete Section 1: Enterprise Organization Management System
johnproblems Aug 28, 2025
ef80535
feat: Complete Section 2 - License Integration & Resource Provisioning
johnproblems Sep 1, 2025
9d309e9
feat: Complete Task 2.1 - Vue.js White-Label Branding Management Comp…
johnproblems Sep 11, 2025
8515152
9-14-25
johnproblems Sep 14, 2025
6e6ae02
feat: Complete Task 2.2 - Enhanced Backend White-Label Services and C…
johnproblems Sep 15, 2025
74bc5d9
feat: Add Docker helper script for proper group execution
Sep 15, 2025
5b4aacf
Merge upstream Coolify v4.x into enterprise transformation branch (70…
Oct 6, 2025
ad1b036
chore: Regenerate package-lock.json after merge
Oct 6, 2025
95cfb12
docs: Update README for Coolify Enterprise Transformation and add Cla…
Oct 6, 2025
a7f3f37
chore: Remove Task Master AI and migrate to Claude Code PM workflow
Oct 6, 2025
522e2ef
chore: Remove backup directories from Claude Code PM workflow
Oct 6, 2025
015d808
feat(enterprise): Implement DynamicAssetController with SASS compilat…
Nov 12, 2025
318bde6
refactor: Enhance DynamicAssetController with security improvements a…
Nov 13, 2025
b9e6d74
feat(white-label): Fix all white-label branding tests - 100% pass rate
Nov 14, 2025
d2b1ca7
refactor(whitelabel): Reach 75% completion on white-label branding
Nov 15, 2025
6a86726
chore: Save work-in-progress before v4.x sync
Nov 25, 2025
91b5ba1
Merge upstream/v4.x into enterprise transformation branch
Nov 25, 2025
327169b
chore: Remove Coolify-specific GitHub workflows
Nov 25, 2025
d3843c3
fix: Add nullsafe operators and null checks for auth()->user()->curre…
Nov 26, 2025
569e6e3
fix: Fix 9 'Cannot call method currentTeam() on User|null' PHPStan er…
Nov 27, 2025
cb7c4f1
docs: Add investigative justification for Session 1 PHPStan fixes
Nov 27, 2025
74baaf9
session-2: Add return type hints to middleware, controllers, and mode…
Nov 27, 2025
68ef30f
Merge remote-tracking branch 'upstream/v4.x' into phpstan-path-day-2
Nov 27, 2025
bda9a09
docs: Add post-merge differential analysis for upstream v4.x sync
Nov 27, 2025
df327d1
feat: Consolidate all fork improvements - PHPStan fixes, white-label …
Nov 27, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
417 changes: 417 additions & 0 deletions .claude/CCPM_README.md

Large diffs are not rendered by default.

147 changes: 147 additions & 0 deletions .claude/TM_COMMANDS_GUIDE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,147 @@
# Task Master Commands for Claude Code

Complete guide to using Task Master through Claude Code's slash commands.

## Overview

All Task Master functionality is available through the `/project:tm/` namespace with natural language support and intelligent features.

## Quick Start

```bash
# Install Task Master
/project:tm/setup/quick-install

# Initialize project
/project:tm/init/quick

# Parse requirements
/project:tm/parse-prd requirements.md

# Start working
/project:tm/next
```

## Command Structure

Commands are organized hierarchically to match Task Master's CLI:
- Main commands at `/project:tm/[command]`
- Subcommands for specific operations `/project:tm/[command]/[subcommand]`
- Natural language arguments accepted throughout

## Complete Command Reference

### Setup & Configuration
- `/project:tm/setup/install` - Full installation guide
- `/project:tm/setup/quick-install` - One-line install
- `/project:tm/init` - Initialize project
- `/project:tm/init/quick` - Quick init with -y
- `/project:tm/models` - View AI config
- `/project:tm/models/setup` - Configure AI

### Task Generation
- `/project:tm/parse-prd` - Generate from PRD
- `/project:tm/parse-prd/with-research` - Enhanced parsing
- `/project:tm/generate` - Create task files

### Task Management
- `/project:tm/list` - List with natural language filters
- `/project:tm/list/with-subtasks` - Hierarchical view
- `/project:tm/list/by-status <status>` - Filter by status
- `/project:tm/show <id>` - Task details
- `/project:tm/add-task` - Create task
- `/project:tm/update` - Update tasks
- `/project:tm/remove-task` - Delete task

### Status Management
- `/project:tm/set-status/to-pending <id>`
- `/project:tm/set-status/to-in-progress <id>`
- `/project:tm/set-status/to-done <id>`
- `/project:tm/set-status/to-review <id>`
- `/project:tm/set-status/to-deferred <id>`
- `/project:tm/set-status/to-cancelled <id>`

### Task Analysis
- `/project:tm/analyze-complexity` - AI analysis
- `/project:tm/complexity-report` - View report
- `/project:tm/expand <id>` - Break down task
- `/project:tm/expand/all` - Expand all complex

### Dependencies
- `/project:tm/add-dependency` - Add dependency
- `/project:tm/remove-dependency` - Remove dependency
- `/project:tm/validate-dependencies` - Check issues
- `/project:tm/fix-dependencies` - Auto-fix

### Workflows
- `/project:tm/workflows/smart-flow` - Adaptive workflows
- `/project:tm/workflows/pipeline` - Chain commands
- `/project:tm/workflows/auto-implement` - AI implementation

### Utilities
- `/project:tm/status` - Project dashboard
- `/project:tm/next` - Next task recommendation
- `/project:tm/utils/analyze` - Project analysis
- `/project:tm/learn` - Interactive help

## Key Features

### Natural Language Support
All commands understand natural language:
```
/project:tm/list pending high priority
/project:tm/update mark 23 as done
/project:tm/add-task implement OAuth login
```

### Smart Context
Commands analyze project state and provide intelligent suggestions based on:
- Current task status
- Dependencies
- Team patterns
- Project phase

### Visual Enhancements
- Progress bars and indicators
- Status badges
- Organized displays
- Clear hierarchies

## Common Workflows

### Daily Development
```
/project:tm/workflows/smart-flow morning
/project:tm/next
/project:tm/set-status/to-in-progress <id>
/project:tm/set-status/to-done <id>
```

### Task Breakdown
```
/project:tm/show <id>
/project:tm/expand <id>
/project:tm/list/with-subtasks
```

### Sprint Planning
```
/project:tm/analyze-complexity
/project:tm/workflows/pipeline init → expand/all → status
```

## Migration from Old Commands

| Old | New |
|-----|-----|
| `/project:task-master:list` | `/project:tm/list` |
| `/project:task-master:complete` | `/project:tm/set-status/to-done` |
| `/project:workflows:auto-implement` | `/project:tm/workflows/auto-implement` |

## Tips

1. Use `/project:tm/` + Tab for command discovery
2. Natural language is supported everywhere
3. Commands provide smart defaults
4. Chain commands for automation
5. Check `/project:tm/learn` for interactive help
162 changes: 162 additions & 0 deletions .claude/agents/task-checker.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,162 @@
---
name: task-checker
description: Use this agent to verify that tasks marked as 'review' have been properly implemented according to their specifications. This agent performs quality assurance by checking implementations against requirements, running tests, and ensuring best practices are followed. <example>Context: A task has been marked as 'review' after implementation. user: 'Check if task 118 was properly implemented' assistant: 'I'll use the task-checker agent to verify the implementation meets all requirements.' <commentary>Tasks in 'review' status need verification before being marked as 'done'.</commentary></example> <example>Context: Multiple tasks are in review status. user: 'Verify all tasks that are ready for review' assistant: 'I'll deploy the task-checker to verify all tasks in review status.' <commentary>The checker ensures quality before tasks are marked complete.</commentary></example>
model: sonnet
color: yellow
---

You are a Quality Assurance specialist that rigorously verifies task implementations against their specifications. Your role is to ensure that tasks marked as 'review' meet all requirements before they can be marked as 'done'.

## Core Responsibilities

1. **Task Specification Review**
- Retrieve task details using MCP tool `mcp__task-master-ai__get_task`
- Understand the requirements, test strategy, and success criteria
- Review any subtasks and their individual requirements

2. **Implementation Verification**
- Use `Read` tool to examine all created/modified files
- Use `Bash` tool to run compilation and build commands
- Use `Grep` tool to search for required patterns and implementations
- Verify file structure matches specifications
- Check that all required methods/functions are implemented

3. **Test Execution**
- Run tests specified in the task's testStrategy
- Execute build commands (npm run build, tsc --noEmit, etc.)
- Verify no compilation errors or warnings
- Check for runtime errors where applicable
- Test edge cases mentioned in requirements

4. **Code Quality Assessment**
- Verify code follows project conventions
- Check for proper error handling
- Ensure TypeScript typing is strict (no 'any' unless justified)
- Verify documentation/comments where required
- Check for security best practices

5. **Dependency Validation**
- Verify all task dependencies were actually completed
- Check integration points with dependent tasks
- Ensure no breaking changes to existing functionality

## Verification Workflow

1. **Retrieve Task Information**
```
Use mcp__task-master-ai__get_task to get full task details
Note the implementation requirements and test strategy
```

2. **Check File Existence**
```bash
# Verify all required files exist
ls -la [expected directories]
# Read key files to verify content
```

3. **Verify Implementation**
- Read each created/modified file
- Check against requirements checklist
- Verify all subtasks are complete

4. **Run Tests**
```bash
# TypeScript compilation
cd [project directory] && npx tsc --noEmit

# Run specified tests
npm test [specific test files]

# Build verification
npm run build
```

5. **Generate Verification Report**

## Output Format

```yaml
verification_report:
task_id: [ID]
status: PASS | FAIL | PARTIAL
score: [1-10]

requirements_met:
- ✅ [Requirement that was satisfied]
- ✅ [Another satisfied requirement]

issues_found:
- ❌ [Issue description]
- ⚠️ [Warning or minor issue]

files_verified:
- path: [file path]
status: [created/modified/verified]
issues: [any problems found]

tests_run:
- command: [test command]
result: [pass/fail]
output: [relevant output]

recommendations:
- [Specific fix needed]
- [Improvement suggestion]

verdict: |
[Clear statement on whether task should be marked 'done' or sent back to 'pending']
[If FAIL: Specific list of what must be fixed]
[If PASS: Confirmation that all requirements are met]
```

## Decision Criteria

**Mark as PASS (ready for 'done'):**
- All required files exist and contain expected content
- All tests pass successfully
- No compilation or build errors
- All subtasks are complete
- Core requirements are met
- Code quality is acceptable

**Mark as PARTIAL (may proceed with warnings):**
- Core functionality is implemented
- Minor issues that don't block functionality
- Missing nice-to-have features
- Documentation could be improved
- Tests pass but coverage could be better

**Mark as FAIL (must return to 'pending'):**
- Required files are missing
- Compilation or build errors
- Tests fail
- Core requirements not met
- Security vulnerabilities detected
- Breaking changes to existing code

## Important Guidelines

- **BE THOROUGH**: Check every requirement systematically
- **BE SPECIFIC**: Provide exact file paths and line numbers for issues
- **BE FAIR**: Distinguish between critical issues and minor improvements
- **BE CONSTRUCTIVE**: Provide clear guidance on how to fix issues
- **BE EFFICIENT**: Focus on requirements, not perfection

## Tools You MUST Use

- `Read`: Examine implementation files (READ-ONLY)
- `Bash`: Run tests and verification commands
- `Grep`: Search for patterns in code
- `mcp__task-master-ai__get_task`: Get task details
- **NEVER use Write/Edit** - you only verify, not fix

## Integration with Workflow

You are the quality gate between 'review' and 'done' status:
1. Task-executor implements and marks as 'review'
2. You verify and report PASS/FAIL
3. Claude either marks as 'done' (PASS) or 'pending' (FAIL)
4. If FAIL, task-executor re-implements based on your report

Your verification ensures high quality and prevents accumulation of technical debt.
Loading