Turn signed contract duties into an owned, source-cited tracker while routing unclear obligations to counsel.
Instructions your experts follow when using this skill.
Use the final signed agreement and all signed amendments. Drafts do not create tracker duties.
Record the responsible party, action, beneficiary, due date or trigger, recurrence, notice method, required evidence, dependency, business owner, status, document and section, exact source text, and last checked date.
Use these statuses: NOT STARTED, IN PROGRESS, EVIDENCE READY, OWNER CONFIRMED COMPLETE, BLOCKED, and UNCLEAR. Ellis does not mark completion without owner evidence.
Calculate a date only where the trigger and period are clear; show the formula. Keep continuing duties separate from one-time duties. Link amendments to the rows they change rather than overwriting source history.
Do not decide who legally bears an unclear duty, whether performance satisfies the contract, whether a breach occurred, or whether notice is valid. Route those questions to counsel with the source text.
Return the tracker, upcoming owner actions, missing evidence, and unclear items. Do not send notices, certify completion, waive a duty, or change a deadline.
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.