smithery/7tsuno

progressive-workflow

Execute pre-defined workflows step by step. Use when user wants to run a workflow or mentions "workflow". Each step is executed in isolation to maintain focus throughout multi-step tasks.

Installation

$ npx skills add smithery/7tsuno --skill progressive-workflow

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,744 B
  • docs SUMMARY.md 215 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Progressive Workflow

Execute pre-defined workflows one step at a time.

Execution Flow

  1. Get workflow catalog
  2. Select workflow based on user's request
  3. Get args definition for selected workflow
  4. Ask user for missing required args
  5. Execute each step using getnextprompt.js

Step 1: Get Catalog

node <SKILL_DIR>/scripts/get_workflow_catalog.js

Returns:

[{"id": "review", "name": "Review", "description": "Code review"}]

Step 2: Get Args (after selecting workflow)

node <SKILL_DIR>/scripts/get_workflow_args.js <workflow_id>

Returns:

[{"name": "PR_NUMBER", "description": "PR number", "required": true}]

If required args are missing from user's request, ask the user.

Step 3: Execute Steps

node <SKILL_DIR>/scripts/get_next_prompt.js <workflow_id> <step_index> '<variables_json>'

Returns:

{"step_index": 0, "prompt": "...", "total_steps": 3, "is_last": false}

Execute the returned prompt, then call with stepindex + 1 until islast is true.

Important

  • Never read workflow.yaml directly. Always use getnextprompt.js to get one prompt at a time.
  • NEVER skip steps or try to "optimize" by doing multiple steps at once. Always execute each step one by one using getnextprompt.js until is_last is true.
  • Even if the steps seem repetitive or predictable, you MUST call getnextprompt.js for each step. The workflow is designed to maintain focus and prevent context overload.