Relationships
#4807 Swampify: guide the last mile from built to everyday use (an adopted state)
Opened by skunk-ape · 11/16/2026· Shipped 11/16/2026
Part of Swampify. Follows #4714 (one build per session, hand back to the page) and #4755 (built only for accepted output), from a first build-brief run.
Repo: swamp (the bundled swampify skill: SKILL.md and references/handoff.md, plus an eval).
Problem
Swampify ends at "built and measured", but at that point the automation isn't used anywhere yet. In a run that built "Stage and commit changes" as a @swamp/git behavior (stage-and-commit), everything that made it usable day to day happened only because the user asked afterwards:
graduatedstops right after the build. After a build brief, the skill prints one directive line and stops, with no next steps. Nothing prompts wiring the build into the user's flow.- The build hard-codes its first-run target.
handoff.mdpushes toward one safe first run, so the agent wrote the scratch repo path and a demo author identity intoglobalArguments. The chore happens in many repos (842 times in 262 sessions), so the target needed to be aninputsfield (repoPath: ${{ inputs.repoPath }}). - Agents work outside the workspace. The user's agents run in their dev repos, not in the swampify workspace. Calling the behavior from there needs
--repo-dir/SWAMP_REPO_DIR, which the skill never mentions. - Agents are never told to use it. Without a rule in
CLAUDE.md/AGENTS.md(global or per repo), agents keep doing the chore by hand. - The adoption signal goes unused.
comparealready recordsforward.rawagainstforward.swamp, but the skill presents them only as numbers that fill in later.
Proposed solution
Add an adopted state between compared and graduated:
- Where the chore happens. Ask one question, seeded from the candidate's session paths (the repos or projects it showed up in). If there's more than one target, turn the fixed targets into behavior
inputsand test one run from outside the workspace with--repo-dir. - Remove first-run setup, such as scratch paths and demo identities, from the definition.
- Tell the agents. Offer to add a short rule with the exact command to the user's global or per-repo
CLAUDE.md(Claude Code) andAGENTS.md(Codex). Read the file first, write only on a yes, and leave each harness's attribution trailer as a placeholder. Mention aPreToolUsehook as an option for enforcing it, but don't push it. - After a kick-off or build brief: one short question ("Wire it into your agents? Where does this chore happen?"), then the same directive line as now. This keeps the page's one-build-per-session model.
- Later visit: if
forward.raw.occurrencesis still aboveforward.swamp.occurrences, revisit the wiring before suggesting the next option.
handoff.md: when a chore spans targets (repos, accounts, clusters), say to make those targets inputs, using the scratch target only for the first run.
Eval: a build-brief run ends with the adoption question before the directive line, and a multi-target chore ends up as a behavior with an inputs field.
Alternatives
- Leave it to the user to ask. That's what happened here, but most users won't think to.
- Have the Swampify page show copy-paste wiring snippets under Built. That helps, but the agent is better placed to edit the instruction files and check the result.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.