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
55 lines
1.2 KiB
Markdown
55 lines
1.2 KiB
Markdown
Add a dependency between tasks.
|
|
|
|
Arguments: $ARGUMENTS
|
|
|
|
Parse the task IDs to establish dependency relationship.
|
|
|
|
## Adding Dependencies
|
|
|
|
Creates a dependency where one task must be completed before another can start.
|
|
|
|
## Argument Parsing
|
|
|
|
Parse natural language or IDs:
|
|
- "make 5 depend on 3" → task 5 depends on task 3
|
|
- "5 needs 3" → task 5 depends on task 3
|
|
- "5 3" → task 5 depends on task 3
|
|
- "5 after 3" → task 5 depends on task 3
|
|
|
|
## Execution
|
|
|
|
```bash
|
|
task-master add-dependency --id=<task-id> --depends-on=<dependency-id>
|
|
```
|
|
|
|
## Validation
|
|
|
|
Before adding:
|
|
1. **Verify both tasks exist**
|
|
2. **Check for circular dependencies**
|
|
3. **Ensure dependency makes logical sense**
|
|
4. **Warn if creating complex chains**
|
|
|
|
## Smart Features
|
|
|
|
- Detect if dependency already exists
|
|
- Suggest related dependencies
|
|
- Show impact on task flow
|
|
- Update task priorities if needed
|
|
|
|
## Post-Addition
|
|
|
|
After adding dependency:
|
|
1. Show updated dependency graph
|
|
2. Identify any newly blocked tasks
|
|
3. Suggest task order changes
|
|
4. Update project timeline
|
|
|
|
## Example Flows
|
|
|
|
```
|
|
/project:tm/add-dependency 5 needs 3
|
|
→ Task #5 now depends on Task #3
|
|
→ Task #5 is now blocked until #3 completes
|
|
→ Suggested: Also consider if #5 needs #4
|
|
``` |