/skill-pipeline
Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills at the right depth. Implements two feedback loops: the inner loop (detect, verify, recover) runs within a session via plan-interview, intent-framed-agent,
$ npx -y skills add pskoett/pskoett-ai-skills --skill skill-pipeline --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/skill-pipeline
Context preview
The summary Claude sees to decide when to auto-load this skill.
Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills at the right depth. Implements two feedback loops: the inner loop (detect, verify, recover) runs within a session via plan-interview, intent-framed-agent,
SKILL.md
skill-pipeline.SKILL.mdname: skill-pipeline
description: >
Pipeline orchestrator that classifies incoming coding tasks and routes them
through the correct combination of skills at the right depth. Implements two
feedback loops: the inner loop (detect, verify, recover) runs within a session
via plan-interview, intent-framed-agent, context-surfing, verify-gate,
self-healing (active recovery on failure), simplify-and-harden, and
self-improvement. The outer loop (inspect, encode, regress-test) runs across
sessions via learning-aggregator, harness-updater, and eval-creator.
pre-flight-check bridges the two by surfacing accumulated knowledge — past
heals and learnings — at session start. Handles standard, team-based, CI,
and outer-loop pipeline variants. Does not replace individual skills;
dispatches to them.
Skill Pipeline
The conductor, not a player. This skill classifies tasks, selects the pipeline variant, calibrates depth, and orchestrates handoffs between skills. It produces no artifacts of its own — its output is routing decisions that activate other skills.
Task Classification
On every coding task, classify before acting. Evaluate scope signals and map to a task class.
**Input signals:** file count, task description, existing plan/handoff files, batch indicators, CI environment.
Task received
│
├─ Trivial (typo, rename, version bump)
│ → No skills. Just do it.
│
├─ Small (isolated fix, single-file, <10 logic lines)
│ → verify-gate + simplify-and-harden
│
├─ Medium (feature in known area, 2-5 files)
│ → intent-framed-agent + verify-gate + simplify-and-harden
│
├─ Large (complex refactor, new architecture, unfamiliar codebase, high-risk logic)
│ → Full standard pipeline
│ → Recommend /plan-interview before starting
│
├─ Long-running (multi-session, high context pressure, prior handoff exists)
│ → Full standard pipeline with context-surfing as critical skill
│
└─ Batch (multiple features from spec, 5+ discrete tasks, issue triage)
→ Team-based pipeline (agent-teams-simplify-and-harden)When uncertain, start with Medium. Add skills if drift or quality issues appear mid-task.
For detailed heuristics, edge cases, and examples: read `references/classification-rules.md`.
Pipeline Selection
Route task class to the right variant:
| Task Class | Variant | Rationale | |------------|---------|-----------| | Trivial | None | No overhead needed | | Small | Standard (minimal) | Verify + S&H only | | Medium | Standard (partial) | Scope monitoring + verify + review | | Large | Standard (full) | Full inner loop with planning | | Long-running | Standard (full) | Context-surfing is critical | | Batch | Team-based | Breadth over depth | | CI environment | CI | Headless review | | Periodic | Outer loop | Cross-session improvement |
**Heuristic:** Standard pipeline for **depth** (single complex feature). Team-based pipeline for **breadth** (batch of tasks). CI pipeline when `CI=true` or `GITHUB_ACTIONS=true`.
Activation Sequences
Standard Pipeline (Inner Loop)
pre-flight-check (SessionStart hook — surfaces prior learnings + heals)
→ classify
→ (recommend /plan-interview if Large or Long-running)
→ intent-framed-agent (at planning-to-execution transition)
→ context-surfing (auto-activates when intent frame + plan exist; concurrent with intent monitoring)
→ [IMPLEMENTATION]
→ self-healing ← inner-loop recovery primitive; called whenever a command/test/build/external call fails or a helper is missing.
→ Diagnoses, patches, verifies, files HEAL- entry. Resumes when verified.
→ verify-gate (compile + test + lint; fix loop if red — fix loop calls self-healing)
→ simplify-and-harden (post-completion, if non-trivial diff)
→ self-improvement (on errors, corrections, S&H learning candidates, recurring heal handoffs)
**Skill-by-class activation:**
| Skill | Trivial | Small | Medium | Large | Long-running | |-------|---------|-------|--------|-------|-------------| | pre-flight-check | Hook | Hook | Hook | Hook | Hook | | plan-interview | - | - | - | Recommend | Recommend | | intent-framed-agent | - | - | Activate | Activate | Activate | | context-surfing | - | - | - | Activate | Critical | | verify-gate | - | Activate | Activate | Activate | Activate | | self-healing | On failure | On failure | On failure | On failure | On failure | | simplify-and-harden | - | If non-trivial | If non-trivial | If non-trivial | If non-trivial | | self-improvement | On error only | On error only | On error/completion | On error/completion | On error/completion |
Team-Based Pipeline
classify (Batch)
→ (recommend /plan-interview if no spec exists)
→ agent-teams-simplify-and-harden
├─ Team lead emits Intent Frame #1
├─ Phase 1: parallel implementation agents
├─ verify-gate (compile + test + lint)
├─ Phase 2: parallel audit agents (simplify, harden, spec)
├─ Fix loop (up to 3 audit rounds)
└─ Learning loop output
→ self-improvementCI Pipeline
classify (CI detected)
→ simplify-and-harden-ci (headless scan, PR changed files only)
→ self-improvement-ci (pattern aggregation, promotion recommendations)
Outer Loop Pipeline
The outer loop runs across sessions, not within them. Trigger on cadence (weekly, sprint boundary) or when `pre-flight-check` surfaces promotion-ready patterns.
learning-aggregator (read .learnings/, find patterns, rank promotion candidates)
→ harness-updater agent (apply promotions to CLAUDE.md, AGENTS.md, copilot-instructions.md)
→ eval-creator (create permanent test cases from promoted patterns)
→ eval-creator run (regression check on all existing evals)
**When to trigger the outer loop:**
- Weekly: recommended minimum cadence
- Sprint boundary: after a burst of sessions
- When `pre-flight-check` reports promotion-ready count > 3
- After a significant incident or recurring failure
- Manually: user invokes `/
Read more
name: skill-pipeline description: > Pipeline orchestrator that classifies incoming coding tasks and routes them through the correct combination of skills at the right depth. Implements two feedback loops: the inner loop (detect, verify, recover) runs within a session via plan-interview, intent-framed-agent, context-surfing, verify-gate, self-healing (active recovery on failure), simplify-and-harden, and self-improvement. The outer loop (inspect, encode, regress-test) runs across sessions via learning-aggregator, harness-updater, and eval-creator. pre-flight-check bridges the two by surfacing accumulated knowledge — past heals and learnings — at session start. Handles standard, team-based, CI, and outer-loop pipeline variants. Does not replace individual skills; dispatches to them.
Skill Pipeline
The conductor, not a player. This skill classifies tasks, selects the pipeline variant, calibrates depth, and orchestrates handoffs between skills. It produces no artifacts of its own — its output is routing decisions that activate other skills.
Task Classification
On every coding task, classify before acting. Evaluate scope signals and map to a task class.
**Input signals:** file count, task description, existing plan/handoff files, batch indicators, CI environment.
Task received
│
├─ Trivial (typo, rename, version bump)
│ → No skills. Just do it.
│
├─ Small (isolated fix, single-file, <10 logic lines)
│ → verify-gate + simplify-and-harden
│
├─ Medium (feature in known area, 2-5 files)
│ → intent-framed-agent + verify-gate + simplify-and-harden
│
├─ Large (complex refactor, new architecture, unfamiliar codebase, high-risk logic)
│ → Full standard pipeline
│ → Recommend /plan-interview before starting
│
├─ Long-running (multi-session, high context pressure, prior handoff exists)
│ → Full standard pipeline with context-surfing as critical skill
│
└─ Batch (multiple features from spec, 5+ discrete tasks, issue triage)
→ Team-based pipeline (agent-teams-simplify-and-harden)When uncertain, start with Medium. Add skills if drift or quality issues appear mid-task.
For detailed heuristics, edge cases, and examples: read `references/classification-rules.md`.
Pipeline Selection
Route task class to the right variant:
| Task Class | Variant | Rationale | |------------|---------|-----------| | Trivial | None | No overhead needed | | Small | Standard (minimal) | Verify + S&H only | | Medium | Standard (partial) | Scope monitoring + verify + review | | Large | Standard (full) | Full inner loop with planning | | Long-running | Standard (full) | Context-surfing is critical | | Batch | Team-based | Breadth over depth | | CI environment | CI | Headless review | | Periodic | Outer loop | Cross-session improvement |
**Heuristic:** Standard pipeline for **depth** (single complex feature). Team-based pipeline for **breadth** (batch of tasks). CI pipeline when `CI=true` or `GITHUB_ACTIONS=true`.
Activation Sequences
Standard Pipeline (Inner Loop)
pre-flight-check (SessionStart hook — surfaces prior learnings + heals) → classify → (recommend /plan-interview if Large or Long-running) → intent-framed-agent (at planning-to-execution transition) → context-surfing (auto-activates when intent frame + plan exist; concurrent with intent monitoring) → [IMPLEMENTATION] → self-healing ← inner-loop recovery primitive; called whenever a command/test/build/external call fails or a helper is missing. → Diagnoses, patches, verifies, files HEAL- entry. Resumes when verified. → verify-gate (compile + test + lint; fix loop if red — fix loop calls self-healing) → simplify-and-harden (post-completion, if non-trivial diff) → self-improvement (on errors, corrections, S&H learning candidates, recurring heal handoffs)
**Skill-by-class activation:**
| Skill | Trivial | Small | Medium | Large | Long-running | |-------|---------|-------|--------|-------|-------------| | pre-flight-check | Hook | Hook | Hook | Hook | Hook | | plan-interview | - | - | - | Recommend | Recommend | | intent-framed-agent | - | - | Activate | Activate | Activate | | context-surfing | - | - | - | Activate | Critical | | verify-gate | - | Activate | Activate | Activate | Activate | | self-healing | On failure | On failure | On failure | On failure | On failure | | simplify-and-harden | - | If non-trivial | If non-trivial | If non-trivial | If non-trivial | | self-improvement | On error only | On error only | On error/completion | On error/completion | On error/completion |
Team-Based Pipeline
classify (Batch)
→ (recommend /plan-interview if no spec exists)
→ agent-teams-simplify-and-harden
├─ Team lead emits Intent Frame #1
├─ Phase 1: parallel implementation agents
├─ verify-gate (compile + test + lint)
├─ Phase 2: parallel audit agents (simplify, harden, spec)
├─ Fix loop (up to 3 audit rounds)
└─ Learning loop output
→ self-improvementCI Pipeline
classify (CI detected) → simplify-and-harden-ci (headless scan, PR changed files only) → self-improvement-ci (pattern aggregation, promotion recommendations)
Outer Loop Pipeline
The outer loop runs across sessions, not within them. Trigger on cadence (weekly, sprint boundary) or when `pre-flight-check` surfaces promotion-ready patterns.
learning-aggregator (read .learnings/, find patterns, rank promotion candidates) → harness-updater agent (apply promotions to CLAUDE.md, AGENTS.md, copilot-instructions.md) → eval-creator (create permanent test cases from promoted patterns) → eval-creator run (regression check on all existing evals)
**When to trigger the outer loop:**
- Weekly: recommended minimum cadence
- Sprint boundary: after a burst of sessions
- When `pre-flight-check` reports promotion-ready count > 3
- After a significant incident or recurring failure
- Manually: user invokes `/
A collection of skills for AI agents. Follows the Agent Skills specification. This repository is my personal skill testing ground.
Other skills on pskoett-ai-skills.
- /agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests
Open skill - /context-surfing
Monitors context window health throughout a session and rides peak context quality for maximum output fidelity. Activates automatically after plan-interview and intent-framed-agent. Stays active through execution and hands off cleanly to simplify-and-harden and self-improvement
Open skill - /control-session-orchestrator
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out
Open skill - /eval-creator-ci
[Beta] CI-only eval regression runner using gh-aw (GitHub Agentic Workflows). Runs all eval cases in .evals/ on a schedule or per-PR, reports pass/fail results, and can block merges on regressions. Also creates new eval cases from promoted patterns flagged by
Open skill - /eval-creator
[Beta] Creates permanent eval cases from promoted learnings and runs regression checks against them. Turns failures into test cases that prevent silent regression. This is the outer loop''s regress-test step. Use when a learning is promoted and has a clear pass/fail condition,
Open skill - /intent-framed-agent
Frames coding-agent work sessions with explicit intent capture and drift monitoring. Use when a session transitions from planning/Q&A to implementation for coding tasks, refactors, feature builds, bug fixes, or other multi-step execution where scope drift is a risk.
Open skill

