Fleet Project Pipeline

Use when running a product through the fleet: stages, gates, kanban cards, briefs, legs, qa fix pairs, merges and the clean-up sweep.

44 starsTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add SamueleBassoli/hermes-fleet-apps --skill fleet-project-pipeline
Manual install
git clone --depth 1 https://github.com/SamueleBassoli/hermes-fleet-apps.git /tmp/hermes-fleet-apps
mkdir -p ~/.claude/skills
cp -r /tmp/hermes-fleet-apps/roles/coordinator/skills/fleet-project-pipeline ~/.claude/skills/fleet-project-pipeline

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Fleet project pipeline

How the coordinator runs one product through the fleet:
`product -> designer -> coder -> qa -> media -> docs`. Read the fleet map
(who does what) before every stage. The coordinator orchestrates, merges and
reports; it never builds the product itself.

The owner decides at two gates only: SPEC (after product) and DESIGN (after
designer). Everything else runs without asking.

## 0. Before the repo exists

- Search for existing FOSS apps and for the data sources (API, licence, rate limits).
  Report in three blocks: what exists, data sources, honest verdict.
- Propose a few names and verify each one with a search; mark each verified/unverified.
- Use trademark-safe wording from day one ("<Brand> data", never "the <Brand> app"): it
  spreads into every brief.
- Check the DATA licence apart from the code licence: open code often serves NC data, which
  rules out ads, paid tiers or donations. Tell the owner before the spec.
- Map every planned feature to a real endpoint of the data source. A feature with no
  endpoint is cut or needs a second source: the owner's call.
- Ask what distribution may cost (signing, stores, certificates) before the spec, not after.

## 1. Repo and identity

- If the owner publishes under more than one identity, git should sign by folder
  (`includeIf` in `~/.gitconfig`). Pick the folder, never set `user.email` by hand.
  After the first commit check `git log --format='%an <%ae>' -1`.
Read the full skill on GitHub

Details

Skill name
fleet-project-pipeline
Path
roles/coordinator/skills/fleet-project-pipeline/SKILL.md
License
MIT
Repo updated
31 October 2026

FAQ

What does the Fleet Project Pipeline skill do?

Use when running a product through the fleet: stages, gates, kanban cards, briefs, legs, qa fix pairs, merges and the clean-up sweep.

How do I install the Fleet Project Pipeline skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add SamueleBassoli/hermes-fleet-apps --skill fleet-project-pipeline. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Fleet Project Pipeline popular?

It lives in SamueleBassoli/hermes-fleet-apps, which has 44 GitHub stars and 0 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.