soloscrum

Breaks a GitHub Issue into Subtasks with type (develop or design-ui) and story points. Proposes the breakdown for confirmation, then registers each Subtask via the active tracker profile's operation skill.

Designs a Subtask of type design-ui in Figma with tokens, components, and state flows. Transitions the Subtask to In Review on completion.

Implements a develop work unit — either a Subtask or a no-Subtask Issue (per soloscrum-define-branch-commit's case-split). Creates a branch, writes code and tests, generates a PR, and transitions the target to In Review.

Recommends the next action based on backlog and active-work state — continues in-progress work, suggests review, starts the next subtask, or prompts to refine a new idea.

Structures an idea into a GitHub Issue. Runs a backlog janitor first (closes stale Issues whose closing PR has merged), then checks size, suggests splitting when too large, determines priority and SP, and creates the Issue after confirmation.

Design agent. Validates feature design, plans subtask decomposition, assigns task types. Use during /validate and /breakdown commands.

Development agent. Decomposes Issues into Subtasks via the active tracker profile (during /breakdown), and implements code / creates PRs / transitions state for the /develop target (Subtask or no-Subtask Issue per soloscrum-define-branch-commit). Use during /breakdown and /develop commands.

Product Owner agent. Structures ideas into GitHub Issues, evaluates size, determines priority and SP. Use during /refine command.

Review agent. Reviews PR code quality, verifies DoD with layered AC check (Subtask PR vs Issue-without-Subtasks vs parent Issue intent-level sign-off per soloscrum-define-dod), makes Pass/Fail verdict. Use during /review command.

UI agent. Creates Figma components, applies design tokens, maintains UI pattern consistency. Use during /design-ui command.

Structures an idea into a GitHub Issue with Background, Goal, AC, and Out of Scope. Checks issue size, suggests splitting if over threshold, and determines priority and story points. Profile-agnostic.

Reference: which agent or command creates, transitions, and verifies each soloscrum concept (Issue, Subtask, SP, type, priority, state, branch, PR, etc.). Tracker-profile-independent — use together with soloscrum-define-tracker-profile.

Reference: branch naming ({type}/{issue-id}-{slug}, where issue-id is the Subtask or no-Subtask Issue), Conventional Commits, and parent Issue close convention (per-Subtask PRs close only the Subtask; parent closes via /refine janitor). Repo-specific strategy in .claude/rules/branch.md takes precedence.

Reference: standard code review pipeline (CodeRabbit + multi-agent review) and the per-finding decision rules. Severity and confidence scores are inputs to a per-item decision, NOT auto-skip filters. Every CodeRabbit finding is surfaced and judged individually; only agent-generated findings have an additional confidence pre-filter to suppress hallucinations.

Reference: criteria for validating feature design across scope clarity (Goal and AC alignment), dependency identification, and technical feasibility against the project stack.