Skip to content
Skills Library
Programming · Automation

poseidon-implement

/poseidon-implement

Run the Poseidon implementation agent on a GitHub issue locally, in the current session, on the session model. Fetches the LIVE upstream implement instructions from a8cteam51/poseidon-actions each run (always up to date), reads the approved "### Poseidon plan" comment, implements on a fix/issue-N branch (Git Flow aware), lints, and opens the PR(s). Use when the user wants to implement an issue the Poseidon way or run poseidon implement locally. Examples - "/poseidon-implement 45", "/poseidon-implement a8cteam51/some-repo 45".

Licence
MIT
Last repository change
23.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 23.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run the Poseidon implementation agent on a GitHub issue locally, in the current session, on the session model. Fetches the LIVE upstream implement instructions from a8cteam51/poseidon-actions each run (always up to date), reads the approved "### Poseidon plan" comment, implements on a fix/issue-N branch (Git Flow aware), lints, and opens the PR(s). Use when the user wants to implement an issue the Poseidon way or run poseidon implement locally. Examples - "/poseidon-implement 45", "/poseidon-implement a8cteam51/some-repo 45".

Triggers from the description

### Poseidon plan

Arguments

/poseidon-implement [owner/repo] <issue>
Original author description

Run the Poseidon implementation agent on a GitHub issue locally, in the current session, on the session model. Fetches the LIVE upstream implement instructions from a8cteam51/poseidon-actions each run (always up to date), reads the approved "### Poseidon plan" comment, implements on a fix/issue-N branch (Git Flow aware), lints, and opens the PR(s). Use when the user wants to implement an issue the Poseidon way or run poseidon implement locally. Examples - "/poseidon-implement 45", "/poseidon-implement a8cteam51/some-repo 45".

How it works

  1. Inputs
  2. How it runs
Original SKILL.md headings · 103 lines, 860 words
SKILL.md preview
---
name: poseidon-implement
description: Run the Poseidon implementation agent on a GitHub issue locally, in the current session, on the session model. Fetches the LIVE upstream implement instructions from a8cteam51/poseidon-actions each run (always up to date), reads the approved "### Poseidon plan" comment, implements on a fix/issue-N branch (Git Flow aware), lints, and opens the PR(s). Use when the user wants to implement an issue the Poseidon way or run poseidon implement locally. Examples - "/poseidon-implement 45", "/poseidon-implement a8cteam51/some-repo 45".
argument-hint: "[owner/repo] <issue>"
---

# poseidon-implement

Local, in-session port of the Poseidon `issue-implement` agent. It does **not**
ship a copy of the Poseidon instructions — it **fetches them live** from
`a8cteam51/poseidon-actions@trunk` every run, so you always match the deployed
version. It then follows those instructions with a thin set of local overrides,
running on the model you've selected with no turn cap.

This ports the plain `issue-implement`, not `implement-v2` (the Pressable clone +
Playwright verification flow), which is tied to OpsOasis provisioning.

## Inputs

`$ARGUMENTS`: `45` or `a8cteam51/some-repo 45` (bare `N` resolves the repo from the
current directory).

Requires: the issue already has an approved `### Poseidon plan` comment (run
`/poseidon-plan` first); `gh` with access to `a8cteam51/poseidon-actions` (fetch)
and write access to the target repo (branches + PRs); and **the current directory
must be a clone of the target repo** (this agent creates branches, commits, and
pushes).

## How it runs

1. **Resolve** `OWNER/REPO` and issue number `N` from `$ARGUMENTS`. Confirm you are
   inside a clone of the target repo; if not, STOP and ask the user where their
   clone lives (or whether to clone it, and where) before continuing.

2. **Fetch the live upstream instructions:**
   ```bash
   mkdir -p /tmp/poseidon
   gh api repos/a8cteam51/poseidon-actions/contents/issue-implement/action.yml \
     -H "Accept: application/vnd.github.raw" > /tmp/poseidon/issue-implement.action.yml
   ```
   If this fails (e.g. 404 / no access), **STOP and tell the user** — do not fall
   back to remembered or guessed instructions.

3. **Read `/tmp/poseidon/issue-implement.action.yml`.** The *Run Claude Code*
   step carries TWO instruction blocks — extract and follow BOTH:
   - the `prompt:` input — the task itself (implement the plan, branch, PR),
     including the rule that newer post-plan human comments beat stale details
     in the plan;
   - the `--append-system-prompt "<PROMPT>"` value inside `claude_args` — your
     authoritative operating contract, **including its untrusted-input and
     production-read-only safety rules**.
   Read both in full and **follow them exactly**, with the local overrides
   below. You are NOT executing the YAML's steps; you only extract and follow
   those two embedded prompts. If the fetched file no longer matches this
   layout, find the embedded prompts wherever they now live, follow them, and
   tell the user the upstream layout changed.

4. **Apply these LOCAL overrides** (they win wherever they conflict with the
   upstream CI prompt):
   - **Environment:** you run locally in an interactive Claude Code session. Ignore
     the "no human in the loop / never ask" framing to the extent that you MAY ask
     the user when genuinely blocked. Your final text is your summary to the user
     (not a comment a workflow posts). The push/PR confirmation rule is step 5 below.
   - **Templating:** substitute the real issue number for
     `${{ steps.prep.outputs.issue }}` = `N` everywhere (branch names `fix/issue-N`,
     commit trailers, PR bodies), and the real title/body from
     `gh issue view N --repo OWNER/REPO --json title,body` for
     `${{ inputs.issue_title }}` / `${{ inputs.issue_body }}`. The upstream prompt
     expects `DEFAULT_BRANCH` and `HAS_DEVELOP` to be pre-set as env vars —
     compute them yourself instead:
     `DEFAULT_BRANCH = gh api repos/OWNER/REPO --jq .default_branch`, and
     `HAS_DEVELOP = true` iff `git ls-remote --heads origin develop` finds it. Use
     those values wherever the prompt references `$DEFAULT_BRANCH` / `$HAS_DEVELOP`.
   - **Plan source:** the upstream reads the pre-staged `/tmp/poseidon-plan.md`.
     Instead fetch it yourself: from `gh api repos/OWNER/REPO/issues/N/comments
     --paginate`, take the latest comment whose body starts with `### Poseidon plan`.
     If none exists, STOP and tell the user to run `/poseidon-plan` first.
     "Approved" locally means the user invoked this skill after reviewing that
     plan — but if multiple plan comments exist, or later human comments dispute
     or supersede the latest plan, confirm with the user which plan (and scope)
     to implement before writing code. The upstream's post-plan-comments file =
     comments created AFTER that plan comment, whose `user.type` is not `Bot`,
     and not themselves starting with `### Poseidon plan` — read those as newer,
     authoritative context.
   - **PR base branch:** in CI a plan-directed custom base branch travels via
     plumbing that doesn't exist locally. If the plan's *Branch / PR* (or
     *Constraints*) section EXPLICITLY names a target branch other than the
     default, cut `fix/issue-N` from that branch and open the primary PR against
     it. When the plan directs a single PR to only that branch, skip the develop
     cherry-pick flow; if it names a custom base but says nothing about develop
     and `HAS_DEVELOP` is true, ask the user whether the develop PR still
     applies. No explicit directive → normal `$DEFAULT_BRANCH` / `$HAS_DEVELOP` flow.
   - **MCP:** replace the OpsOasis `gateway` MCP (`mcp__gateway__load-provider` /
     `execute-tool`) with your local `team51` MCP — call `mcp__team51__wpcom_*` /
     `mcp__team51__pressable_*` directly for any verification lookups. If a tool is
     denied or unavailable, note it and continue.
   - **Ignore all CI plumbing:** run-tokens, OIDC, progress pings, cost telemetry,
     Node-toolchain auto-select, dependency pre-install, `poseidon-pr` labeling, and
     the `pr-review-fix` auto-chain. Install deps yourself before linting if needed.
   - **Output:** you create the branch/commits/PR(s) yourself as the upstream
     directs. Give your summary as your final message (it's fine to name/link the PRs
     you opened). Override any upstream line saying the workflow posts the summary or
     that you must not list PRs.

5. Because this pushes branches and opens PRs under **your** identity, confirm the
   diff with the user before the final `git push` / `gh pr create`, unless they
   told you to run unattended.

Versions

The database has no other skills named poseidon-implement.

Database snapshot: 13.11.2026 · package version f98ffebbbffe (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100poseidon-plan
    Run the Poseidon planning agent on a GitHub issue locally, in the current session, on the session model. Fetches the LIVE upstream plan instructions from a8cteam51/poseidon-actions each run (always up to date), reads the issue, gathers site context via the local team51 MCP, and…
  • 100implement-issue
    Read a GitHub issue, create a branch, implement the solution, and open a PR. Use when given an issue number to implement.
  • 100gh-issue-resolver
    Implement and verify a fix for a GitHub Issue whose response plan has already been posted as a comment by gh-issue-planner. Creates a feature branch, applies the agreed plan, runs tests, and opens a Pull Request. Use when the user asks to implement/fix/resolve a planned GitHub…
  • 84implement
    This skill should be used when the user asks to "implement an issue", "create a PR for issue", "implement issue #123", "turn this issue into code", or wants to implement a GitHub issue following an implementation plan and create a pull request.
  • 86build-feature
    Stage 3b (Build) - implement an approved plan.md on a feature branch in the app (the app in `<app.dir>/`, database in `<app.migrationsDir>`), commit, push and open a GitHub PR. Use only after plan.md is approved, or when the user says "build it", "implement the plan", or…
  • 90github-issue-autofix
    Implement a GitHub Issue fix on a branch and open a PR (Fixes #N). Use in conversation when the user gives an Issue number or URL and asks to implement or fix it. Also the L2 loop entry skill after autofix label, repository_dispatch, or workflow_dispatch. Interactive default is…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.