Results for “fork”

Runs focused experiments to validate feasibility of an idea, saving artifacts to .planning/spikes/ and supporting both idea and frontier modes.

Runs a relentless interview session to sharpen a plan or design.

Lark/Feishu CLI router: match intent, then Read the Entry file under lark-*/ (e.g. lark-doc/lark-doc.md). Covers docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, note, event via lark-cli. Use when operating Feishu/Lark workspace resources, messaging, docs, calendars, tasks, OKRs, or Miaoda deploys.

Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", or "anchoring". Also trigger when preparing for vendor negotiations, resolving pricing disputes, or navigating high-stakes conversations where both parties need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product/marketing, see influence-psychology.

Runs an autonomous multi-agent software development pipeline that takes a PRD through to production with zero human intervention, using model-tiered agents, memory, and verification cycles.

Run structured What-If scenario analysis with 4-6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use for speculative questions about uncertain futures, strategic forks, contingency planning, or stress-testing decisions.