denolfe/dotfiles/task

New Task

This is the starting point of any new work. It facilitates the creation of a task directory and a 1-TASK.md file, which serves as the initial documentation for the task. The task file will contain a summary of the task, its objectives, and any relevant details.

Compute the task directory path, then run the script. If no argument is provided, use the current conversation to fill in the details.

1. task-name: hyphenated, lowercase, 2-4 words summarizing the argument (e.g., buggy-auth).
2. issue-number: deduce from argument or branch name (e.g., ECMS-12345). Omit if not applicable.
3. task-title: title-cased task-name, prefixed with issue-number if applicable (e.g., ECMS-12345: Buggy Auth).
4. project-dirname: basename of the current project directory (e.g., my-project).
5. folder: {YYYY-MM-DD}_{project-dirname}_{issue-number}-{task-name} (omit {issue-number}- if none).
6. task-dir: $HOME/.agents/plans/{folder}

Resolve this skill's directory as exposed by the host, then run its bundled task.sh script with "<task-dir>" "<task-title>".

The script creates the directory and 1-TASK.md, then outputs the path.

Once created:

1. Read and present 1-TASK.md contents
2. Ask the user to choose, noting which option is '(recommended)' based upon the details provided and task complexity:

• Research web
• Brainstorm design
• Add more detail
• Implement directly

1. Handle choice, also note which is '(recommended)' based upon task complexity:

• Brainstorm → Run superpowers-custom:brainstorming with this task directory as the task folder, present 1-TASK.md + 2-DESIGN.md
• Add details → Accept more input, merge into 1-TASK.md, return to step 2
• Implement directly → Implement directly
• Research → Ask topic, fetch, return to step 2