Skip to content

notque/vexjoy-agent / skills/process/workflow

workflow

Verified

Structured work: multi-phase tasks, feature builds, planning, objective loops, hill climbing.

FileKindSize
SKILL.mdskill md13.2 KB
references/adr-template.mdmarkdown9.4 KB
references/agent-upgrade.mdmarkdown12.5 KB
references/article-evaluation-pipeline.mdmarkdown8.9 KB
references/article-evaluation-pipeline/references/report-template.mdmarkdown2.5 KB
references/article-evaluation-pipeline/references/wabi-sabi-classification.mdmarkdown2.4 KB
references/auto-pipeline.mdmarkdown12.5 KB
references/auto-pipeline/references/pipeline-catalog.jsonconfig15.0 KB
references/auto-pipeline/references/pipeline-catalog.mdmarkdown4.3 KB
references/build_dag.pyscript12.5 KB
references/chain-composer.mdmarkdown20.4 KB
references/chain-composer/references/canonical-chains.mdmarkdown13.9 KB
references/comprehensive-review-workflow.jsscript19.3 KB
references/comprehensive-review.mdmarkdown27.8 KB
references/comprehensive-review/references/output-templates.mdmarkdown10.6 KB
references/comprehensive-review/references/wave-0-per-package.mdmarkdown5.6 KB
references/comprehensive-review/references/wave-1-foundation.mdmarkdown10.4 KB
references/comprehensive-review/references/wave-2-deep-dive.mdmarkdown7.3 KB
references/comprehensive-review/references/wave-3-adversarial.mdmarkdown7.4 KB
references/dag-compatibility-matrix.mdmarkdown13.0 KB
references/dag-composition-patterns.mdmarkdown5.0 KB
references/dag-orchestration-advanced.mdmarkdown6.3 KB
references/dag-orchestration-examples.mdmarkdown11.4 KB
references/dag-skill-patterns.mdmarkdown12.5 KB
references/de-ai-pipeline.jsscript14.6 KB
references/de-ai-pipeline.mdmarkdown6.3 KB
references/discover_skills.pyscript12.1 KB
references/do-perspectives.mdmarkdown11.5 KB
references/doc-pipeline.mdmarkdown9.2 KB
references/domain-research.mdmarkdown32.8 KB
references/domain-research/references/task-type-guide.mdmarkdown11.4 KB
references/explore-pipeline.jsscript18.6 KB
references/explore-pipeline.mdmarkdown15.0 KB
references/fan-out-workflow.jsscript9.7 KB
references/fan-out-workflow.pyscript10.4 KB
references/feedback-loop-construction.mdmarkdown14.3 KB
references/fl-design.mdmarkdown9.6 KB
references/fl-error-handling.mdmarkdown8.5 KB
references/fl-implement.mdmarkdown7.6 KB
references/fl-pipeline.mdmarkdown6.0 KB
references/fl-plan.mdmarkdown11.0 KB
references/fl-release.mdmarkdown3.8 KB
references/fl-shared.mdmarkdown3.6 KB
references/fl-validate.mdmarkdown4.5 KB
references/github-profile-rules.mdmarkdown10.5 KB
references/github-profile-rules/references/rule-categories.mdmarkdown6.5 KB
references/hc-SPEC.mdmarkdown3.3 KB
references/hc-domain-playbooks.mdmarkdown15.4 KB
references/hc-ledger.mdmarkdown3.3 KB
references/hc-profiling-tools.mdmarkdown3.7 KB
references/hill-climb.mdmarkdown9.3 KB
references/hook-development-pipeline.mdmarkdown12.9 KB
references/mcp-pipeline-builder.mdmarkdown16.3 KB
references/mcp-pipeline-builder/references/analysis-checklist.mdmarkdown6.2 KB
references/mcp-pipeline-builder/references/design-rules.mdmarkdown7.1 KB
references/mcp-pipeline-builder/references/evaluation-guide.mdmarkdown7.6 KB
references/mcp-pipeline-builder/references/python-scaffold-template.mdmarkdown9.5 KB
references/mcp-pipeline-builder/references/ts-scaffold-template.mdmarkdown1.6 KB
references/mcp-pipeline-builder/scripts/assemble-scaffold.pyscript6.3 KB
references/mcp-pipeline-builder/scripts/register_mcp.pyscript6.9 KB
references/mcp-pipeline-builder/templates/client-cli.ts.tmplother682 B
references/mcp-pipeline-builder/templates/client-http.ts.tmplother1.4 KB
references/mcp-pipeline-builder/templates/index.ts.tmplother1.1 KB
references/mcp-pipeline-builder/templates/package.json.tmplother477 B
references/mcp-pipeline-builder/templates/readme.md.tmplother1.1 KB
references/mcp-pipeline-builder/templates/tools.ts.tmplother3.0 KB
references/mcp-pipeline-builder/templates/ts-scaffold.tmplother556 B
references/mcp-pipeline-builder/templates/tsconfig.json.tmplother408 B
references/ol-SPEC.mdmarkdown2.4 KB
references/ol-state-file.mdmarkdown2.9 KB
references/pipeline-index.jsonconfig23.9 KB
references/pipeline-orchestrator.mdmarkdown15.3 KB
references/pipeline-orchestrator/orchestration-patterns.mdmarkdown8.1 KB
references/pipeline-orchestrator/preferred-patterns.mdmarkdown4.6 KB
references/pipeline-retro.mdmarkdown19.0 KB
references/pipeline-scaffolder.mdmarkdown22.4 KB
references/pipeline-scaffolder/references/architecture-rules.mdmarkdown18.9 KB
references/pipeline-scaffolder/references/generated-skill-template.mdmarkdown1.9 KB
references/pipeline-scaffolder/references/pipeline-spec-format.mdmarkdown36.8 KB
references/pipeline-scaffolder/references/step-menu.mdmarkdown21.5 KB
references/pipeline-scaffolder/scripts/assemble-skill.pyscript6.3 KB
references/pipeline-scaffolder/templates/phases/decision-planning.md.tmplother1.2 KB
references/pipeline-scaffolder/templates/phases/domain-extension.md.tmplother1.5 KB
references/pipeline-scaffolder/templates/phases/generation.md.tmplother427 B
references/pipeline-scaffolder/templates/phases/git-release.md.tmplother1.1 KB
references/pipeline-scaffolder/templates/phases/interaction.md.tmplother965 B
references/pipeline-scaffolder/templates/phases/learning-retro.md.tmplother1.5 KB
references/pipeline-scaffolder/templates/phases/observation.md.tmplother1.3 KB
references/pipeline-scaffolder/templates/phases/research-gathering.md.tmplother1.2 KB
references/pipeline-scaffolder/templates/phases/review.md.tmplother930 B
references/pipeline-scaffolder/templates/phases/safety-guarding.md.tmplother1.7 KB
references/pipeline-scaffolder/templates/phases/structuring.md.tmplother361 B
references/pipeline-scaffolder/templates/phases/synthesis-reporting.md.tmplother1.9 KB
references/pipeline-scaffolder/templates/phases/validation.md.tmplother1.1 KB
references/pipeline-scaffolder/templates/skill-template.md.tmplother12.0 KB
references/pipeline-test-runner.mdmarkdown16.7 KB
references/pl-ambiguity-triage.mdmarkdown2.7 KB
references/pl-check-dimensions.mdmarkdown7.4 KB
references/pl-check-errors.mdmarkdown824 B
references/pl-check-verdict-format.mdmarkdown3.2 KB
references/pl-check.mdmarkdown6.5 KB
references/pl-context-boundary.mdmarkdown1.6 KB
references/pl-depth-first-interview.mdmarkdown11.6 KB
references/pl-empirical-prototype.mdmarkdown825 B
references/pl-executor-ready-plan-template.mdmarkdown7.7 KB
references/pl-human-source-elicitation.mdmarkdown1.5 KB
references/pl-manage.mdmarkdown5.1 KB
references/pl-pause-confirm-and-errors.mdmarkdown2.1 KB
references/pl-pause-extract-decisions.mdmarkdown3.0 KB
references/pl-pause-gather-steps.mdmarkdown2.3 KB
references/pl-pause-synthesize-fields.mdmarkdown2.3 KB
references/pl-pause-write-templates.mdmarkdown5.3 KB
references/pl-pause.mdmarkdown6.5 KB
references/pl-plan-files.mdmarkdown8.4 KB
references/pl-pre-plan.mdmarkdown11.6 KB
references/pl-resume.mdmarkdown12.3 KB
references/pl-spec.mdmarkdown5.2 KB
references/pr-fix-loop.mdmarkdown10.3 KB
references/pr-fix-loop/references/message-formats.mdmarkdown1.6 KB
references/pr-fix-loop/references/publish.mdmarkdown5.4 KB
references/pr-fix-loop/references/review-checklist.mdmarkdown3.4 KB
references/pr-pipeline/references/pr-templates.mdmarkdown5.4 KB
references/pr-pipeline/references/preflight-checklist.mdmarkdown2.8 KB
references/pr-pipeline/references/retro-adr-phases.mdmarkdown2.7 KB
references/pr-pipeline/references/review-fix-loop.mdmarkdown2.0 KB
references/project-coordinator.mdmarkdown6.5 KB
references/project-coordinator/agent-capability-map.mdmarkdown5.4 KB
references/project-coordinator/communication-protocols.mdmarkdown4.5 KB
references/project-coordinator/coordination-playbook.mdmarkdown3.7 KB
references/project-coordinator/death-loop-prevention.mdmarkdown3.6 KB
references/project-coordinator/error-catalog.mdmarkdown2.7 KB
references/project-coordinator/parallel-execution-patterns.mdmarkdown2.8 KB
references/project-coordinator/preferred-patterns.mdmarkdown5.9 KB
references/project-coordinator/todowrite-integration.mdmarkdown5.6 KB
references/research-pipeline.jsscript15.2 KB
references/skill-creation-pipeline.mdmarkdown17.1 KB
references/system-upgrade.mdmarkdown12.8 KB
references/systematic-debugging.mdmarkdown11.0 KB
references/systematic-refactoring.mdmarkdown11.4 KB
references/toolkit-improvement.jsscript39.0 KB
references/toolkit-improvement.mdmarkdown20.5 KB
references/toolkit-improvement/references/adr-template.mdmarkdown10.5 KB
references/toolkit-improvement/references/agent-roster.mdmarkdown15.8 KB
references/workflow-helpers.jsscript12.1 KB
references/workflow-orchestrator.mdmarkdown20.8 KB
references/workflow-orchestrator/references/plan-template.mdmarkdown1.3 KB
references/workflow-orchestrator/references/task-patterns.mdmarkdown23.3 KB
references/workflow-orchestrator/scripts/assemble-plan.pyscript6.9 KB
references/workflow-orchestrator/scripts/validate.pyscript14.4 KB
references/workflow-orchestrator/templates/plan-template.json.tmplother904 B

references/pipeline-orchestrator/orchestration-patterns.md

View on GitHub
# Pipeline Orchestration — Fan-Out/Fan-In Patterns

> **Scope**: Dispatching parallel sub-agents, collecting outputs, enforcing phase gates. Orchestrator role only.

---

## Pattern Table

| Pattern | When | Avoid When |
|---------|------|------------|
| Fan-out by creator type | 3+ independent components | Single component |
| Context package pre-flight | Every sub-agent dispatch | Never skip |
| Hard gate before fan-in | Phase 3→4 transition | Never skip |
| ADR hash embed | Domain pipelines (full 7-phase) | Simple single-skill pipelines |
| Sequential within sub-agent | One component depends on another | Same-type components (parallel) |

---

## Fan-Out by Creator Type

Group components by creator, dispatch one sub-agent per type in parallel.

```
Orchestrator
  ├── toolkit (all new skills + references)       ← parallel
  ├── general-purpose + toolkit/references/hook-development.md (all hooks) ← parallel
  └── Direct (Python scripts)                     ← parallel

Gate: wait for ALL three before Phase 4 INTEGRATE
```

---

## Context Package Structure

Every sub-agent dispatch must include all four fields:

```python
Agent(
  description="Create {N} skills for {domain}",
  prompt=f"""
  ## Context Package

  ### Components to Create
  {component_list}

  ### Discovery Report
  {discovery_report}

  ### Inter-Component Relationships
  {relationships}

  ### Template Reference
  Follow skills/meta/toolkit/references/skill-creator/agent-template.md for agents. Standard frontmatter + operator context for skills.

  ### Architecture Rules
  See skills/process/workflow/references/pipeline-scaffolder/references/architecture-rules.md.
  Critical: Rule 12 (parallel research), Rule 18 (ADR hash), role-matched allowed-tools (advisory; Claude Code ignores it for agents).
  """
)
```

Sub-agents start with no shared context. Without discovery report → duplicates. Without relationships → orphaned files. Without template → non-compliant output.

---

## Phase Gate Enforcement

```bash
# Gate: Phase 3 → Phase 4
for component in "${expected_components[@]}"; do
  if [[ ! -f "$component" ]]; then
    echo "GATE FAIL: $component missing"
    exit 1
  fi
done

python3 scripts/validate-references.py --agent {name}

for hook in hooks/{pipeline-name}*.py; do
  python3 -c "import ast; ast.parse(open('$hook').read())" || echo "Syntax error: $hook"
done
```

---

## ADR Context Injection

```bash
adr_context=$(python3 ~/.claude/scripts/adr-query.py context \
  --adr adr/{pipeline-name}.md --role toolkit)
```

Manual injection only needed when sub-agent needs full role-targeted ADR context beyond session-level auto-injection.

---

## Simple vs. Domain Pipeline Decision

```
Single skill/agent with one clear purpose?
  YES → Simple: Phase 0 → Phase 1 (legacy discover) → Phase 3 → Phase 4

  NO / broad domain →
    Domain: Full 7-phase flow with subdomain decomposition,
    validate-chain, ADR hash gate, test-runner, retro.
```

---

## Pattern Catalog

### Wait for All Sub-Agents Before Integration
**Signal**: Starting Phase 4 after only 2 of 3 sub-agents complete.
**Fix**: Hard gate — wait for ALL dispatched agents before any integration step. No acceptable partial state.

### Create ADR Before Starting Domain Pipelines
**Signal**: Starting Phase 1 without `adr/pipeline-{name}.md`.
**Fix**: Phase 0 is always first. Create ADR, register session: `python3 ~/.claude/scripts/adr-query.py register --adr adr/{pipeline-name}.md`

### Match Pipeline Complexity to Request Scope
**Signal**: Creating 4 sub-agents, a hook, and 3 scripts for a one-skill request.
**Fix**: Apply 80% rule — if existing agent covers 80%+, bind new skills to it.

---

## Error-Fix Mappings

| Error | Root Cause | Fix |
|-------|------------|-----|
| `Agent tool: unknown subagent_type` | New agent not available until session restart | Restart Claude Code |
| Hook import fails | Syntax error or wrong path | `python3 -m py_compile hooks/X.py` |
| `toolkit: no triggers` | Missing `routing.triggers` in frontmatter | Add triggers to frontmatter |
| Orphaned component | Wrong output path | Check actual vs expected path; rename |
| `validate-chain: unknown step type` | Step not in step-menu.md | Pick a step from `skills/process/workflow/references/pipeline-scaffolder/references/step-menu.md` |

---

## Detection Commands

```bash
# Verify components created after Phase 3
for f in skills/*/{name}/SKILL.md skills/*/*/references/{name}.md hooks/{name}*.py; do
  [[ -f "$f" ]] && echo "OK: $f" || echo "MISSING: $f"
done

# Overlay agents only (owner-requested): find agents missing from the private-inclusive index
comm -23 \
  <(ls private-agents/*.md 2>/dev/null | xargs -r -I{} basename {} .md | sort) \
  <(python3 -c "import json; print('\n'.join(json.load(open('agents/INDEX.local.json'))['agents']))" | sort)

# Check ADR session registered
ls -la .adr-session.json 2>/dev/null || echo "ADR session not registered"
```

---

## Phase 4 — Integration Verification Checklist

- Every new skill reference is named in its skill's Reference Loading Table; an owner-requested overlay agent is in `agents/INDEX.local.json`
- Each new component's frontmatter triggers appear in the regenerated `skills/INDEX.json` (`python3 scripts/check-routing-drift.py` checks skills)
- All hooks syntactically valid Python
- All skills follow frontmatter + operator context pattern
- No orphaned components

---

## Phase 3 — Creator Sub-Agent Table

| Creator | Components | Template |
|---------|-----------|----------|
| `toolkit` | Agent manifests + skill SKILL.md + references | `skills/meta/toolkit/references/skill-creator/agent-template.md` / standard skill format |
| `general-purpose` worker; prompt starts "Read ~/.claude/skills/toolkit/references/hook-development.md and follow it" | Python hooks | `hooks/lib/hook_utils.py` conventions |
| Direct (orchestrator) | Python scripts | `scripts/` conventions |

Each sub-agent receives: component list, Discovery Report/Pipeline Spec, bound skills/agents, architecture patterns, inter-component relationships.

---

## ADR Template (Phase 0)

```markdown
# ADR: Pipeline {Name}

## Status
PROPOSED | ACCEPTED | IMPLEMENTED | DEPRECATED

## Context
[Why needed, what triggered creation]

## Decision
[Pipeline design: components, flow, triggers]

## Component Manifest
[Agents, skills, hooks, scripts — updated during discovery]

## Constraints
[Architecture rules, reuse requirements, naming conventions]

## Consequences
[Routing changes, new triggers, affected pipelines]

## Test Plan
[Validation approach]
```

---

## Capabilities Summary

**CAN Do**: Orchestrate complete pipelines; plan component graphs; fan out to the toolkit skill and a hook worker (`general-purpose` + `hook-development.md`) in parallel; detect/reuse existing components; integrate into /do routing; research domains for subdomains; compose valid chains; validate chain compatibility.

**CANNOT Do**: Write domain business logic; modify existing pipelines directly; create pipelines without routing integration; compose chains without validation; create monolithic single-skill for multi-subdomain domains.

---

## Output Format — Planning Schema

**Required Sections**: (1) Discovery Report, (2) Pipeline Spec (domain), (3) Execution Plan, (4) Integration Checklist, (5) Completion Report, (6) Session Restart Notice.

**Session Restart Notice (MANDATORY)** — last output after every pipeline creation:

```
SESSION RESTART REQUIRED
New agent '{agent-name}' was created and synced to ~/.claude/agents/.
Claude Code compiles available subagent types at session startup:
agents added during a session are NOT available as subagent_type
until the next session.

To use this pipeline:
  1. Restart Claude Code (Ctrl+C, then rerun `claude`)
  2. Then invoke: /do {trigger phrase}

The agent will be available immediately after restart.
```

---

## See Also

- `preferred-patterns.md` — pipeline creation mistakes
- `skills/process/workflow/references/pipeline-scaffolder/references/step-menu.md` — valid steps and type signatures
- `skills/process/workflow/references/pipeline-scaffolder/references/architecture-rules.md` — architecture rules
- `scripts/artifact-utils.py` — discovery, chain validation
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall