Files
claude-task-master/assets/claude/commands/tm/next/next-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.8 KiB

Intelligently determine and prepare the next action based on comprehensive context.

This enhanced version of 'next' considers:

  • Current task states
  • Recent activity
  • Time constraints
  • Dependencies
  • Your working patterns

Arguments: $ARGUMENTS

Intelligent Next Action

1. Context Gathering

Let me analyze the current situation:

  • Active tasks (in-progress)
  • Recently completed tasks
  • Blocked tasks
  • Time since last activity
  • Arguments provided: $ARGUMENTS

2. Smart Decision Tree

If you have an in-progress task:

  • Has it been idle > 2 hours? → Suggest resuming or switching
  • Near completion? → Show remaining steps
  • Blocked? → Find alternative task

If no in-progress tasks:

  • Unblocked high-priority tasks? → Start highest
  • Complex tasks need breakdown? → Suggest expansion
  • All tasks blocked? → Show dependency resolution

Special arguments handling:

  • "quick" → Find task < 2 hours
  • "easy" → Find low complexity task
  • "important" → Find high priority regardless of complexity
  • "continue" → Resume last worked task

3. Preparation Workflow

Based on selected task:

  1. Show full context and history
  2. Set up development environment
  3. Run relevant tests
  4. Open related files
  5. Show similar completed tasks
  6. Estimate completion time

4. Alternative Suggestions

Always provide options:

  • Primary recommendation
  • Quick alternative (< 1 hour)
  • Strategic option (unblocks most tasks)
  • Learning option (new technology/skill)

5. Workflow Integration

Seamlessly connect to:

  • /project:task-master:start [selected]
  • /project:workflows:auto-implement
  • /project:task-master:expand (if complex)
  • /project:utils:complexity-report (if unsure)

The goal: Zero friction from decision to implementation.