@swamp/issue-lifecycle
v2026.04.22.2
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 ──[link_pr]──> pr_open
pr_open ──[link_pr]──> pr_open (idempotent re-link)
pr_open ──[complete]──> done
implementing ──[complete]──> done (legacy, no PR linked)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 typeplan— generate an implementation planreview— display the current plan (read-only)iterate— revise the plan with feedback (versioned)adversarial_review— record adversarial review findingsresolve_findings— mark adversarial findings as resolvedapprove— lock the plan and transition to in_progressimplement— signal implementation has startedlink_pr— link an opaque pull request URL to the lifecycle record (idempotent; transitions topr_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_KEYenv var (orswamp auth login) for swamp-club access- The target lab issue must already exist in swamp-club
Repository
https://github.com/systeminit/swamp-extensions
Labels
Quality score
Verified by SwampHow well-documented and verifiable this extension is.
Grade A
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types1/1earned
- Has description1/1earned
- At least one platform tag (or universal)1/1earned
- Two or more platform tags (or universal)1/1earned
- License declared1/1earned
- Verified public repository2/2earned
Install
$ swamp extension pull @swamp/issue-lifecycleSecurity Notice
This extension includes AI agent skills that can modify AI assistant behavior. Review the skill files before installing.
| Argument | Type | Description |
|---|---|---|
| confidence | enum | |
| reasoning | string | |
| isRegression? | boolean | True if this is a regression (something that previously worked). Implies type=bug. |
| clarifyingQuestions? | array |
| Argument | Type | Description |
|---|---|---|
| summary | string | |
| dddAnalysis | string | |
| steps | array | |
| testingStrategy | string | |
| potentialChallenges | array |
| Argument | Type | Description |
|---|---|---|
| version? | number | Specific plan version to review |
| Argument | Type | Description |
|---|---|---|
| feedback | string | Human feedback on the current plan |
| summary | string | |
| dddAnalysis | string | |
| steps | array | |
| testingStrategy | string | |
| potentialChallenges | array |
| Argument | Type | Description |
|---|---|---|
| findings | array |
| Argument | Type | Description |
|---|---|---|
| resolutions | array |
| Argument | Type | Description |
|---|---|---|
| url | string | Canonical pull request URL. Opaque to the model — pass whatever |
| Argument | Type | Description |
|---|---|---|
| mergedAt? | string | ISO-8601 timestamp of when the PR was merged. Defaults to now. |
| Argument | Type | Description |
|---|---|---|
| reason | string | Why the PR failed: CI failure details, review rejection reason, etc. |
| Argument | Type | Description |
|---|---|---|
| releaseUrl? | string | URL of the release (e.g., GitHub release page, package registry). Optional. |
| releaseNotes? | string | Brief release notes or summary. Optional. |
Resources
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 ──[link_pr]──> pr_open pr_open ──[link_pr]──> pr_open (idempotent re-link) pr_open ──[complete]──> done implementing ──[complete]──> done (legacy, no PR linked) ``` 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
Changelog
Models
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 ──[link_pr]──> pr_open pr_open ──[link_pr]──> pr_open (idempotent re-link) pr_open ──[complete]──> done implementing ──[complete]──> done (legacy, no PR linked) ``` 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
Changelog
Models
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 ──[complete]──> 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. ## 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 - `complete` — mark the lifecycle done ## Data All resources are versioned and immutable: `state`, `context`, `classification`, `plan`, `feedback`, `adversarialReview`. ## 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
Changelog
Models
Interactive GitHub issue triage and implementation planning. Moves the triage/plan/iterate/approve/implement loop out of GitHub Actions and into a local conversation with Claude, while keeping the GitHub issue thread up to date as a live status dashboard. ## 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 ──[ci_status]──> ci_review ci_review ──[fix]──> implementing (fix loop) ci_review ──[complete]──> 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. ## Methods - `start` — fetch issue context from GitHub - `triage` — classify as bug/feature/unclear - `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 post it to the issue - `implement` — signal implementation has started - `record_pr` — record the PR number for CI tracking - `ci_status` — fetch CI check results and review comments - `fix` — direct specific fixes from review feedback - `complete` — mark the lifecycle done ## Data All resources are versioned and immutable: `state`, `context`, `classification`, `plan`, `feedback`, `adversarialReview`, `ciResults`, `fixDirective`. ## Prerequisites - `gh` CLI installed and authenticated (`gh auth login`) - swamp initialized in the repository (`swamp init`) - (Optional) `SWAMP_API_KEY` env var to mirror lifecycle entries to [swamp.club](https://swamp.club)