Notre avis
Cette compétence orchestre la transition entre les phases d'un pipeline de développement en découvrant la phase suivante et en créant un plan pour le transfert de contexte.
Points forts
- Automatise la continuité entre les phases sans intervention humaine.
- Utilise un script de découverte pour identifier l'état actuel.
- Génère un plan structuré pour le prochain contexte.
Limites
- Nécessite que le script de découverte soit correctement installé et exécutable.
- Dépend des références de continuation spécifiques au type de travail.
Utilisez cette compétence après avoir terminé une phase de développement pour passer automatiquement à la phase suivante sans perte de contexte.
Ne l'utilisez pas si vous préférez décider manuellement des prochaines étapes ou si le pipeline n'est pas encore défini.
Analyse de sécurité
SûrThis skill only executes a predetermined script (discovery.sh) that outputs YAML for pipeline phase discovery. It has no external inputs, no network calls, and no destructive commands. The Bash tool is restricted to that script, making execution safe.
Aucun point d'attention détecté
Exemples
The technical specification for the login feature is complete. Route to the next phase.I have finished the analysis for bug #42. What's the next phase in the bugfix workflow?The design phase for the greenfield project 'MyApp' is done. Show me the current state and available actions.name: workflow-bridge user-invocable: false allowed-tools: Bash(.claude/skills/workflow-bridge/scripts/discovery.sh)
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:
.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:
- Use discovery output to compute a single
next_phase - Call
EnterPlanModetool, write plan file with instructions to invokestart-{next_phase}with topic + work_type - Call
ExitPlanModetool 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.
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.