What is coding-pipeline?

An 11-stage coding process that moves from writing and checking a specification through planning, architecture, coding, testing, review, tuning, and deployment. It assigns these jobs to separate named agents.

Use it to take a software change from an initial specification through coding, quality review, stress testing, final judgment, and deployment.

It organizes software work into defined stages, making requirements, implementation, quality checks, and release tasks easier to follow.

coding-pipeline — Plugin by LuisFelipeMoro

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code

/plugin marketplace add LuisFelipeMoro/Harness-devkit

agentmods

npx agentmods add plugins/luisfelipemoro/harness-devkit/coding-pipeline

Clone the repo

git clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkit

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

coding-pipeline 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 2d 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.

plugins/coding-pipeline/.claude-plugin/plugin.json · 10 lines

What it actually says

{
  "name": "coding-pipeline",
  "version": "2.2.0",
  "description": "11-agent spec-first coding pipeline (Analyst \u2192 PM \u2192 Architect \u2192 ScrumMaster \u2192 Coder \u2192 QA \u2192 Reviewer \u2192 StressTester \u2192 Tuner \u2192 Verdict \u2192 DevOps)",
  "author": {
    "name": "Luis Moro"
  },
  "hooks": "./hooks/hooks.json"
}

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.

2d ago First seen · 10 lines scan A e0e26882b0a4

Subscribe to this mod's changes

coding-pipeline is a plugin published in the GitHub repository LuisFelipeMoro/Harness-devkit (10 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.

Code review Project management Testing

coding-pipeline

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

jira-assistant-skills

beans-prime

rook-claude

rook-maintainer

ai-skills

workbench