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
49 lines
1.0 KiB
Markdown
49 lines
1.0 KiB
Markdown
Parse a PRD document to generate tasks.
|
|
|
|
Arguments: $ARGUMENTS (PRD file path)
|
|
|
|
## Intelligent PRD Parsing
|
|
|
|
Analyzes your requirements document and generates a complete task breakdown.
|
|
|
|
## Execution
|
|
|
|
```bash
|
|
task-master parse-prd --input=$ARGUMENTS
|
|
```
|
|
|
|
## Parsing Process
|
|
|
|
1. **Document Analysis**
|
|
- Extract key requirements
|
|
- Identify technical components
|
|
- Detect dependencies
|
|
- Estimate complexity
|
|
|
|
2. **Task Generation**
|
|
- Create 10-15 tasks by default
|
|
- Include implementation tasks
|
|
- Add testing tasks
|
|
- Include documentation tasks
|
|
- Set logical dependencies
|
|
|
|
3. **Smart Enhancements**
|
|
- Group related functionality
|
|
- Set appropriate priorities
|
|
- Add acceptance criteria
|
|
- Include test strategies
|
|
|
|
## Options
|
|
|
|
Parse arguments for modifiers:
|
|
- Number after filename → `--num-tasks`
|
|
- `research` → Use research mode
|
|
- `comprehensive` → Generate more tasks
|
|
|
|
## Post-Generation
|
|
|
|
After parsing:
|
|
1. Display task summary
|
|
2. Show dependency graph
|
|
3. Suggest task expansion for complex items
|
|
4. Recommend sprint planning |