agentleFS
kkrlstrmkkrlstrm/gtm-pipeline/CLAUDE.md

gtm-pipeline

CLAUDE.md16 starsChanged 49 days agoApache-2.0View on GitHub

Read AGENTS.md (how the repo works, for any agent) and REVIEW.md (the quality bar). This file adds only what is specific to Claude Code. The fan-out stages run as workflows in .claude/workflows/. Each passes a narrow agent type from .claude/agents/ (web tools only, no skill listing), which keeps each sub-agent's starting context small. Pass agentType: '' in a workflow's args to fall back to the generic sub-agent. Every workflow returns failed[] (or unscored_ids); report those.

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read AGENTS.md (how the repo works, for any agent) and REVIEW.md (the quality bar).

    line 3

≈ “Common” is an estimate: at least 1 in 5 of the 28,029 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

Read AGENTS.md (how the repo works, for any agent) and REVIEW.md (the quality bar). This file adds only what is specific to Claude Code.

Commands

CommandWhat it does
/gtm-setupFirst run: writes your ICP, personas, segments, exclusions and do-not-contact file from your website and a few answers, then checks your setup
/gtm <brief>Runs the pipeline from a plain-English brief
/gtm status <list_id>Shows what ran, what was skipped, cost, and open warnings (from the run ledger)
/gtm resume <list_id>Continues a list from its last completed stage with its frozen plan
/company-discovery, /contact-sourcer, /contact-qualifier, /email-finder, /phone-finder, /activateOne stage on its own

Workflows and agent types

The fan-out stages run as workflows in .claude/workflows/. Each passes a narrow agent type from .claude/agents/ (web tools only, no skill listing), which keeps each sub-agent's starting context small. Pass agentType: '' in a workflow's args to fall back to the generic sub-agent. Every workflow returns failed[] (or unscored_ids); report those.

WorkflowAgent typeModel
discover-companiescompany-researcherSonnet
enrich-companiescompany-intel-researcherHaiku per dimension, Sonnet to synthesize
preview-titlespeople-sourcerSonnet
source-peoplepeople-sourcerSonnet
score-leadslead-scorerHaiku

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.