Skip to main content

/breakdown

Break a scope into one or more GitHub issues, each following the BeWith 6-section format with effort / urgency / domain labels picked by the AI.

What it doesโ€‹

Invokes the breakdown skill, which:

  1. Resolves the input โ€” ClickUp task ID, design doc path, or free-text description.
  2. Decides single-issue vs. multi-issue (asks one question if ambiguous).
  3. Drafts each issue body with the 6 sections (Summary ยท Goal ยท Implementation ยท Registration ยท Acceptance Criteria ยท Limitations ยท Related).
  4. Assigns labels โ€” effort:xs|s|m|l|xl ยท urgency:low|medium|high|critical ยท domain:*.
  5. Shows you the draft. Does not open issues without your approval.
  6. Opens the issues via gh issue create in one batch.
  7. Back-links to the ClickUp parent task with the resulting issue URLs.

Argumentsโ€‹

$ARGUMENTS โ€” the scope. Accepts:

  • A ClickUp task ID: /breakdown CU-86ca02ybf
  • A design doc path: /breakdown docs/designs/refresh-tokens-CU-123.md
  • A free-text description: /breakdown "rewrite the auth middleware to support refresh tokens"

If omitted, the skill asks for one.

When to skipโ€‹

  • Trivial change (one file, one hour): just open a PR, no issue needed.
  • No clear scope yet: write a proposal or design doc first.
  • Cross-team week-plus work: write an RFC first; break down after the RFC settles.

Cross-referencesโ€‹

  • Underlying skill: breakdown
  • Memory: project_gh_issue_format (the 6-section template + label vocabulary)
  • Memory: project_workflow_task_lifecycle (where this skill sits end-to-end)
  • docs/methodology/planning-docs.md โ€” design doc convention consumed when the input is a design path