prd-pipeline

prd-pipeline is a skill for Claude Code from hamzaPixl/pixl-ai. It costs 87 tokens per session (1,890 once invoked), scanned A, original, MIT.

An automated workflow that takes a product requirements document (PRD) through planning, implementation, quality checks, and pull-request creation across multiple sessions.

In plain words
What is it for?
Use it to decompose a PRD, plan tasks and sprints, implement the work, run quality gates, and create a pull request from the finished changes.
Why use it?
It preserves progress and decisions between sessions, so a long project can resume without starting the planning process again.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Part of the pixl-crew plugin — 93 skills, 14 agents, 6 hooks shipped together

Good fit Use it to decompose a PRD, plan tasks and sprints, implement the work, run quality gates, and create a pull request from the finished changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hamzapixl/pixl-ai/prd-pipeline
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.

Any agent
npx skills add hamzaPixl/pixl-ai --skill prd-pipeline
Clone the repo
git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

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.

agentmods badge for prd-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/prd-pipeline/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/prd-pipeline)
Your own site
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/prd-pipeline"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/prd-pipeline/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.

agentmods 80×15 button for prd-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/prd-pipeline"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/prd-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,890 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00087 $0.01890
Opus 5.5 $0.00035 $0.00756
Sonnet 5.5 $0.00017 $0.00378
Haiku 4.5 $0.00009 $0.00189

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

Security

Grade A, and why

prd-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 1mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/run-prd.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

packages/crew/skills/prd-pipeline/SKILL.md · 135 lines

How it starts

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

Overview

Orchestrates a PRD-to-production pipeline by composing existing pixl-crew skills across multiple sessions. Each phase persists state to a pipeline state file so the next session can resume without replanning. The session-start.sh hook auto-injects prior session summaries and decisions on restart.

A scope guard hook (prd-pipeline-scope-guard) activates automatically when pipeline-state.json is present — it blocks accidental writes to critical infrastructure files (CI workflows, .env, Makefile, docker-compose, package manifests, CLAUDE.md) during autonomous execution. Set PIXL_PIPELINE_BYPASS=1 to override.

Mode Detection

Input pipeline-state.json exists? Mode
File path or URL No Init — start new pipeline
File path or URL Yes Reset — restart pipeline with new PRD
resume or no argument Yes Resume — continue from last phase
No argument No Error — ask for PRD path

Pipeline State

Track progress in a pipeline-state.json file committed alongside the project:

{
  "version": "1.0",
  "started_at": "ISO timestamp",
  "updated_at": "ISO timestamp",
  "prd_source": "<path to canonical PRD>",
  "current_phase": "planning",
  "phases": {
    "setup": { "status": "completed", "started_at": "...", "completed_at": "..." },
    "planning": { "status": "in_progress", "started_at": "..." },
    "foundation": { "status": "pending" },
    "implementation": { "status": "pending" },
    "quality": { "status": "pending" },
    "delivery": { "status": "pending" },
    "finalization": { "status": "pending" }
  },
  "sprints_completed": 0,
  "total_sprints": 4,
  "coverage_percentage": 0.0,
  "branch": "feat/prd-implementation"
}

Phases

Phase 0: Setup

Goal: Bootstrap the pipeline workspace and verify the project is buildable and testable. Inputs: PRD file path or URL. Outputs: Canonical PRD stored in the project context directory, pipeline-state.json initialized, test command verified. Constraints: PRD must be readable before proceeding. The project must have a discoverable test command. Suggest scoped permission wildcards via AskUserQuestion if none are configured.

Read the full file on GitHub · 135 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 1mo ago First seen · 135 lines · 87 tokens per session scan A 5b71352aca4d

Subscribe to this mod's changes

prd-pipeline is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 87 tokens to every session and 1,890 once invoked, about $0.0003 per session on Opus 5.5. 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-09-03.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens