Results for “one-on-ones”

Launch new products from idea to first customers using frameworks for positioning, outreach, and experimentation.

Provides evidence-first revenue, pricing, refunds, team-billing, and billing-model truth workflows for sales snapshots, pricing comparisons, duplicate-charge diagnosis, or code-backed billing reality.

Create a practical onboarding plan for a new team member with outcomes, first-week structure, stakeholder introductions, learning path, and manager check-ins.

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

Design the small details—triggers, rules, feedback, loops, and modes—that separate good products from great ones, based on Dan Saffer's framework.

Use when a project's durable context needs to be seeded or refreshed — creating or updating docs/product/context.md (overview + digest + source index + glossary + Know/Don't-Know ledger + design context + technical context) in the target repo; when a project has no context layer yet (Stage-0 setup); when domain terminology is still forming or has drifted; after a meeting, new evidence batch, or scope change that outdates the current context. Also use to ingest new docs/product/input/ batches into the digest. Do not use for repo scaffolding or CI setup, for writing the discovery plan, PRD, or epics (use discovery-plan, prd-writer, epics), or for creating or revising Jobs to be Done — this skill records finished JTBDs by id and marks missing ones TBD; jobs-to-be-done owns minting them.