Issue Lifecycle

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.

State Machine

created ──[start]──> triaging
triaging ──[triage]──> classified
classified ──[plan]──> plan_generated
plan_generated ──[iterate]──> plan_generated  (feedback loop)
plan_generated ──[approve]──> approved
approved ──[implement]──> implementing
implementing ──[verify]──> verifying
verifying ──[verification_passed]──> verifying  (record results)
verifying ──[verification_failed]──> implementing  (fix and retry)
verifying ──[post_attestation]──> verifying  (post to swamp-club)
verifying ──[link_pr]──> pr_open
pr_open ──[link_pr]──> pr_open  (idempotent re-link)
pr_open ──[pr_failed]──> pr_failed
pr_failed ──[link_pr]──> pr_open  (retry with new PR)
pr_failed ──[implement]──> implementing  (restart implementation)
pr_open ──[pr_merged]──> releasing
releasing ──[ship]──> notify
implementing ──[complete]──> notify  (no PR linked)
pr_open ──[complete]──> notify
releasing ──[complete]──> notify
notify ──[notify]──> summarizing  (thank external contributor)
notify ──[skip_notify]──> summarizing  (skip notification)
summarizing ──[summarize]──> done

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. start can resume from any phase except done. complete accepts implementing, pr_open, and releasing as source phases.

Methods

• start — fetch issue context from swamp-club (fails if the issue does not exist); auto-assigns the current user
• triage — classify as bug/feature/platform/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
• verify — start pre-PR verification (transitions to verifying)
• verification_passed — record that verification passed with full checklist
• verification_failed — record failure, return to implementing
• post_attestation — post verification attestation to swamp-club (hard gate)
• 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.
• pr_merged — record that the linked PR was merged (transitions to releasing)
• pr_failed — record that the linked PR failed (transitions to pr_failed; can retry via link_pr or implement)
• ship — mark as shipped/released (transitions to notify)
• complete — mark the lifecycle complete (transitions to notify)
• notify — post a thank-you ripple to the issue author and transition to summarizing
• skip_notify — skip contributor notification and transition to summarizing
• summarize — record session summary and transition to done

Data

All resources are versioned and immutable: state, context, classification, plan, feedback, adversarialReview, codeConformanceReview, verificationResult, attestation, pullRequest, summary.

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