Interactive triage and implementation planning for swamp-club lab issues.
Drives the triage/plan/iterate/approve/implement loop as a local
conversation with Claude, while posting structured lifecycle entries and
status transitions back to the swamp-club issue on every step.
The model operates directly on swamp-club lab issue numbers — the issue
must already exist in swamp-club before you start. There is no GitHub
integration.
Pre-flight checks enforce valid transitions: you cannot approve without a
plan, cannot implement without approval, and cannot approve while critical
or high adversarial findings remain unresolved. complete accepts both
implementing and pr_open as source phases so legacy records (created
before link_pr existed) can still reach done.
Methods
start — fetch issue context from swamp-club (fails if the issue does
not exist)
triage — classify as bug/feature/security and PATCH the swamp-club
issue type
plan — generate an implementation plan
review — display the current plan (read-only)
iterate — revise the plan with feedback (versioned)
adversarial_review — record adversarial review findings
resolve_findings — mark adversarial findings as resolved
approve — lock the plan and transition to in_progress
implement — signal implementation has started
link_pr — link an opaque pull request URL to the lifecycle record
(idempotent; transitions to pr_open). Git-host agnostic — the model
persists whatever URL the agent supplies without fetching anything.
complete — mark the lifecycle done
Data
All resources are versioned and immutable: state, context,
classification, plan, feedback, adversarialReview, pullRequest.
Prerequisites
swamp initialized in the repository (swamp init)
SWAMP_API_KEY env var (or swamp auth login) for swamp-club access
The target lab issue must already exist in swamp-club