claude-pipeline: Skill for Claude Code

Adapting Claude Pipeline to a Codebase

Overview

Adapt the generic .claude/ pipeline folder to a specific project's tech stack, domain, and workflows. This means modifying, replacing, or removing every skill, agent, hook, script, prompt, and setting so they serve the target codebase — not the original Laravel/web template.

Core principle: Every file in .claude/ must earn its place. If it doesn't serve the target project, delete it. If it needs modification, modify it. If new capabilities are needed, create them.

When to Use

• Cloning the claude-pipeline repo into a new project
• Onboarding an existing codebase with the generic .claude/ folder
• Switching tech stacks (e.g., Laravel to Python, web to CLI, monolith to microservices)

The Process

digraph adaptation {
    rankdir=TB;

    "1. Brainstorm with user" [shape=box style=filled fillcolor=lightyellow];
    "2. Research domain patterns" [shape=box];
    "3. Audit existing .claude/ inventory" [shape=box];
    "4. Write adaptation plan" [shape=box];
    "5. Execute plan with subagents" [shape=box style=filled fillcolor=lightblue];
    "6. Verify adapted pipeline" [shape=box style=filled fillcolor=lightgreen];

    "1. Brainstorm with user" -> "2. Research domain patterns";
    "2. Research domain patterns" -> "3. Audit existing .claude/ inventory";
    "3. Audit existing .claude/ inventory" -> "4. Write adaptation plan";
    "4. Write adaptation plan" -> "5. Execute plan with subagents";
    "5. Execute plan with subagents" -> "6. Verify adapted pipeline";
}

---

Phase 1: Brainstorm

REQUIRED: Use the brainstorming skill to explore the target project.

Focus questions on:

• Tech stack: Language, framework, database, infrastructure
• Project type: Web app, CLI tool, library, API, microservice, data pipeline, etc.
• Team workflows: CI/CD, code review, deployment, testing patterns
• Pain points: What does the team struggle with that agents could help?
• Existing tooling: Linters, formatters, test runners, build systems
• Scope: Full adaptation or partial (e.g., keep orchestration, replace agents)?