Pipeline Reflection Ux

Name: Pipeline Reflection Ux
Author: oimiragieo

oimiragieo/agent-studio

43 installs
36 repo stars
Updated July 14, 2026
oimiragieo/agent-studio

Helps with ai & agent building tasks.

About

pipeline-reflection-ux is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

pipeline-reflection-ux
AI & Agent Building
AI-coding skill

Pipeline Reflection Ux by the numbers

43 all-time installs (skills.sh)
Ranked #7,921 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 4, 2026 (Skillselion catalog sync)

npx skills add https://github.com/oimiragieo/agent-studio --skill pipeline-reflection-ux

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/oimiragieo/agent-studio/pipeline-reflection-ux.svg)](https://skillselion.com/skills/oimiragieo/agent-studio/pipeline-reflection-ux)

Installs	43
repo stars	★ 36
Last updated	July 14, 2026
Repository	oimiragieo/agent-studio ↗

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Pipeline Reflection UX

Use this skill to keep pipeline/reflection output concise, explicit, and low-noise.

Workflow

1. Make Step 0 visible in router narration. 2. Emit Step 0 completion before TaskList(). 3. Emit a one-line reflection outcome with report path. 4. Batch late post-pipeline notifications into one summary. 5. Keep guardrail semantics unchanged (block stays block).

Required Checks

Add/adjust tests before behavior changes.
Confirm no regression in routing/taskupdate/read-safety tests.
Verify debug-log counts improve for repeated violations/noise.

Iron Laws

1. ALWAYS emit Step 0 narration (pending reflections count) before any TaskList() call — omitting the narration makes reflection spawning invisible to the user and breaks the pipeline audit trail. 2. NEVER batch reflection spawns with tool calls that depend on their results — reflection agents must complete before the router proceeds to routing; mixing them creates race conditions. 3. ALWAYS emit a one-line reflection outcome (report path + summary) after reflection-agent completes — without this, the user cannot distinguish a completed reflection from a skipped one. 4. NEVER emit one status message per late-completing background agent — per-agent late notifications create noise storms; batch all late completions into one summary after drain gate passes. 5. ALWAYS preserve existing block semantics when modifying pipeline narration — changing guardrail modes while fixing UX copy conflates two concerns and masks the behavioral impact of either change.

Anti-Patterns

Anti-Pattern	Why It Fails	Correct Approach
Omitting Step 0 narration	Reflection spawning invisible to user; pipeline audit trail broken	Always emit "Step 0: N pending reflections..." before spawning reflection agents
Missing one-line reflection outcome	User cannot distinguish completed reflection from skipped one	Emit report path + one-line summary after every reflection-agent completion
One status message per late-completing agent	Creates noise storms; clutters pipeline output	Batch all late completions into one summary message after drain gate passes
Changing guardrail modes while fixing UX copy	Conflates two changes; behavioral impact of each masked in review	Separate UX copy changes from guardrail mode changes in distinct commits
Emitting Step 0 completion after TaskList()	Violates router output contract; narration out of sequence	Emit "Step 0 complete." before calling TaskList(), not after

Memory Protocol (MANDATORY)

Before starting: Read .claude/context/memory/learnings.md

After completing:

New pattern → .claude/context/memory/learnings.md
Issue found → .claude/context/memory/issues.md
Decision made → .claude/context/memory/decisions.md

ASSUME INTERRUPTION: If it's not in memory, it didn't happen.

References

Detailed UX review: references/ui-reflection-review.md
Troubleshooting runbook: .claude/docs/TROUBLESHOOTING.md
Task tracking protocol: .claude/docs/@TASK_TRACKING_GUIDE.md

'use strict';
/**
 * Post-execute hook for pipeline-reflection-ux
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Records metrics after skill execution.
 */

function postExecute(_context) {
  // Record execution metrics
  return { ok: true, skill: 'pipeline-reflection-ux' };
}

module.exports = { postExecute };

'use strict';
/**
 * Pre-execute hook for pipeline-reflection-ux
 * Auto-generated by enterprise-bundle-scaffolder
 *
 * Validates inputs before skill execution.
 */

function preExecute(context) {
  // Validate skill invocation context
  if (!context || typeof context !== 'object') {
    return { allow: true, message: 'pipeline-reflection-ux: no context to validate' };
  }
  return { allow: true };
}

module.exports = { preExecute };

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "pipeline-reflection-uxInput",
  "description": "Input schema for Improve router-facing pipeline and reflection narration to reduce noisy status churn and make Step 0/Reflection outcomes explicit. Use when updating Router output contract, reflection reminder wording, or post-pipeline notification batching.",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "target": {
      "type": "string",
      "description": "Target file or path for the skill to operate on"
    },
    "options": {
      "type": "object",
      "description": "Additional options for skill execution",
      "additionalProperties": true
    }
  }
}

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "pipeline-reflection-uxOutput",
  "type": "object",
  "additionalProperties": true,
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "summary": {
      "type": "string"
    }
  }
}

#!/usr/bin/env node
'use strict';
/**
 * pipeline-reflection-ux - Enterprise Skill Script
 * Auto-generated by enterprise-bundle-scaffolder
 */

const fs = require('fs');
const path = require('path');

// Parse arguments
const args = process.argv.slice(2);
const options = {};
for (let i = 0; i < args.length; i++) {
  if (args[i].startsWith('--')) {
    const key = args[i].slice(2);
    const value = args[i + 1] && !args[i + 1].startsWith('--') ? args[++i] : true;
    options[key] = value;
  }
}

if (options.help) {
  console.log(`
pipeline-reflection-ux - Enterprise Skill

Usage:
  node main.cjs --check <file>    Check a file against guidelines
  node main.cjs --list            List all guidelines
  node main.cjs --help            Show this help

Description:
  Improve router-facing pipeline and reflection narration to reduce noisy status churn and make Step 0/Reflection outcomes explicit. Use when updating Router output contract, reflection reminder wording, or post-pipeline notification batching.
`);
  process.exit(0);
}

if (options.list) {
  console.log('Guidelines for pipeline-reflection-ux:');
  console.log('See SKILL.md for full guidelines');
  process.exit(0);
}

console.log('pipeline-reflection-ux skill loaded. Use with Claude for code review.');