Compose Workflow logo

Compose Workflow

Community
danielvm-git
compose-workflow

Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes.

Overview

Publisherdanielvm-git
Repositorybigpowers
Skill namecompose-workflow
Stars
206
Forks
18
Bundled files
1
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by danielvm-git on GitHub. Read the source before you install it.

Installation

Install the Compose Workflow AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p .claude/skills
cp -r /tmp/bigpowers/skills/compose-workflow .claude/skills/compose-workflow
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Compose Workflow in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Compose Workflow on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Compose Workflow is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

story: e09s01

story: e45s27

story: e21s04

Compose Workflow

HARD GATE — HARD GATE — Workflows are orchestration, not automation. Do NOT create workflows for tasks that should be single skills. Workflow complexity must be justified.

Process

  1. Interview: goal, phases, which skills, gates between steps.
  2. Write specs/workflows/<name>.yaml:
    • name, command, description, skills[], verify
    • Optional: args for skill-specific arguments
  3. Register in state.yaml Active Decisions.
  4. Optional: reference from orchestrate-project Ad-Hoc mode.

Prefer the YAML recipe format over the legacy specs/WORKFLOW-<name>.md markdown format. YAML recipes are command-mappable, machine-readable, and listed in the Standard Recipe Library.

Terminal-state taxonomy (e45s27)

Every workflow step and /loop tick MUST exit with exactly one terminal state:

StateMeaningNext action
successStep verify passed; artifacts writtenAdvance to next skill in recipe
no-opNothing to do (already green / already applied)Skip step; advance
blockedExternal gate (approval, red CI, missing dep)diagnose-stall or escalate to user
exhaustedMax iterations/cycles reached (review cap, dispatch cycles)Stop; human decision required

Record terminal state in specs/state.yaml handoff.last_terminal_state when a recipe step completes. /loop ticks that produce no progress for two consecutive wakes → invoke diagnose-stall.

Standard Recipe Library

Pre-built recipes in specs/workflows/ map agentic stack commands to skill chains. Reference them in AGENTS.md so /command directly invokes the matching recipe.

CommandWorkflowSkill chain
/check-stackcheck-stacksurvey-context → assess-impact → setup-environment
/shipshipaudit-code → commit-message → release-branch
/tddtdddevelop-tdd → enforce-first
/code-reviewcode-reviewaudit-code → request-review → respond-review
/securitysecurityaudit-code → request-review
/planplansurvey-context → research-first → plan-work
/build-fixbuild-fixinvestigate-bug → diagnose-root → develop-tdd → validate-fix
/e2ee2esmoke-test → verify-work

Add to AGENTS.md:

/check-stack = compose-workflow check-stack
/ship        = compose-workflow ship

Verify

→ verify: [ "$(ls specs/workflows/*.yaml 2>/dev/null | wc -l | tr -d ' ')" -ge 8 ]

See REFERENCE.md for template.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Compose Workflow AI skill do?

Chain multiple bigpowers skills into a custom workflow recipe saved in specs/. Use when a project repeats a non-standard skill sequence, or user wants a documented playbook beyond orchestrate-project modes.

Why use Compose Workflow on TypingMind?

Because you install it once and use it with any model. Compose Workflow is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Compose Workflow in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/danielvm-git/bigpowers/tree/main/skills/compose-workflow. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Compose Workflow?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Compose Workflow?

As many as you like. As long as a model supports skills, you can use Compose Workflow with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Compose Workflow AI skill free?

Yes. It is published on GitHub by danielvm-git under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
nexu-io logo

Html Ppt Taste Brutalist

nexu-io
OrganizationPopular

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration.…

11.2K
96.7K
1 files
View
addyosmani logo

Code Review And Quality

addyosmani
CommunityPopular

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple…

10.1K
95.8K
Instructions
View
addyosmani logo

Security And Hardening

addyosmani
CommunityPopular

Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login…

10.1K
95.8K
Instructions
View
addyosmani logo

Shipping And Launch

addyosmani
CommunityPopular

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up…

10.1K
95.8K
Instructions
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇