What is implement-issue?

A command for implementing one specified Linear issue in the mcp-for-argo-workflows project. Linear is a tool for tracking software tasks and issues.

Use it with an issue ID such as PIP-15 to inspect requirements, verify prerequisites, start work, and implement the issue.

It gathers the issue requirements, checks dependencies, creates the requested branch, and updates the issue's status during implementation.

How pipekit/mcp-for-argo-workflows configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to pipekit/mcp-for-argo-workflows. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/pipekit/mcp-for-argo-workflows/main/.claude/commands/implement-issue.md

Clone the repo

git clone --depth 1 https://github.com/pipekit/mcp-for-argo-workflows

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/pipekit/mcp-for-argo-workflows/implement-issue/github.svg)](https://agentmods.dev/commands/pipekit/mcp-for-argo-workflows/implement-issue)

Your own site

<a href="https://agentmods.dev/commands/pipekit/mcp-for-argo-workflows/implement-issue"><img src="https://agentmods.dev/badge/commands/pipekit/mcp-for-argo-workflows/implement-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/pipekit/mcp-for-argo-workflows/implement-issue"><img src="https://agentmods.dev/badge/commands/pipekit/mcp-for-argo-workflows/implement-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,466 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02466
Opus 5.5	$0.00000	$0.00986
Sonnet 5.5	$0.00000	$0.00493
Haiku 4.5	$0.00000	$0.00247

Measured 2mo ago against content hash ab3279207ce0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/implement-issue.md · 313 lines

How it starts

The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement Single Linear Issue

Implement a specific Linear issue for mcp-for-argo-workflows.

Usage

Provide the issue identifier (e.g., PIP-15) as an argument: /implement-issue PIP-15

The argument is: $ARGUMENTS

Step 1: Fetch Issue Details

Use mcp__linear-server__get_issue with the provided issue ID
Parse the issue description for:
- Tasks/requirements
- Tool schema (if MCP tool)
- Implementation notes
- Dependencies
- Acceptance criteria

Step 2: Check Dependencies

Identify dependencies from the issue description (usually listed at bottom)
Verify each dependency is complete:
- Check Linear status
- Verify code exists locally
If dependencies not met, report and stop

Step 3: Create Feature Branch

Create a branch for this issue using the Linear-suggested branch name:

git checkout main
git pull origin main
git checkout -b <branch-name-from-linear>

The branch name is provided in the Linear issue details as gitBranchName (e.g., alan/pip-10-implement-mcp-server-skeleton).

Step 4: Update Linear Status

Move issue to "In Progress":

mcp__linear-server__update_issue(id: "<issue-id>", state: "In Progress")

Step 5: Plan Agent Collaboration

Based on issue labels and content, determine which agents need to be involved:

Primary Implementation Agent

Label	Primary Agent
`setup`	`go-developer` or `ci-devops`
`mcp-tool`	`mcp-tool-implementer`
`testing`	`testing`
`docs`	`docs-examples`
`ci`	`ci-devops`

Supporting Agents (as needed)

testing - Write or update tests for the implementation
docs-examples - Update README, CLAUDE.md, or add examples
go-developer - Review Go code patterns and architecture
kubernetes-argo - Review Argo/K8s integration code

Agent Collaboration Patterns

Implementation + Testing: Primary agent implements, then testing agent adds/updates tests
Implementation + Docs: Primary agent implements, then docs-examples updates documentation
Implementation + Review: Primary agent implements, then another agent reviews for correctness
Full Pipeline: Implement → Test → Document → Review

Read the full file on GitHub · 313 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 313 lines · 0 tokens per session scan A ab3279207ce0

Subscribe to this mod's changes

implement-issue is a command published in the GitHub repository pipekit/mcp-for-argo-workflows (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,466 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

implement-issue next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
implement-issuepipekit/mcp-for-argo-workflows	Command	5	1mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

mcp-for-argo-workflows: Command for Claude Code