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/dag-skill-patterns.md

View on GitHub
# Common Skill Composition Patterns

This document describes proven patterns for composing multiple skills into effective workflows.

## Pattern Catalog

### 1. Feature Development Pipeline

**Pattern**: `workflow-orchestrator → test-driven-development → verification-before-completion`

**When to Use**:
- Adding new features to codebase
- Need structured task breakdown
- Require comprehensive testing
- Want verification before completion

**Example Task**: "Add user authentication feature with tests"

**Execution Flow**:
1. **workflow-orchestrator**: Breaks feature into 2-5 minute subtasks with exact file paths
2. **test-driven-development**: Implements each subtask with RED-GREEN-REFACTOR cycle
3. **verification-before-completion**: Validates tests pass, code quality meets standards

**Expected Duration**: 20-40 minutes depending on feature complexity

**Success Criteria**:
- All subtasks completed
- Tests pass (RED → GREEN achieved)
- Code refactored for quality
- Verification gates passed

---

### 2. Debug and Document

**Pattern**: `systematic-debugging → comment-quality`

**When to Use**:
- Fixing bugs in production code
- Need root cause analysis
- Want proper documentation of fixes
- Prevent temporal references in comments

**Example Task**: "Debug authentication timeout and document the fix"

**Execution Flow**:
1. **systematic-debugging**: 4-phase root cause analysis (Reproduce → Isolate → Identify → Verify)
2. **comment-quality**: Reviews fix comments to ensure they explain WHAT/WHY, not WHEN

**Expected Duration**: 15-30 minutes

**Success Criteria**:
- Bug root cause identified
- Fix verified with tests
- Comments explain logic, not history
- No temporal references ("fixed bug", "TODO")

---

### 3. Parallel Quality Checks

**Pattern**: `[code-linting, comment-quality] → verification-before-completion`

**When to Use**:
- Improving existing code quality
- Pre-commit validation
- Preparing code for review
- Independent quality dimensions

**Example Task**: "Check code quality and documentation before PR"

**Execution Flow**:
1. **Phase 1 (Parallel)**:
   - `code-linting`: Run ruff (Python) or Biome (JS) linters
   - `comment-quality`: Check for temporal references in comments
2. **Phase 2 (Sequential)**:
   - `verification-before-completion`: Ensure all quality gates pass

**Expected Duration**: 5-10 minutes

**Parallelization Benefit**: ~50% time reduction compared to sequential

**Success Criteria**:
- Linting passes (or auto-fixed)
- Comments are timeless
- All verification checks pass

---

### 4. Research-Driven Implementation

**Pattern**: `pr-workflow (miner) → codebase-analyzer → workflow-orchestrator → test-driven-development`

**When to Use**:
- Implementing features in unfamiliar codebase
- Want to learn existing patterns first
- Need coding standards from PR reviews
- Building on established conventions

**Example Task**: "Add rate limiting following existing patterns"

**Execution Flow**:
1. **pr-workflow (miner)**: Mine GitHub PR review comments for tribal knowledge
2. **codebase-analyzer**: Extract implementation patterns from existing code
3. **workflow-orchestrator**: Plan implementation based on learned patterns
4. **test-driven-development**: Implement following discovered conventions

**Expected Duration**: 40-60 minutes

**Success Criteria**:
- Patterns extracted from existing code
- Implementation follows established conventions
- Tests validate behavior
- Code style matches project standards

---

### 5. Language-Specific Quality Gate

**Pattern**: `test-driven-development → (if Go: go-patterns, else: code-linting)`

**When to Use**:
- Multi-language projects
- Language-specific quality requirements
- Different validation tools per language

**Example Task**: "Implement feature with language-appropriate quality checks"

**Execution Flow**:
1. **test-driven-development**: Implement feature with tests
2. **Conditional Branch**:
   - If Go: `go-patterns` (golangci-lint, go test, go build)
   - Else: `code-linting` (ruff for Python, Biome for JS)

**Expected Duration**: 20-35 minutes

**Success Criteria**:
- Feature implemented with tests
- Language-specific linting passes
- Quality gates appropriate to language

---

### 6. Documentation Audit and Enhancement

**Pattern**: `codebase-analyzer → comment-quality → (generate docs)`

**When to Use**:
- Auditing documentation quality
- Preparing for external users
- Improving maintainability
- Removing outdated comments

**Example Task**: "Audit and improve documentation quality"

**Execution Flow**:
1. **codebase-analyzer**: Analyze code structure and patterns
2. **comment-quality**: Identify temporal references and poor documentation
3. **Generate docs**: Create/update documentation based on findings

**Expected Duration**: 25-40 minutes

**Success Criteria**:
- Code structure documented
- Temporal references removed
- Comments explain WHAT/WHY
- Documentation reflects current state

---

### 7. Comprehensive Quality Gate

**Pattern**: `test-driven-development → (language-specific-quality-gate) → verification-before-completion`

**When to Use**:
- Need comprehensive language-specific validation
- Running multiple quality tools in one step
- Want automated language detection for multi-language projects

**Example Task**: "Implement feature with comprehensive quality checks"

**Execution Flow**:
1. **test-driven-development**: Implement with RED-GREEN-REFACTOR
2. **Language-specific gate**:
   - Go projects: `go-patterns` (golangci-lint, tests, race detector, build)
   - Python projects: `python-quality-gate` (ruff, pytest, mypy, bandit)
   - Multi-language: `universal-quality-gate` (auto-detect and run appropriate tools)
3. **verification-before-completion**: Final validation

**Expected Duration**: 20-35 minutes

**Success Criteria**:
- All tests pass with good coverage
- Language-specific linting passes
- No security issues detected
- Type checking passes (where applicable)
- Code ready for production

---

### 8. Loop Until Clean

**Pattern**: `code-linting → (if violations: fix-violations → code-linting, else: done)`

**When to Use**:
- Iteratively fixing linting violations
- Auto-fix not sufficient alone
- Want guarantee of clean code

**Example Task**: "Fix all linting violations in module"

**Execution Flow**:
1. **code-linting**: Identify violations
2. **Loop Decision**:
   - If violations > 0: Fix violations and re-lint
   - Else: Exit loop
3. **Maximum iterations**: 5 (prevent infinite loops)

**Expected Duration**: 5-20 minutes depending on violations

**Success Criteria**:
- Zero linting violations
- Code follows style guidelines
- Loop completed in < 5 iterations

---

## Composition Guidelines

### Sequential vs Parallel Decision Tree

```
Can skills run independently?
│
├─ YES → Consider parallel execution
│   ├─ Do they share resources?
│   │   ├─ YES → Sequential (avoid conflicts)
│   │   └─ NO → Parallel (maximize speed)
│   └─ Is output needed by another skill?
│       ├─ YES → Sequential (dependency)
│       └─ NO → Parallel
│
└─ NO → Sequential execution required
    └─ What's the dependency order?
        └─ Use topological sort
```

### Conditional Execution Guidelines

**When to use conditionals**:
- Language-specific tooling (Go vs Python vs JS)
- Error recovery paths (if fails, try alternative)
- Optional enhancements (if time permits, add feature)
- Environment-specific (if production, extra validation)

**When NOT to use conditionals**:
- Core workflow steps (always run)
- Simple linear sequences (just chain them)
- Overly complex branching (split into separate compositions)

### Loop Composition Guidelines

**Safe loop patterns**:
```
loop until clean:
  - linting → fix → re-lint
  - test → fix failures → re-test
  - validate → improve → re-validate
```

**Required safeguards**:
- **Maximum iterations**: Always set (typically 3-5)
- **Progress check**: Ensure each iteration improves (fewer violations, fewer failures)
- **Exit condition**: Clear definition of "done"
- **Timeout**: Overall time limit for loop

**Watch for**:
- Infinite loops; always set max iterations
- No progress detection; require a progress check
- Complex multi-skill loops; split them when the flow is harder to debug

---

## Patterns to Detect and Fix

### Signal 1: Over-Composition
**Signal**: Chaining too many skills (6+) in a single workflow
**Why It Matters**: The workflow becomes harder to reason about and easier to break
**Preferred Action**: Break the work into multiple compositions or use workflow-orchestrator to manage complexity

### Signal 2: Circular Dependencies
**Signal**: Skill A depends on B, B depends on C, C depends on A
**Why It Matters**: Cycles make routing and execution order ambiguous
**Preferred Action**: Redesign to remove cycles or split the work into independent workflows

### Signal 3: False Parallelism
**Signal**: Running skills "in parallel" that actually share resources
**Why It Matters**: Shared resources create contention and non-deterministic behavior
**Preferred Action**: Identify the resource conflicts and run the steps sequentially

### Signal 4: Missing Verification
**Signal**: Implementing features without a verification step
**Why It Matters**: Unverified work can regress silently
**Preferred Action**: End with `verification-before-completion` or an equivalent check

### Signal 5: Premature Optimization
**Signal**: Forcing parallelism where sequential is clearer
**Why It Matters**: Early parallelism adds coordination cost before there is evidence it helps
**Preferred Action**: Start sequential and parallelize only when a bottleneck is confirmed

---

## Pattern Selection Guide

| Task Type | Recommended Pattern | Duration | Complexity |
|-----------|---------------------|----------|------------|
| Add feature | Feature Development Pipeline | 20-40 min | Medium |
| Fix bug | Debug and Document | 15-30 min | Low |
| Quality check | Parallel Quality Checks | 5-10 min | Low |
| Learn codebase | Research-Driven Implementation | 40-60 min | High |
| Multi-language | Language-Specific Quality Gate | 20-35 min | Medium |
| Doc audit | Documentation Audit | 25-40 min | Medium |
| Style enforcement | Style Compliance | 10-15 min | Low |
| Fix violations | Loop Until Clean | 5-20 min | Low |

---

## Advanced Techniques

### Pattern Composition

Combine patterns for complex workflows:

```
Research-Driven Implementation + Style Compliance:
  pr-workflow (miner) → codebase-analyzer → workflow-orchestrator →
  verification-before-completion
```

### Adaptive Composition

Modify execution based on intermediate results:

```
Initial: test-driven-development
If tests reveal complexity: insert systematic-debugging before continue
If code quality low: insert code-linting after tests
```

### Nested Composition

Use workflow-orchestrator to manage sub-compositions:

```
workflow-orchestrator:
  Subtask 1: Feature Development Pipeline
  Subtask 2: Parallel Quality Checks
  Subtask 3: Documentation Audit
```

---

## Performance Optimization

### Parallelization Strategies

**Maximum Benefit**:
- Independent code analysis (linting + documentation)
- Multiple test suites (unit + integration)
- Different quality dimensions (style + security)

**Overhead Considerations**:
- Skill invocation: ~2-3 seconds per skill
- Context passing: ~0.5-1 second per transition
- Parallel coordination: ~10% overhead

**When to Parallelize**:
- Skills take > 30 seconds each
- No shared resource conflicts
- Independent outputs
- 2-4 skills in parallel (sweet spot)

**When to Stay Sequential**:
- Skills take < 10 seconds each
- Output needed by next skill
- Shared resource access
- Complex error recovery needed

---

## Troubleshooting Compositions

### Common Issues

**Issue**: "Skills selected don't match task"
**Cause**: Task analysis failed to identify goals
**Fix**: Make task description more explicit about goals

**Issue**: "Circular dependency detected"
**Cause**: Skills reference each other cyclically
**Fix**: Remove one dependency or split into separate compositions

**Issue**: "Skill outputs incompatible"
**Cause**: Output format doesn't match next skill's input
**Fix**: Add transformation step or choose different skills

**Issue**: "Parallel execution slower than expected"
**Cause**: Resource contention or coordination overhead
**Fix**: Make sequential or reduce parallel skill count

**Issue**: "Loop never terminates"
**Cause**: Exit condition never met or max iterations too high
**Fix**: Lower max iterations or fix exit condition logic

---

This pattern catalog provides proven compositions for common development workflows. Use these as starting points and adapt to your specific needs.
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