feat(claude): update working with superpowers, add task and implement-plan commands

Author: denolfe

claude/CLAUDE.md

@@ -5,7 +5,27 @@
 
 # Working with superpowers plugin
 
-- When using `superpowers` skills, if directed to write to `docs/plans`, instead write to `~/.claude/plans` instead. This is to avoid cluttering the main repository with temporary plan files that will not be kept or committed.
+- When using `superpowers` skills, if directed to write to `docs/plans`, instead write to `~/.claude/plans`. This is to avoid cluttering the main repository with temporary plan files that will not be kept or committed.
+- The files should be written in the following tree structure:
+
+  ```
+  ~/.claude/plans/
+    ├── `{timestamp}-{task-name}`/ # Each task in its own timestamped folder
+    │     ├── 1-TASK.md # This is the main task description or details provided to brainstorming skill
+    │     ├── 2-DESIGN.md # This is the resulting design file from the `superpowers:brainstorming` skill
+    │     ├── 3-PLAN.md # This is the output of `superpowers:writing-plans` skill
+    │     └── ...
+    └── another-task/
+          ├── 3-PLAN.md
+          └── ...
+  ```
+
+- `superpowers:brainstorming` skill should:
+  - Write the provided prompt and context to `1-TASK.md`
+  - Generate a structured plan and write to `2-DESIGN.md`. Add all clarifying questions asked during brainstorming to the end of the `2-DESIGN.md` file.
+- `superpowers:writing-plans` skill should:
+  - Read the `2-DESIGN.md` file from the respective plan folder
+  - Write the resulting implementation details to `3-PLAN.md` in the same folder.
 
 # Coding Patterns and Best Practices (Typescript)
 

claude/commands/implement-plan.md

@@ -0,0 +1,11 @@
+---
+description: Implement the PLAN.md file for a specific plan or feature development
+---
+
+Implement the plan:
+
+- **REQUIRED SUB-SKILL:** Use superpowers:subagent-driven-development
+- Dispatch a fresh subagent per task
+- Do code review between tasks using `superpowers:code-reviewer`
+- Quickly iterate until done
+- Group tasks if it makes sense for code review purposes

claude/commands/task.md

@@ -0,0 +1,30 @@
+---
+description: Create a new task file for a specific task or feature development
+argument-hint: <task-name-or-desc>
+allowed-commands: Write, Bash(mkdir:*), Bash(mkdir -p:*)
+---
+
+# New Task
+
+- Create the following structure in `~/.claude/plans/`:
+
+  ```
+  ~/.claude/plans/
+    ├── `{timestamp}-{task-name}`/ # Each task in its own timestamped folder
+    │     ├── 1-TASK.md # This is the main task description or details provided to brainstorming skill
+    │     └── ...
+    └── another-task/
+          ├── 1-TASK.md
+          └── ...
+  ```
+
+- The task-name should be a short, hyphenated version of the provided task name or description argument (e.g., "implement-authentication", "refactor-database-layer"). Be concise and summarize if necessary.
+- Create the directory with `mkdir -p ~/.claude/plans/$(date +%Y-%m-%d)-task-name` but replace `task-name` with the hyphenated version of the provided task name or description.
+- 1-TASK.md should contain a single H1 header with the provided task name or description.
+
+Once created:
+
+- Present the 1-TASK.md contents
+- AskUserQuestion:
+  - Add details to task?
+  - Brainstorm design using `superpowers:brainstorming`?