workflow-bridge — for Claude Code workflow-bridge, portal, community, for Claude Code, ide skills, deterministic, continuation, instructions, invoked, processing

v1.0.0

À propos de ce Skill

Parfait pour les Agents de Développement ayant besoin d'une gestion de workflow avancée et d'une automatisation de phase de pipeline dans des environnements tmux. Resume localise : The workflow-bridge skill enables interactive GO CLI session picking for tmux, benefiting developers who need to manage complex pipeline phases. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Fonctionnalités

Enter plan mode with deterministic continuation instructions.
It creates a plan mode handoff that survives context compaction
Enter plan mode with deterministic continuation instructions
It discovers the next phase and creates a plan mode handoff that survives context compaction
ZERO OUTPUT RULE : Do not narrate your processing

# Sujets clés

leeovery leeovery
[1]
[0]
Mis à jour: 3/11/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Parfait pour les Agents de Développement ayant besoin d'une gestion de workflow avancée et d'une automatisation de phase de pipeline dans des environnements tmux. Resume localise : The workflow-bridge skill enables interactive GO CLI session picking for tmux, benefiting developers who need to manage complex pipeline phases. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Pourquoi utiliser cette compétence

Permet aux agents de créer des passes en mode plan qui survivent à la compaction de contexte, en utilisant des instructions de continuation déterministes et des sessions interactives GO CLI pour une gestion transparente des phases de pipeline, en exploitant des compétences techniques comme la

Meilleur pour

Parfait pour les Agents de Développement ayant besoin d'une gestion de workflow avancée et d'une automatisation de phase de pipeline dans des environnements tmux.

Cas d'utilisation exploitables for workflow-bridge

Automatiser les transitions de phases de pipeline avec des passes en mode plan
Gérer des phases de workflow complexes dans des environnements tmux
Découvrir les prochaines phases de pipeline avec une résilience à la compaction de contexte

! Sécurité et Limitations

  • Nécessite un environnement tmux
  • Dépendante de compétences de traitement comme la discussion technique et la spécification technique
  • La compaction de contexte doit être gérée

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Démo Labs

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ et étapes d’installation

These questions and steps mirror the structured data on this page for better search understanding.

? Questions fréquentes

Qu’est-ce que workflow-bridge ?

Parfait pour les Agents de Développement ayant besoin d'une gestion de workflow avancée et d'une automatisation de phase de pipeline dans des environnements tmux. Resume localise : The workflow-bridge skill enables interactive GO CLI session picking for tmux, benefiting developers who need to manage complex pipeline phases. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Comment installer workflow-bridge ?

Exécutez la commande : npx killer-skills add leeovery/portal. Elle fonctionne avec Cursor, Windsurf, VS Code, Claude Code et plus de 19 autres IDE.

Quels sont les cas d’usage de workflow-bridge ?

Les principaux cas d’usage incluent : Automatiser les transitions de phases de pipeline avec des passes en mode plan, Gérer des phases de workflow complexes dans des environnements tmux, Découvrir les prochaines phases de pipeline avec une résilience à la compaction de contexte.

Quels IDE sont compatibles avec workflow-bridge ?

Cette skill est compatible avec Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Utilisez la CLI Killer-Skills pour une installation unifiée.

Y a-t-il des limites pour workflow-bridge ?

Nécessite un environnement tmux. Dépendante de compétences de traitement comme la discussion technique et la spécification technique. La compaction de contexte doit être gérée.

Comment installer ce skill

  1. 1. Ouvrir le terminal

    Ouvrez le terminal ou la ligne de commande dans le dossier du projet.

  2. 2. Lancer la commande d’installation

    Exécutez : npx killer-skills add leeovery/portal. La CLI détectera automatiquement votre IDE ou votre agent et configurera la skill.

  3. 3. Commencer à utiliser le skill

    Le skill est maintenant actif. Votre agent IA peut utiliser workflow-bridge immédiatement dans le projet.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

workflow-bridge

Install workflow-bridge, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

Enter plan mode with deterministic continuation instructions.

This skill is invoked by processing skills (technical-discussion, technical-specification, etc.) when a pipeline phase concludes. It discovers the next phase and creates a plan mode handoff that survives context compaction.

ZERO OUTPUT RULE: Do not narrate your processing. Produce no output until a step or reference file explicitly specifies display content. No "proceeding with...", no discovery summaries, no routing decisions, no transition text. Your first output must be content explicitly called for by the instructions.

Instructions

This skill receives context from the calling processing skill:

  • Topic: The topic name
  • Work type: greenfield, feature, or bugfix
  • Completed phase: The phase that just concluded

Step 1: Run Discovery

!.claude/skills/workflow-bridge/scripts/discovery.sh

If the above shows a script invocation rather than YAML output, the dynamic content preprocessor did not run. Execute the script before continuing:

bash
1.claude/skills/workflow-bridge/scripts/discovery.sh

The output contains three sections: features:, bugfixes:, and greenfield:. Use the known work type and topic from the calling context to extract the relevant data:

If work type is "feature"

Find the topic entry under features: > topics: and extract its next_phase.

If work type is "bugfix"

Find the topic entry under bugfixes: > topics: and extract its next_phase.

If work type is "greenfield"

Parse the greenfield: section for phase-centric state:

  • state: Counts of artifacts across all phases
  • Phase-specific file lists with their statuses

→ Proceed to Step 2.


Step 2: Route to Continuation Reference

Based on work type, load the appropriate continuation reference:

If work type is "feature"

Load feature-continuation.md and follow its instructions as written.

If work type is "bugfix"

Load bugfix-continuation.md and follow its instructions as written.

If work type is "greenfield"

Load greenfield-continuation.md and follow its instructions as written.


Notes

Feature/bugfix continuation references:

  1. Use discovery output to compute a single next_phase
  2. Call EnterPlanMode tool, write plan file with instructions to invoke start-{next_phase} with topic + work_type
  3. Call ExitPlanMode tool for user approval

The user will then clear context, and the fresh session will invoke the appropriate start-* skill with the topic and work_type provided, causing it to skip discovery and proceed directly to validation/processing.

Greenfield continuation is interactive — greenfield is phase-centric with multiple actionable items, so there is no single next phase. The reference displays state, presents a menu of choices, waits for user selection, then enters plan mode with that specific choice. The plan mode content is deterministic (same as feature/bugfix) once the user has chosen.

Compétences associées

Looking for an alternative to workflow-bridge or another community skill for your workflow? Explore these related open-source skills.

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Resume localise : 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

widget-generator

Logo of f
f

Resume localise : Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

flags

Logo of vercel
vercel

Resume localise : The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

138.4k
0
Navigateur

pr-review

Logo of pytorch
pytorch

Resume localise : Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

98.6k
0
Développeur