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
76 lines
1.7 KiB
Markdown
76 lines
1.7 KiB
Markdown
Add a subtask to a parent task.
|
|
|
|
Arguments: $ARGUMENTS
|
|
|
|
Parse arguments to create a new subtask or convert existing task.
|
|
|
|
## Adding Subtasks
|
|
|
|
Creates subtasks to break down complex parent tasks into manageable pieces.
|
|
|
|
## Argument Parsing
|
|
|
|
Flexible natural language:
|
|
- "add subtask to 5: implement login form"
|
|
- "break down 5 with: setup, implement, test"
|
|
- "subtask for 5: handle edge cases"
|
|
- "5: validate user input" → adds subtask to task 5
|
|
|
|
## Execution Modes
|
|
|
|
### 1. Create New Subtask
|
|
```bash
|
|
task-master add-subtask --parent=<id> --title="<title>" --description="<desc>"
|
|
```
|
|
|
|
### 2. Convert Existing Task
|
|
```bash
|
|
task-master add-subtask --parent=<id> --task-id=<existing-id>
|
|
```
|
|
|
|
## Smart Features
|
|
|
|
1. **Automatic Subtask Generation**
|
|
- If title contains "and" or commas, create multiple
|
|
- Suggest common subtask patterns
|
|
- Inherit parent's context
|
|
|
|
2. **Intelligent Defaults**
|
|
- Priority based on parent
|
|
- Appropriate time estimates
|
|
- Logical dependencies between subtasks
|
|
|
|
3. **Validation**
|
|
- Check parent task complexity
|
|
- Warn if too many subtasks
|
|
- Ensure subtask makes sense
|
|
|
|
## Creation Process
|
|
|
|
1. Parse parent task context
|
|
2. Generate subtask with ID like "5.1"
|
|
3. Set appropriate defaults
|
|
4. Link to parent task
|
|
5. Update parent's time estimate
|
|
|
|
## Example Flows
|
|
|
|
```
|
|
/project:tm/add-subtask to 5: implement user authentication
|
|
→ Created subtask #5.1: "implement user authentication"
|
|
→ Parent task #5 now has 1 subtask
|
|
→ Suggested next subtasks: tests, documentation
|
|
|
|
/project:tm/add-subtask 5: setup, implement, test
|
|
→ Created 3 subtasks:
|
|
#5.1: setup
|
|
#5.2: implement
|
|
#5.3: test
|
|
```
|
|
|
|
## Post-Creation
|
|
|
|
- Show updated task hierarchy
|
|
- Suggest logical next subtasks
|
|
- Update complexity estimates
|
|
- Recommend subtask order |