mcpbeat

Workflow

notque/workflow

Structured multi-phase workflows: review, debug, refactor (tidy, clean up, untangle messy code without behaviour change), deploy, create, research.

242k tokens
context cost
the whole folder, loaded on every use
104
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
413
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/notque/vexjoy-agent --skill workflow

The instruction itself

4 sections, as written by the author

Workflow

Umbrella skill for all structured multi-phase workflows.

Load the appropriate workflow reference based on the task.

Terminology: "workflow" is the canonical term for these flows. "pipeline" is the retained legacy alias — kept for back-compat. Routing keys, meta.name exports, and pipeline-index.json keep their existing "pipeline" identifiers unchanged; do not rename them. Use "workflow" in new prose.

Available Workflows

| Category | Workflow | Reference |

|----------|----------|-----------|

| Code Review | Comprehensive multi-wave review | references/comprehensive-review.md |

| Code Review | Systematic code review | skills/review/systematic-code-review/SKILL.md |

| Debugging | Evidence-based debugging pipeline | references/systematic-debugging.md |

| Refactoring | Safe refactoring with test gates | references/systematic-refactoring.md |

| Features | End-to-end feature lifecycle | skills/process/feature-lifecycle/references/pipeline.md |

| PR Workflow | PR creation pipeline | skills/process/pr-workflow/references/pipeline.md |

| Research | Formal research with source gates | references/research-pipeline.md |

| Research | Research to article pipeline | references/research-to-article.md |

| Content | Voice content generation | references/voice-writer.md |

| Content | Article evaluation | references/article-evaluation-pipeline.md |

| Content | De-AI content pipeline | references/de-ai-pipeline.md |

| Content | Documentation pipeline | references/doc-pipeline.md |

| Exploration | Codebase exploration | references/explore-pipeline.md |

| Exploration | Multi-perspective analysis | references/do-perspectives.md |

| Creation | Skill creation pipeline | references/skill-creation-pipeline.md |

| Creation | Hook development pipeline | references/hook-development-pipeline.md |

| Creation | MCP server pipeline | references/mcp-pipeline-builder.md |

| Creation | Pipeline scaffolding | references/pipeline-scaffolder.md |

| Creation | Domain research for pipelines | references/domain-research.md |

| Creation | Chain composition | references/chain-composer.md |

| Creation | Auto-pipeline generation | references/auto-pipeline.md |

| Upgrade | Agent/skill upgrade | references/agent-upgrade.md |

| Upgrade | System upgrade | references/system-upgrade.md |

| Upgrade | Toolkit improvement | references/toolkit-improvement.md |

| Testing | Pipeline test runner | references/pipeline-test-runner.md |

| Testing | Pipeline retro | references/pipeline-retro.md |

| GitHub | Profile rules extraction | references/github-profile-rules.md |

| Orchestration | Task orchestration | references/workflow-orchestrator.md |

| Patterns | Composable-pattern + failure-mode + cost-gate catalog | references/workflow-patterns.md |

| Patterns | Tournament (pairwise-comparison) template | references/tournament-workflow.md |

| Patterns | Quarantine (untrusted-source triage isolation) | references/quarantine-pattern.md |

| Orchestration | DAG-based multi-skill composition patterns | references/dag-composition-patterns.md |

| Orchestration | Skill compatibility matrix for chaining | references/dag-compatibility-matrix.md |

| Orchestration | Common DAG skill patterns | references/dag-skill-patterns.md |

| Orchestration | DAG orchestration worked examples (standard sequential/parallel compositions) | references/dag-orchestration-examples.md |

| Orchestration | Error recovery, circular-dependency detection, adaptive/nested composition, performance metrics | references/dag-orchestration-advanced.md |

How to Use (MANDATORY)

You MUST load the named target before executing any workflow phase. The table above is a routing index — the actual methodology, phases, gates, and instructions are in its references or standalone skills.

  • Identify the workflow category from the user's task using the table above
  • Load the matching target. references/... paths resolve under ${CLAUDE_SKILL_DIR}; skills/.../SKILL.md paths are standalone public skills rooted at the repository.
  • Follow the phases and gates defined in that reference exactly — do not improvise phases
  • Report using the output format specified in the loaded reference

If the task spans multiple workflows (e.g., research then write), load each reference in sequence and follow them in order.

Workflow rule: Load the named target before executing a workflow phase. The table shows names only; the target contains the actual instructions, gates, artifact requirements, and quality criteria.

Reference Loading Table

| Signal | Load These Files | Why |

|---|---|---|

| Code Review | comprehensive-review.md | Comprehensive multi-wave review |

| Code Review | skills/review/systematic-code-review/SKILL.md | Systematic code review |

| Debugging | systematic-debugging.md | Evidence-based debugging pipeline |

| Refactoring | systematic-refactoring.md | Safe refactoring with test gates |

| Features | pipeline.md | End-to-end feature lifecycle |

| PR Workflow | pipeline.md | PR creation pipeline |

| Research | research-pipeline.md | Formal research with source gates |

| Research | research-to-article.md | Research to article pipeline |

| Content | voice-writer.md | Voice content generation |

| Content | article-evaluation-pipeline.md | Article evaluation |

| Content | de-ai-pipeline.md | De-AI content pipeline |

| Content | doc-pipeline.md | Documentation pipeline |

| Exploration | explore-pipeline.md | Codebase exploration |

| Exploration | do-perspectives.md | Multi-perspective analysis |

| Creation | skill-creation-pipeline.md | Skill creation pipeline |

| Creation | hook-development-pipeline.md | Hook development pipeline |

| Creation | mcp-pipeline-builder.md | MCP server pipeline |

| Creation | pipeline-scaffolder.md | Pipeline scaffolding |

| Creation | domain-research.md | Domain research for pipelines |

| Creation | chain-composer.md | Chain composition |

| Creation | auto-pipeline.md | Auto-pipeline generation |

| Upgrade | agent-upgrade.md | Agent/skill upgrade |

| Upgrade | system-upgrade.md | System upgrade |

| Upgrade | toolkit-improvement.md | Toolkit improvement |

| Testing | pipeline-test-runner.md | Pipeline test runner |

| Testing | pipeline-retro.md | Pipeline retro |

| GitHub | github-profile-rules.md | Profile rules extraction |

| Orchestration | workflow-orchestrator.md | Task orchestration |

| Patterns / cost gate / failure modes | workflow-patterns.md | Which named pattern + when to escalate + when NOT to use |

| Tournament | tournament-workflow.md | Pairwise-comparison ranking template |

| Quarantine | quarantine-pattern.md | Isolate untrusted-source readers from privileged actions |

| DAG orchestration, multi-skill chaining, dependency resolution | dag-composition-patterns.md, dag-compatibility-matrix.md | Proven multi-skill composition patterns and compatibility (from demoted skill-composer). |

| DAG skill patterns, skill chain troubleshooting | dag-skill-patterns.md, dag-orchestration-examples.md | Common patterns and worked examples (from demoted skill-composer). |

| Error recovery, circular-dependency detection, adaptive/nested skill composition, aggregate performance metrics | dag-orchestration-advanced.md | Advanced/failure-path worked examples split out of dag-orchestration-examples.md to stay under the 500-line reference limit (ADR-001). |

How to use it

Copy the folder

Take notque/workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.