intake

Classify user requests, estimate complexity, and route to harness pipelines.

1|Updated Mar 15, 2026

Search Tags:#automation #workflow #routing #orchestration #pipeline #harness #intake

Ready to run

npx skills add https://github.com/paulingham/.claude --skill intake-paulingham

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: intake
Source: https://github.com/paulingham/.claude/tree/main/skills/intake
Command: npx skills add https://github.com/paulingham/.claude --skill intake-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Entry point for all user requests. Classifies work type (feature, refactor, bug, spike, question), estimates complexity, determines pipeline entry point, and invokes /harness:pipeline. Use when receiving any new task from the user.

Core Features & Use Cases

Classifies work, estimates complexity, and routes to the appropriate pipeline or skill.
Provides a structured intake workflow including fingerprinting, risk assessment, build routing, contracts discovery, and pre-flight checks.
Supports both single-repo and multi-repo tasks and can trigger /harness:pipeline or sub-skills as needed.

Quick Start

Describe a task to intake and watch Claude classify it, estimate its complexity, and route it to the correct harness pipeline.

Frequently Asked Questions about intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate task routing to the right development pipeline?▼

Automating task routing involves classifying user requests, estimating complexity, and selecting the appropriate pipeline entry point. This intake workflow applies fingerprinting, risk assessment, and pre-flight checks to direct tasks to the correct execution pipeline.

What is the best way to classify software work types before execution?▼

Classifying software work types involves categorizing requests as features, bug fixes, refactors, technical spikes, or setup tasks. A structured intake process fingerprints the request and assesses risk to determine the correct build routing.

Can I route multi-repo tasks through a single intake workflow?▼

Yes, the intake workflow supports both single-repo and multi-repo tasks. It identifies contracts and performs pre-flight checks across the project scope before triggering the appropriate harness pipeline for execution.

Does automated intake work with feature requests and technical spikes?▼

Yes, automated intake handles feature requests, bug fixes, refactors, technical spikes, questions, and setup tasks. It estimates complexity for each work type and routes them to the matching harness pipeline.

Why do I need pre-flight checks before triggering a build pipeline?▼

Pre-flight checks are needed to validate risk assessments and contract identification before execution begins. They ensure the selected harness pipeline receives a properly fingerprinted and classified task request to prevent routing errors.