create-tasklisted

# Create Task Skill Takes arbitrary text input — feature specs, meeting notes, brainstorm lists, bug reports, requirements docs — and decomposes it into structured, deduplicated tasks in the tusk database. ## Step 1: Capture Input The user provides freeform text after `/create-task`. This could be: - A feature description or requirements list - Meeting notes or brainstorm output - A bug report or incident summary - A pasted document or spec - A simple one-liner for a single task If the user didn't provide any text after the command, ask: > What would you like to turn into tasks? Paste any text — feature specs, meeting notes, bug reports, requirements, etc. ## Step 2: Fetch Config and Backlog Fetch everything needed for analysis in a single call: ```bash tusk setup ``` This returns a JSON object with two keys: - **`config`** — full project config (domains, task_types, agents, priorities, complexity, etc.). Store for use when assigning metadata. If a field is an empty list (e.g., `"domains": []`), that field has no validation — use your best judgment or leave it NULL. - **`backlog`** — all open tasks as an array of objects. Hold in context for Step 3. The heuristic dupe checker (`tusk dupes check`) catches textually similar tasks, but you can catch **semantic** duplicates that differ in wording — e.g., "Implement password reset flow" vs. existing "Add forgot password endpoint" — which the heuristic would miss. ## Step 2.5: Bundled-Scope Pre-Check Before drafting task