agentleFS
lenar-amirovlenar-amirov/product-pipeline-public/.claude/skills/pipeline-steps/SKILL.md

pipeline-steps

Skill13 starsChanged 5 months agoMITView on GitHub

Map of pipeline steps (0-19) and jobs with registry rules; detailed per-step instructions live in references/steps.md. Read this whenever the PM calls a pipeline command (/analyze-cjm, /validate-problems, …) or a job, then read the matching section of references/steps.md.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every job runs standalone: no initiative → work on chat context, type evidence INFERRED, offer to persist afterwards.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
SKILL.md

Pipeline Step Instructions

Navigation layer: jobs map + registry rules here, per-step details in references/steps.md (read only the section you are executing).

Jobs → steps. Jobs are the primary interface (CLAUDE.md → JOBS CATALOG): /hypotheses → steps 1–2 · /brief → 4/5/11 · /validate → 6 · /solutions → 7 · /sketch → 8 · /tickets → create-tickets · /ingest → skill ingest · /next → skill next-advisor · /challenge → skill challenge · /deep-think → skill deep-think. Every job runs standalone: no initiative → work on chat context, type evidence INFERRED, offer to persist afterwards; initiative exists → read and write its registry and artifacts as described per step.

Hypothesis registry (all steps). Hypothesis STATE (status, evidence type, confidence, sources, history) lives in output/hypotheses.json — manage it via python3 tools/scripts/hypotheses.py (add / set / validate / render). set records history automatically. Narrative markdown (hypotheses.md, validated-hypotheses.md) stays authored prose and must not contradict the registry. After changing the registry run hypotheses.py render <dir> to refresh output/registry.md. Legacy initiatives: convert once with python3 tools/scripts/migrate-hypotheses.py <dir>.


Step index

Details for every step live in references/steps.md — read the section for the step you are executing (table of contents at the top; don't load other steps, they aren't needed).

#CommandTypeNote
0/setup-initiativeCore
1/analyze-cjmCore
2/synthetic-researchRecommended
3/competitor-researchRecommended
4/generate-researchRecommended
5/create-survey-audienceOptional
6/validate-problemsCore
7/solution-hypothesesCore
8/sketch-solutionCore
8.5/user-test-conceptOptional; alias for user-testing concept mode
9/review-designRecommended
10/create-presentationCoreProblem Research Report
11/create-design-briefRecommended
12/estimate-with-devCore
13/finalize-prdCore
14/design-ab-testRecommended
15/create-gate2-presentationCoreSolution Research Report
—/create-ticketsafter Gate 2push to tracker via MCP
16/analyze-ab-testRecommended
17/plan-gtmCore
18/create-gtm-materialsOptional
19/support-taskOptional

Gates (steps 10, 15) have machine preconditions — validate-evidence.py --gate must be CLEAR before assembling a deck; offer /challenge to rehearse. External handoffs (steps 4, 5, 11, 12, 14, 16, 18, 19) create dependencies[] entries with owner + deadline.

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.