How do I install the Flow Compat skill?

Run npx skillmds@latest add pwdev-solucoes/flow-compat in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flow Compat safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flow Compat?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flow Compat free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flow Compat?

pwdev-solucoes (@pwdev-solucoes) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flow Compat by pwdev-solucoes — Agent Skill

Name: Flow Compat
Rating: 4.5 (4 reviews)
Author: pwdev-solucoes

File contents

Route PWDEV Code Intent to PWDEV Flow

Read migration before routing legacy initialization or project adoption. Read fleet and delegation before routing their respective operational commands.

Supported routing

Legacy intent	Canonical skill
`init`, `session`	`$flow-init`
`quick`	`$flow-quick`
`discover`	`$flow-discover`
`design`	`$flow-design`
`plan`	`$flow-plan`
`execute`	`$flow-execute`
`review`	`$flow-review`
`verify`	`$flow-verify`
`product`	`$flow-product`
`memory`	`$flow-memory`
`simplify`	`$flow-simplify`
`health`	`$flow-health`
`maintenance`	`$flow-maintenance`
`audit`	`$flow-audit`
`fleet`	`$flow-fleet`
`delegate`	`$flow-delegate auto`
`codex`	`$flow-delegate` with explicit provider `codex`
`opencode`	`$flow-delegate` with explicit provider `opencode`
`kimi`	`$flow-delegate` with explicit provider `kimi`
`gemini`	`$flow-delegate` with explicit provider `gemini`
`kiro`	`$flow-delegate` with explicit provider `kiro`

Procedure

Parse only the legacy command name and user-supplied arguments. Use automatic provider selection only for delegate; preserve the explicit provider for provider-named routes.
Report ROUTE: <legacy> -> <canonical>.
Follow the canonical skill completely, including its inspection, safety, approval, artifact, and verification rules.
Keep all new portable and operational state under .planning/flow/; never translate Flow output back into .planning/fleet, .planning/delegation, or any other legacy layout.
When init or session finds .planning/config.json without .planning/flow/config.json, invoke the $flow-init migration route and stop for approval after the read-only plan.

Constraints

Compatibility never expands user authorization or bypasses canonical approval gates.
Do not migrate files, enable audit, change Git, launch a fleet, install tools, or call external providers merely because a legacy command previously did so. Follow the routed skill's exact confirmation gates.
Do not reuse legacy fleet bookkeeping, Docker projects, tmux sessions, branches, delegation output, or locks.
Do not create one-off aliases or hidden compatibility state.

Output

Return ROUTE, COMPATIBILITY: SUPPORTED, the canonical skill result, and NEXT.

---name: flow-compatdescription: Routes legacy PWDEV Code command intents to their canonical PWDEV Flow skills, preserving history when adopting an existing .planning workspace.---# Route PWDEV Code Intent to PWDEV FlowRead [migration](../../references/migration.md) before routing legacy initialization or project adoption. Read [fleet](../../references/fleet.md) and [delegation](../../references/delegation.md) before routing their respective operational commands.## Supported routing| Legacy intent | Canonical skill ||---|---|| `init`, `session` | `$flow-init` || `quick` | `$flow-quick` || `discover` | `$flow-discover` || `design` | `$flow-design` || `plan` | `$flow-plan` || `execute` | `$flow-execute` || `review` | `$flow-review` || `verify` | `$flow-verify` || `product` | `$flow-product` || `memory` | `$flow-memory` || `simplify` | `$flow-simplify` || `health` | `$flow-health` || `maintenance` | `$flow-maintenance` || `audit` | `$flow-audit` || `fleet` | `$flow-fleet` || `delegate` | `$flow-delegate auto` || `codex` | `$flow-delegate` with explicit provider `codex` || `opencode` | `$flow-delegate` with explicit provider `opencode` || `kimi` | `$flow-delegate` with explicit provider `kimi` || `gemini` | `$flow-delegate` with explicit provider `gemini` || `kiro` | `$flow-delegate` with explicit provider `kiro` |## Procedure1. Parse only the legacy command name and user-supplied arguments. Use automatic provider selection only for `delegate`; preserve the explicit provider for provider-named routes.2. Report `ROUTE: <legacy> -> <canonical>`.3. Follow the canonical skill completely, including its inspection, safety, approval, artifact, and verification rules.4. Keep all new portable and operational state under `.planning/flow/`; never translate Flow output back into `.planning/fleet`, `.planning/delegation`, or any other legacy layout.5. When `init` or `session` finds `.planning/config.json` without `.planning/flow/config.json`, invoke the `$flow-init` migration route and stop for approval after the read-only plan.## Constraints- Compatibility never expands user authorization or bypasses canonical approval gates.- Do not migrate files, enable audit, change Git, launch a fleet, install tools, or call external providers merely because a legacy command previously did so. Follow the routed skill's exact confirmation gates.- Do not reuse legacy fleet bookkeeping, Docker projects, tmux sessions, branches, delegation output, or locks.- Do not create one-off aliases or hidden compatibility state.## OutputReturn `ROUTE`, `COMPATIBILITY: SUPPORTED`, the canonical skill result, and `NEXT`.

Frequently asked questions

Flow Compat