diff --git a/skills/brainstorming/SKILL.md b/skills/brainstorming/SKILL.md
index 2fd19ba1e..b7f6dd52c 100644
--- a/skills/brainstorming/SKILL.md
+++ b/skills/brainstorming/SKILL.md
@@ -52,3 +52,43 @@ Start by understanding the current project context, then ask questions one at a
 - **Explore alternatives** - Always propose 2-3 approaches before settling
 - **Incremental validation** - Present design in sections, validate each
 - **Be flexible** - Go back and clarify when something doesn't make sense
+
+---
+
+## Native Task Integration
+
+**REQUIRED:** Use Claude Code's native task tools (v2.1.16+) to create structured tasks during the design process.
+
+### During Design Validation
+
+After each design section is validated by the user, create a task:
+
+```yaml
+TaskCreate:
+  subject: "Implement [Component Name]"
+  description: |
+    [Key requirements from the design section]
+
+    Acceptance Criteria:
+    - [ ] [Criterion from design]
+    - [ ] [Criterion from design]
+  activeForm: "Implementing [Component Name]"
+```
+
+Track all task IDs for dependency setup.
+
+### After All Components Validated
+
+Set up dependency relationships:
+
+```yaml
+TaskUpdate:
+  taskId: [dependent-task-id]
+  addBlockedBy: [prerequisite-task-ids]
+```
+
+### Before Handoff
+
+Run `TaskList` to display the complete task structure with dependencies.
+
+Include task IDs in the design document for reference.
diff --git a/skills/writing-plans/SKILL.md b/skills/writing-plans/SKILL.md
index 448ca3193..5fb80f4ba 100644
--- a/skills/writing-plans/SKILL.md
+++ b/skills/writing-plans/SKILL.md
@@ -114,3 +114,72 @@ After saving the plan, offer execution choice:
 **If Parallel Session chosen:**
 - Guide them to open new session in worktree
 - **REQUIRED SUB-SKILL:** New session uses superpowers:executing-plans
+
+---
+
+## Native Task Integration
+
+**REQUIRED:** Use Claude Code's native task tools (v2.1.16+) to create structured tasks alongside the plan document.
+
+### Pre-Check
+
+Before creating tasks, check for existing tasks from brainstorming:
+
+```
+TaskList
+```
+
+If tasks exist: enhance descriptions with implementation details from the plan.
+If no tasks: create them as you write each plan task.
+
+### Creating Native Tasks
+
+For each task in the plan, create a corresponding native task:
+
+```
+TaskCreate:
+  subject: "Task N: [Component Name]"
+  description: |
+    **Files:**
+    - Create: `exact/path/to/file.py`
+    - Modify: `exact/path/to/existing.py:123-145`
+    - Test: `tests/exact/path/to/test.py`
+
+    [Full task content from plan]
+
+    **Acceptance Criteria:**
+    - [ ] Test exists and fails initially
+    - [ ] Implementation passes test
+    - [ ] Committed with descriptive message
+  activeForm: "Implementing [Component Name]"
+```
+
+### Setting Dependencies
+
+After all tasks created, set blockedBy relationships:
+
+```
+TaskUpdate:
+  taskId: [task-id]
+  addBlockedBy: [prerequisite-task-ids]
+```
+
+### During Execution
+
+Update task status as work progresses:
+
+```
+TaskUpdate:
+  taskId: [task-id]
+  status: in_progress  # when starting
+
+TaskUpdate:
+  taskId: [task-id]
+  status: completed    # when done
+```
+
+### Notes
+
+- Native tasks provide CLI-visible progress tracking
+- Plan document remains the permanent record
+- Tasks are session-scoped; re-run TaskCreate from plan for new sessions