95c299df64
* 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
36 lines
901 B
Markdown
36 lines
901 B
Markdown
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 |