Skip to content

Conversation

@pcvelz
Copy link

@pcvelz pcvelz commented Jan 23, 2026

Integrate Claude Code v2.1.16 native task management tools (TaskCreate, TaskGet, TaskUpdate, TaskList) into the brainstorming and writing-plans skills, replacing TodoWrite with structured task tracking and dependency management.

Screenshot 2026-01-23 at 13 17 06

Changes:

  • brainstorming: Creates tasks during design validation with TaskCreate
  • writing-plans: Creates tasks with dependencies via TaskUpdate
  • README: Document native task management support with release link

Motivation and Context

Claude Code v2.1.16 (January 22, 2026) introduced native task management with dependency tracking. This provides significant advantages over the previous TodoWrite approach:

  • Tasks can have explicit dependencies (blockedBy relationships)
  • Individual task status tracking (pending/in_progress/completed)
  • Task ownership for multi-agent workflows
  • Structured execution order based on dependency graph

The brainstorming and writing-plans skills are natural candidates for this integration as they already generate task-like outputs during design and planning phases.

How Has This Been Tested?

  • Tested brainstorming skill: Verified tasks are created during design validation with proper descriptions
  • Tested writing-plans skill: Confirmed tasks with dependencies are created and TaskList shows correct structure
  • Verified TaskUpdate correctly sets blockedBy relationships between tasks
  • Tested execution handoff with subagent-driven development workflow

Breaking Changes

None. The skills maintain their original interfaces and behavior patterns. The change is internal to how tasks are stored and tracked.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

Additional context

This PR leverages Claude Code's native task management system released in v2.1.16. The native tasks are session-scoped (not persisted across sessions), so the plan document remains the permanent record.

Screenshot 2026-01-23 at 13 26 45

Summary by CodeRabbit

  • New Features
    • Integrated native task management tools into brainstorming and planning workflows.
    • Added structured task creation with subjects, descriptions, and acceptance criteria.
    • Introduced task dependency management to establish prerequisite relationships.
    • Added task status tracking during execution (in_progress, completed).
    • Enhanced visibility with complete task structure and dependency display.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Jan 23, 2026

Warning

Rate limit exceeded

@pcvelz has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 5 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📝 Walkthrough

Walkthrough

Two SKILL documentation files are updated to introduce "Native Task Integration" sections, establishing mandatory workflows for creating and managing structured tasks using Claude Code's native task tools (v2.1.16+). The brainstorming skill gains design-validation task workflows, while the writing-plans skill adds comprehensive task creation templates and lifecycle management instructions.

Changes

Cohort / File(s) Summary
Native Task Integration Documentation
skills/brainstorming/SKILL.md, skills/writing-plans/SKILL.md
Adds mandatory Native Task Integration sections with CloudCode task tool workflows (+43 and +69 lines respectively). Brainstorming skill introduces design-validation workflow with TaskCreate and dependency management via TaskUpdate. Writing-plans skill adds pre-check task inspection, detailed TaskCreate template, dependency setting block, task status lifecycle updates, and clarifying notes on CLI visibility and session scoping.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Hops through the docs with glee!
Tasks now structured, wild and free,
Native tools make workflows bright,
Dependencies linked just right,
Brainstorms and plans—chef's kiss—unite! 🎯✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'feat: add native task management support to brainstorming and writing-plans skills' accurately summarizes the main change, which is integrating Claude Code's native task management tools into two skills.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@README.md`:
- Around line 35-42: The README's example install commands reference marketplace
identifiers that must exactly match the fork's manifest; open the fork's
.claude-plugin/marketplace.json and confirm the "name" field value, then update
the README install lines (the `/plugin marketplace add pcvelz/superpowers` and
`/plugin install superpowers@pcvelz-superpowers` entries) to use that exact
marketplace slug, and also update the duplicate example at lines 51-52 so both
occurrences match the manifest.

@pcvelz pcvelz force-pushed the main branch 4 times, most recently from 2813a2b to 3a74b57 Compare January 23, 2026 13:36
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
README.md (1)

64-77: Correct the documented command names to match actual skills.

The README lists incorrect command names. The verification section shows /superpowers:brainstorm, /superpowers:write-plan, and /superpowers:execute-plan, but the actual skills are named brainstorming, writing-plans, and executing-plans. Update lines 75–77 to:

# /superpowers:brainstorming - Interactive design refinement
# /superpowers:writing-plans - Create implementation plan
# /superpowers:executing-plans - Execute plan in batches
🤖 Fix all issues with AI agents
In `@README.md`:
- Around line 27-29: Clarify in the README that TaskCreate, TaskUpdate, and
TaskList are fork-specific implementations used by this project's brainstorming
and writing-plans skills, not official Anthropic/Claude APIs; update the section
describing "Native Task Integration" to explicitly state that while Claude Code
v2.1.16+ introduces task concepts, the TaskCreate, TaskUpdate, and TaskList
functions referenced here are custom to this fork and not part of the documented
Claude API surface.

@pcvelz pcvelz force-pushed the main branch 4 times, most recently from 42820af to b546056 Compare January 23, 2026 14:35
@pcvelz
Copy link
Author

pcvelz commented Jan 23, 2026

Caution

Some comments are outside the diff and can't be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

README.md (1)

64-77: Correct the documented command names to match actual skills.

The README lists incorrect command names. The verification section shows /superpowers:brainstorm, /superpowers:write-plan, and /superpowers:execute-plan, but the actual skills are named brainstorming, writing-plans, and executing-plans.

This comment targets pre-existing code (lines 88-90) that was not changed in this PR.

Additionally, both forms are valid. Claude Code uses fuzzy matching for skill invocation - /superpowers:write-plan correctly loads the writing-plans skill.

No changes needed.

README.md Outdated


## Installation
## This Fork: Native Task Integration

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pcvelz "This fork" wording doesn't seem right

README.md Outdated

Then add marketplace, install, and enable (run each separately):
```bash
/plugin marketplace add https://github.com/pcvelz/superpowers

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pcvelz This doesn't seem right since this is going into obra's repo

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Fix all issues with AI agents
In `@README.md`:
- Line 60: Update the README heading "## Installation (Original)" to remove the
"(Original)" suffix so it reads "## Installation"; locate the header string "##
Installation (Original)" and change it to "## Installation" to avoid implying a
preferred alternative when the forked section is no longer separate.
- Around line 27-57: The "This Fork: Native Task Integration" section and its
fork-specific install commands (references: heading "This Fork: Native Task
Integration" and commands like "/plugin marketplace add
https://github.com/pcvelz/superpowers" and "/plugin install
superpowers@superpowers-dev") must be removed or rewritten for the main repo;
either delete the entire section or replace it with a neutral "Native Task
Integration" section that removes fork language, updates installation
instructions to the main repo's marketplace/package names, and removes the
uninstall/switch-back steps that reference pcvelz/superpowers and
superpowers-dev so the README documents native task features for the main
project instead of fork-specific workflows.

README.md Outdated
Comment on lines 27 to 57
## This Fork: Native Task Integration

This fork adds **Claude Code v2.1.16+ native task management** to the brainstorming and writing-plans skills. Tasks are created with `TaskCreate`, dependencies set with `TaskUpdate`, and progress tracked via `TaskList`.

### Installing This Fork

First, uninstall any existing superpowers (run whichever applies):
```bash
/plugin uninstall superpowers@claude-plugins-official
```
```bash
/plugin uninstall superpowers@superpowers-marketplace
```

Then add marketplace, install, and enable (run each separately):
```bash
/plugin marketplace add https://github.com/pcvelz/superpowers
```
```bash
/plugin install superpowers@superpowers-dev
```
```bash
/plugin enable superpowers@superpowers-dev
```

To switch back to the original:
```bash
/plugin uninstall superpowers@superpowers-dev
/plugin install superpowers@superpowers-marketplace
```

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Remove or rewrite fork-centric documentation for main repo context.

This PR targets obra/superpowers (the main repository), but this section documents installation from pcvelz/superpowers as if it were a separate fork. After merge:

  1. "This Fork" terminology is incorrect—this becomes the main repo
  2. Installation commands pointing to pcvelz/superpowers and superpowers-dev marketplace will confuse users
  3. The uninstall/switch-back instructions reference switching between fork and original, which won't make sense

Consider either:

  • Remove this section entirely if native task integration should be the default behavior
  • Rewrite for main repo by removing fork references and updating the main installation section (lines 64-76) to document the native task features instead
🤖 Prompt for AI Agents
In `@README.md` around lines 27 - 57, The "This Fork: Native Task Integration"
section and its fork-specific install commands (references: heading "This Fork:
Native Task Integration" and commands like "/plugin marketplace add
https://github.com/pcvelz/superpowers" and "/plugin install
superpowers@superpowers-dev") must be removed or rewritten for the main repo;
either delete the entire section or replace it with a neutral "Native Task
Integration" section that removes fork language, updates installation
instructions to the main repo's marketplace/package names, and removes the
uninstall/switch-back steps that reference pcvelz/superpowers and
superpowers-dev so the README documents native task features for the main
project instead of fork-specific workflows.

README.md Outdated

---

## Installation (Original)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Remove "(Original)" label if this becomes the main installation path.

The "(Original)" suffix implies there's a preferred alternative (the fork section above). If the fork section is removed or integrated, this should simply be "## Installation".

🤖 Prompt for AI Agents
In `@README.md` at line 60, Update the README heading "## Installation (Original)"
to remove the "(Original)" suffix so it reads "## Installation"; locate the
header string "## Installation (Original)" and change it to "## Installation" to
avoid implying a preferred alternative when the forked section is no longer
separate.

@pcvelz pcvelz force-pushed the main branch 2 times, most recently from b546056 to 316ea9d Compare January 24, 2026 13:43
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@skills/brainstorming/SKILL.md`:
- Around line 66-88: The fenced code blocks for the TaskCreate and TaskUpdate
YAML snippets are missing language tags (MD040); update the two triple-backtick
blocks surrounding the TaskCreate and TaskUpdate examples to use ```yaml so the
blocks are correctly recognized as YAML—specifically modify the block that
starts before TaskCreate and the block that starts before TaskUpdate (referenced
by the TaskCreate and TaskUpdate example headers) to include the language
specifier.
🧹 Nitpick comments (1)
skills/brainstorming/SKILL.md (1)

64-83: Use headings instead of bold labels.

The bolded labels are being used as headings, which triggers MD036. Consider converting them to proper subheadings for readability and lint compliance.

♻️ Suggested change
-After each design section is validated by the user, create a task:
+#### After each design section is validated by the user, create a task
@@
-Track all task IDs for dependency setup.
+#### Track all task IDs for dependency setup
@@
-Set up dependency relationships:
+#### Set up dependency relationships

…ing-plans

Integrate Claude Code v2.1.16+ native task management tools into the
brainstorming and writing-plans skills.

Changes:
- brainstorming: Creates tasks during design validation with TaskCreate,
  sets dependencies with TaskUpdate after all components validated
- writing-plans: Creates tasks for each plan step, tracks dependencies,
  updates status during execution

Native task tools used: TaskCreate, TaskGet, TaskUpdate, TaskList
@obra
Copy link
Owner

obra commented Jan 24, 2026

I appreciate the submission, but don't plan to be taking this at this time. Claude is very good at using those tools on its own as it is executing a plan, but I believe strongly that we should have durable artifacts from the planning process. On top of that, Cibra Powers works with platforms that are not just Claude code.

@obra obra closed this Jan 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants