Files
claude-task-master/assets/claude/commands/tm/expand/expand-task.md
Joe Danziger 95c299df64 Unify and streamline profile system architecture (#853)
* move claude rules and commands to assets/claude

* update claude profile to copy assets/claude to .claude

* fix formatting

* feat(profiles): Implement unified profile system

- Convert Claude and Codex profiles to use createProfile() factory
- Remove simple vs complex profile distinction in rule transformer
- Unify convertAllRulesToProfileRules() to handle all profiles consistently
- Fix mcpConfigPath construction in base-profile.js for null mcpConfigName
- Update terminology from 'simpleProfiles' to 'assetOnlyProfiles' throughout
- Ensure Claude .claude directory copying works in both CLI and MCP contexts
- All profiles now follow same execution flow with proper lifecycle functions

Changes:
- src/profiles/claude.js: Convert to createProfile() factory pattern
- src/profiles/codex.js: Convert to createProfile() factory pattern
- src/utils/rule-transformer.js: Unified profile handling logic
- src/utils/profiles.js: Remove simple profile categorization
- src/profiles/base-profile.js: Fix mcpConfigPath construction
- scripts/modules/commands.js: Update variable naming
- tests/: Update all tests for unified system and terminology

Fixes Claude profile asset copying issue in MCP context.
All tests passing (617 passed, 11 skipped).

* re-checkin claude files

* fix formatting

* chore: clean up test Claude rules files

* chore: add changeset for unified profile system

* add claude files back

* add changeset

* restore proper gitignore

* remove claude agents file from root

* remove incorrect doc

* simplify profiles and update tests

* update changeset

* update changeset

* remove profile specific code

* streamline profiles with defaults and update tests

* update changeset

* add newline at end of gitignore

* restore changes

* streamline profiles with defaults; update tests and add vscode test

* update rule profile tests

* update wording for clearer profile management

* refactor and clarify terminology

* use original projectRoot var name

* revert param desc

* use updated claude assets from neno

* add "YOUR_" before api key here

* streamline codex profile

* add gemini profile

* update gemini profile

* update tests

* relocate function

* update rules interactive setup Gemini desc

* remove duplicative code

* add comma
2025-07-09 13:22:11 +02:00

1.0 KiB

Break down a complex task into subtasks.

Arguments: $ARGUMENTS (task ID)

Intelligent Task Expansion

Analyzes a task and creates detailed subtasks for better manageability.

Execution

task-master expand --id=$ARGUMENTS

Expansion Process

  1. Task Analysis

    • Review task complexity
    • Identify components
    • Detect technical challenges
    • Estimate time requirements
  2. Subtask Generation

    • Create 3-7 subtasks typically
    • Each subtask 1-4 hours
    • Logical implementation order
    • Clear acceptance criteria
  3. Smart Breakdown

    • Setup/configuration tasks
    • Core implementation
    • Testing components
    • Integration steps
    • Documentation updates

Enhanced Features

Based on task type:

  • Feature: Setup → Implement → Test → Integrate
  • Bug Fix: Reproduce → Diagnose → Fix → Verify
  • Refactor: Analyze → Plan → Refactor → Validate

Post-Expansion

After expansion:

  1. Show subtask hierarchy
  2. Update time estimates
  3. Suggest implementation order
  4. Highlight critical path