Use when the deal is a credit facility or capital product that needs underwriting and a term sheet, not a SaaS order form.
Instructions your experts follow when using this skill.
Run this when the deal is a credit facility or capital product. Underwrite first, structure inside approval bands, and sequence internal consensus before the borrower ever sees terms.
The borrower's cash-flow picture and capital need, the facility size and use of funds, the underwriting checklist, your approval bands, and the founder, CFO, and lender-side owners.
Inflows, burn or seasonality, existing facilities, and what the new capital unlocks. Every number is FACT with a source or UNKNOWN until the statements arrive.
Size, tenor, pricing, covenants, and collateral shaped to the risk you found. If the ask exceeds the band, say so early with what would need to change.
Economics, conditions precedent, key covenants, and the path from sheet to docs to funding — commercial truth the founder and CFO can sign. Legal language waits for counsel. Label the term_state drafting while you write.
Risk, ops, and exec each get the sheet with the risks named, not hidden. An internal no after a founder yes is the failure mode, so sequence risk before the founder sees terms. The sheet stays term_state in review until every internal owner signs off, then approved.
Founder, CFO, and co-lender steps each carry a date and an owner. A quiet month gets a dated check-in, never a surprise expiry.
The signed sheet (term_state signed) goes with the conditions checklist attached: each condition precedent has an owner and a date, and funding waits on all of them.
Cash-flow read with sourced numbers, an offer inside approval bands, a plain-terms sheet draft, internal consensus log, and a dated cycle tracker through funding.
No financials yet: record the founder's stated numbers as claims, each attributed to them, and leave the number itself UNKNOWN until the statements arrive — the rule above does not bend because the statements are late. List exactly which statements close the gap. No approval bands on file: ask for them before any structure is shown.
Nothing goes to the borrower and no size, price, or term is promised without your explicit yes.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.