tflow

Use when a raw request should go to whichever tflow skill fits best — when it is unclear which family member applies, or the request needs sharpening, delegation, and an acceptance check against criteria fixed before any work starts

Use when authoring or hardening a portable Agent Skill (a SKILL.md plus its scripts and references) that must stay valid and distributable across Claude Code and Codex skill directories

Use when the gateway itself must never appear in its own routing table

Use when a non-tflow skill must be ignored by discovery

Use when alpha fixture routing applies

Use when beta fixture routing applies

Use when the user shares a raw, vague, or first-draft prompt and wants it clarified, tightened, strengthened, or made more reliable — or asks to improve, rewrite, or optimize a prompt, write a system prompt, or apply prompt-engineering techniques like few-shot examples, chain-of-thought, role framing, or XML structuring

Use when a raw Agent Skill idea must become a tested, reviewed, and documented skill through the full eight-step pipeline; for a single phase alone, use the matching phase skill directly

Use when an Agent Skill needs a TDD-style test plan before authoring, or a finished skill needs the three-layer test pass — structural gate, deterministic script checks, and judged eval scenarios

Use when a raw Agent Skill idea needs interactive shaping into a research-ready idea brief — surfacing the core purpose with Five Whys and a human-chosen direction before any research or authoring begins

Use when bundled shell syntax must be checked without shellcheck

Use when a decision needs bounded web research before committing — comparing options, picking an approach, or pressure-testing an existing idea — and the answer must be traceable to opened sources rather than model memory

Use when formatting a report before sending it to a teammate

Use when a focused agent capability belongs in a reusable portable skill

Use when compatibility must remain a scalar string

Use when duplicate frontmatter fields must fail

Use when: colon-space makes an unquoted YAML scalar invalid

Use when metadata values must remain strings

Use when unknown frontmatter fields must fail

Use when quoted frontmatter scalars need portable validation

Use when an observable trigger condition applies to the current state

Use when you need information about typically uninstalled prior art

Use when you need to test detection of at-path references in the body

Use when you need to test name pattern validation

Use when you need to test body line count enforcement

Use when you need to test name-to-directory mismatch detection

Use when you need to test name length validation

This skill helps you do things without the required prefix

Use when creating a new skill with the scaffold tool

Use when you need a canonical example of a well-formed skill that passes all quality checks