Workflow

Organization

g2i-ai

workflow

Orchestrate the repo workflow from brief through draft PR using skills and thin role wrappers.

Overview

Publisher	g2i-ai
Repository	`agents`
Skill name	`workflow`
Stars	53
Forks	2
Bundled files	Instructions only
Links	Skill source Repository

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by g2i-ai on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/g2i-ai/agents/tree/main/skills/workflow
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.

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/g2i-ai/agents.git /tmp/agents
mkdir -p .claude/skills
cp -r /tmp/agents/skills/workflow .claude/skills/workflow

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable 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 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 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.

Workflow

Objective

Coordinate the standard delivery flow:

brief -> spec -> tdd -> code -> review -> draft-pr

This is a skill entry point, not a command wrapper. Keep the orchestration light and route work into the stage skills instead of duplicating their guidance here.

Instructions

Ask for the feature or change name and which stage range to run (full, partial like spec -> code, or resume from an existing artifact).
Check which stage artifacts already exist before asking the user to recreate them:
- docs/briefs/
- docs/specs/
- docs/qa/reports/
For each selected stage, invoke the matching skill (brief, spec, tdd, code, review, draft-pr). Each skill self-routes via its own Invocation preface: brief, spec, tdd, code, and test run inline in the current chat under the appropriate persona, while review, draft-pr, and pr-description default to delegating to their owning subagent.
After each stage, summarize:
- what was produced
- which paths changed or were created
- open decisions or blockers
- the next recommended skill
Keep context compact. Prefer referencing existing artifact paths over restating full document contents.
Do not create workflow state files or command-era JSON checkpoint files in Phase 1.

PR validation (before `draft-pr`)

Prefer targeted checks while iterating; do not rerun full verification on every tiny commit by default.
Before opening or updating a PR: run a full verification pass from the repo root. Include builds when the change touches app/runtime code, config, dependencies, or anything that could affect shipped output.
Docs-only edits (markdown with no runtime effect): a full build is not required; still run linting when the diff touches linted paths.
On follow-up pushes to an open PR, rerun checks when the changeset meaningfully affects verified code.

Stage Outputs

brief -> docs/briefs/{feature}.md
spec -> docs/specs/{feature}.md
tdd -> failing or newly added unit tests
code -> implementation and verification results
review -> docs/qa/reports/{date}-{branch-or-pr}.md
draft-pr -> branch, commit, and draft PR output

Frequently asked questions

What does the Workflow AI skill do?

Orchestrate the repo workflow from brief through draft PR using skills and thin role wrappers.

Why use Workflow on TypingMind?

Because you install it once and use it with any model. 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 Workflow in TypingMind?

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

Which AI models can use 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 Workflow?

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

Is the Workflow AI skill free?

It is published on GitHub by g2i-ai. Check the repository for licensing terms. 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.

View all

Subagent Driven Development

obra

CommunityPopular

Use when executing implementation plans with independent tasks in the current session

Unified Memory

Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer…

Draw Your Font

Turn a handwriting photo into an installable TTF font.

Adversarial Ux Test

Roleplay a hostile user to find and triage UX pain points.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Workflow

Objective

Instructions

PR validation (before draft-pr)

Stage Outputs

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

PR validation (before `draft-pr`)