Skip to content
cccskills
FreePublished on GitHub

pipeline-stage-definitions

Define each pipeline stage with an entry rule, an exit rule, and required proof.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Pipeline stage definitions

Use this when reps read stages differently or the forecast leans on stage.

Review how stages are used

From a dated deal export, count deals by stage, median days in stage, and conversion to the next stage. Note stages that are skipped, stages where deals sit for months, and stages that mean different things to different reps. Ask two or three reps how they decide to move a deal.

Write the definitions

For each stage write:

  • what the stage means, in one line;
  • the entry rule: what must be true to move a deal in;
  • the exit rule: what must be true to move it on;
  • the proof: the field, note, or document that shows it;
  • the expected time in stage, from the data, not a target.

Keep the language plain enough that a new rep applies it the same way. Mark any rule that needs a new field.

Deals that do not fit

List open deals that would sit in a different stage under the new rules, with owner and amount. Do not move them; give the list to the sales lead.

Do not change stages, fields, or deals in the CRM yourself. Never set a probability or a stage from a guess; the sales lead approves the definitions.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill