One-click install
npx skills add https://github.com/curdx/curdx-flow --skill switch-curdx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switch
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/switch
Command: npx skills add https://github.com/curdx/curdx-flow --skill switch-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switching between specs can be error-prone and lose continuity when you need the right requirements, progress, and phase context for the task you are about to continue.

Core Features & Use Cases

  • Multi-directory spec discovery: Resolves spec names across all configured spec roots and supports full-path switching.
  • Safe validation with disambiguation: Lists specs when no argument is given, errors clearly when not found, and forces an explicit full-path choice when multiple matches exist.
  • Continuity-aware context loading: Updates the current spec pointer and surfaces the spec’s phase and progress so you can continue in the correct step.

Quick Start

Run /curdx-flow:switch feature-b to switch to the spec named feature-b in the configured specs directories.

Frequently Asked Questions about switch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I switch the active spec in a multi-root repository without losing progress?

To switch the active spec, provide the spec name or full path to the switch command. It updates the current spec pointer deterministically and surfaces the phase and progress context so you can resume work accurately.

What happens if I try to switch specs by name and multiple matches are found?

When multiple spec matches are found, the system forces an explicit full-path choice to prevent ambiguity. It safely validates the input, errors clearly when a spec is not found, and lists available specs if no argument is given.

How does spec management handle workflow continuity when jumping between different phases?

Spec management handles continuity by loading continuity-aware context when switching. It updates the current spec pointer and reports the spec's phase and progress, ensuring you continue in the correct workflow step.

Do I need specific metadata to activate spec switching in a delivery workflow?

Yes, spec switching requires YAML-frontmatter-defined activation metadata to function. This metadata enables multi-directory resolution via the runtime CLI and ensures strict path and name validation during the switch process.

What is the best way to resolve a spec name across multiple configured spec directories?

The best way to resolve a spec name across multiple directories is using multi-directory spec discovery. The system resolves spec names across all configured spec roots and supports full-path switching for exact targeting.

Why does ambiguous auto-selection fail when managing multiple workflow specs?

Ambiguous auto-selection fails because the system enforces strict path and name validation without ambiguous auto-selection. It requires deterministic current-spec pointer updates to ensure you load the exact requirements needed.