signal-forge

Emits reader-specific account copy — outreach sequences, follow-ups, one-pagers, case-study atoms, QBR narratives, renewal and expansion notes — by selecting a typed sequence blueprint and filling its slots only with facts the account already holds, so every piece reads like it was written for one named reader and never like mail-merge. Use when the user says "outreach for [prospect]", "follow-up email", "nurture sequence", "one-pager", "case study", "QBR narrative", "renewal note", "win-back", "expansion copy", or when a factory contract includes 07-copy. Runs one reader or batches a whole list with per-reader verification. Every claim cites SYNTHESIS or is cut; refuses unpersonalizable sends and "just checking in" revivals.

Emits deal-specific bid paperwork from a typed clause system — proposal, contract skeleton, and internal pricing-floor math — by reading SYNTHESIS, computing a cost floor, selecting pricing shapes via a decision tree, and assembling plain-language clauses with bound slots. Use when the user says "write the bid", "proposal draft", "SOW", "contract for [prospect]", "pricing options", "redline their paper", or runs the 03-bid stage of a factory. Operates a level up from a document: a meta-prompt that generates paper, not a template. Never commits to volumes before proof; unknowns surface as flagged TBDs, never silent defaults; final terms always carry an attorney-review caveat.

Builds the touchable sample that enacts the buyer's own workflow step — an interactive single-file prototype, a ceti-method animated explainer, or a live-channel (phone/chat) demo — so the buyer experiences the offer instead of reading about it, with buildable per-form artifact specs and a rehearsed 3-minute run-of-show. Use when the user says "demo for [prospect]", "build the sample", "prototype they can touch", "demo plan", "show don't tell", or as the 04-demo stage of a factory run. A demo the buyer can call or click beats any document; a generic vertical demo demonstrates nothing.

Extracts a prospect's real brand palette from their public materials, harmonizes it into a WCAG 2.2 AA-audited token set, and fuses it with CETI house rigor so every deliverable feels already theirs. Emits design/tokens.css (the versioned sf-tokens schema every artifact skill consumes) and design/palette.md (provenance + contrast matrix). Use when the user says "design DNA for [company]", "extract their colors", "brand the deliverables for this prospect", "tokens for this client", or automatically as the design stage of any factory run before artifacts are built. Refuses to ship invented colors or failing contrast pairs.

Forges a new reusable deliverable FACTORY — a versioned, example-agnostic meta-prompt that serves every future instance of a recurring sales, copywriting, or account-material category, one abstraction level above any single deal. Use when the user says "forge a factory", "/forge", "new factory for X", "we keep making X for clients", "turn this into a standing pipeline", or names a recurring deliverable category (QBR packs, launch copy, onboarding kits, audit reports, renewal decks, partnership pitches). Also use to EDIT an existing factory after feedback — version bumps, slot additions, rule changes — and to run the generalization check on any factory edit. This is the meta-meta skill: it does not produce client artifacts; it mints the machine that produces them.

Hunts a prospect's provable weaknesses and buying tells from public sources and packages them as a typed, cited tells-dossier — the left half of the sign-here bijection (tells ↔ scope ↔ price) that makes the pitch feel painfully obvious. Use when the user says "hunt [company]", "find their tells", "weakness map", "recon this prospect", "why would they buy", "what are their gaps", "build the dossier", or before any bid, deck, demo, or outreach so positioning rests on demonstrated gaps instead of generic value props. Runs one prospect or fans out across many. Produces a cited dossier with severity/provability/monetizability scores, a live-demo wedge list, a quarantined-hypotheses section, and a NEEDS/UNKNOWNS handoff — never client-facing.

The compounding engine of signal-forge — captures reusable knowledge atoms from every run and every human correction, traces each correction to the exact factory line that allowed it, writes append-only ledgers with a same-transaction discoverability index, and refreshes decay-prone atoms on a cadence so run

Builds the proposal slide deck for a prospect — an animated single-file HTML deck by default, .pptx when the buyer's meeting culture demands Office, or both — walking from evidenced weaknesses (tells) to the sign-here moment. Use when the user says "pitch deck", "proposal deck", "slides for [prospect]", "deck for the meeting", or as the 05-deck stage of a factory run. Every number comes from SYNTHESIS; every scope item traces to a tell; the tells ↔ scope ↔ price bijection is the spine. The HTML artifact is a precise, buildable spec (16:9 stage, anime.js v4, `--sf-*` tokens, ≤2.5MB, zero console errors, WCAG AA, prefers-reduced-motion) — not a vibe.

Execute a deliverable factory end-to-end on one prospect signal, or a batch of them — intake, digest, parallel cited research lanes, weakness hunt, synthesis, adversarial citation audit, then fan out the winning artifacts (dashboard, bid, deck, demo, copy). Use when the user pastes a prospect signal (text, email, call note), says "run the factory", "new prospect", "bid package for X", "full pipeline on this lead", "portfolio run" or "run these N leads", "resume the run", or names a registered factory to execute. This is the flagship orchestration harness of signal-forge.

Produce a complete, lab-first workshop or training deliverable set for a client engagement — timeboxed agenda, hands-on labs on the buyer's own stack, facilitator run-of-show, self-sufficient participant handouts, instructional slides, and a metric'd 30/60/90 follow-up. Use when the user says "workshop for [client]", "training kit", "bootcamp materials", "enablement session", "build the academy module", or when a factory's artifact contract includes 06-workshop. Teaching-first: participants leave having DONE the thing, measured against a done-when, not watched it. Refuses overstuffed agendas and labs built on unverified stack assumptions.