Use for engineered or project-based deals that run from spec-shaping through tender, bid, contract, and site handover.
Instructions your experts follow when using this skill.
Use this for engineered or project-based deals. Start from the project or tender, the consultants or architects shaping the spec, the bid deadline and bond or qualification needs, the distributor or engineering, procurement and construction (EPC) partners involved, and the handover site and date if known.
Map which consultants and architects write the requirements, what language favors your solution, and the dated steps to get it specified. Prescription work is dated like any close step.
Confirm the design meets the spec, prep the bill of quantities (BoQ) with quantities the buyer has confirmed, and price only against the validated BoQ.
Survey, solution, design, tender, bid, contract, handover. Each stage has an owner, a date, and an exit test. A stage is done only when its exit test passes.
One tracker across engineering, supply, distributors, and the buyer, with the most-stuck item first at every check. Distributors get tasks with dates, not FYIs. Introduce new products through the channel: train and enable the distributors who will quote and support them, and log who was trained on what and when.
Confirm install or delivery readiness, open items with owners and dates, and the service contact the site calls first. Nothing is "done" with unnamed open items.
The spec-shaping plan with dated steps, the validated BoQ, the stage plan with exit tests, the EPC tracker with the stuck item first, the distributor training log, and a handover sheet with open items.
No spec access means you draft the consultant-discovery questions and work from the published tender docs. No BoQ inputs means you list the quantities needed and who confirms each.
Nothing goes to the buyer, the consultant, or the EPC and no price or delivery date 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.