Breakdown tasks skill

[trmartin4]

📔 Objective

Adds the next in a sequence of changes to decompose and enhance the existing writing-tech-breakdowns skill, for use with our new tech-breakdowns repo.

• Creating a new breakdown Breakdown initialization and spec definition skills #141
• Defining the Specification (the WHAT and WHY) Breakdown initialization and spec definition skills #141
• Defining the Plan (the HOW) Breakdown plan skill #143
• Defining the Tasks (this PR)
• Completing the breakdown (archiving to avoid ambiguous future references) Skill for completing tech breakdowns #148

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: APPROVE

This PR continues the decomposition of the tech-breakdown skills: it removes the two superseded skills (writing-tech-breakdowns, coordinating-cross-team-breakdown), adds the new decomposing-into-tasks skill, and updates all cross-references in developing-breakdown-spec, navigating-the-initiative-funnel, and the tech-lead AGENT.md. The breaking removals are correctly reflected in a major version bump of bitwarden-delivery-tools (1.5.0 → 2.0.0) with a matching changelog entry, and bitwarden-tech-lead gets a patch bump (2.3.1 → 2.3.2) for its reference updates. I verified no live references to the removed skills remain outside of historical CHANGELOG entries.

Code Review Details

• 🎨 : Acceptance Criteria format ordering reversed — should be GIVEN/WHEN/THEN (Gherkin), not GIVEN/THEN/WHEN
  • plugins/bitwarden-delivery-tools/skills/decomposing-into-tasks/SKILL.md:104

Notes on items checked and cleared:

• Version bumps and changelog entries are present and semantically correct (major bump for the breaking skill removals).
• No dangling references to the removed skills in any active SKILL.md, AGENT.md, README, or plugin.json — only in CHANGELOG history, which is correct.
• The new skill's use of AskUserQuestion/TaskCreate without listing them in allowed-tools matches the established convention of sibling breakdown skills.
• New cspell terms (duplicative, MECE, narratively) cover the vocabulary introduced.

[theMickster]

Couple minor thoughts for discussion; nothing blocking with those.

Let's fix up that changelog though

[trmartin4]

Had to address a merge conflict.

[theMickster]

Had to address a merge conflict.

Sorry! I think that was me merging in the work for the multi agent code review.