Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

issue-lifecycle models should support --assignee for swamp.club issues

Opened by keeb · 4/11/2026· Shipped 4/12/2026

Problem

When using the issue-lifecycle skill/models to triage and work on swamp.club Lab issues, there is no way to assign the issue to a user as part of the lifecycle flow. Assignment has to be done out-of-band (via the web UI or a separate API call), which breaks the otherwise smooth CLI-driven workflow.

Proposed Solution

Add an `--assignee` flag to the issue-lifecycle model methods that interact with swamp.club issues, so an issue can be claimed/assigned as part of triage or plan iteration. It should accept a swamp.club username and set the assignee on the target issue.

Alternatives

  • Assign via the swamp.club web UI after running the lifecycle flow (current workaround — context-switchy).
  • Add a separate `swamp issue assign` command (useful generally, but doesn't solve the lifecycle integration).

Context

Came up while driving swamp.club issues through the issue-lifecycle skill — wanted to claim an issue during triage without leaving the CLI.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPEDTRIAGE+ 6 MOREREVIEW+ 3 MOREPR_MERGEDSHIPPED

Shipped

4/12/2026, 12:05:49 AM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack724/11/2026, 11:27:44 PM

Sign in to post a ripple.