Four Contexts that answer one brief together and return a product plan, a design direction, a GTM plan, and an engineering plan. A starting point you sharpen with your own private instructions.
For product managers running a launch across design, GTM, and engineering.
Contexts
4
Product Manager, Designer, GTM Strategist, Software Engineer
How it works
A feature launch fails at the seams. Product writes a plan, design starts late, GTM finds out at the end, and engineering discovers the instrumentation was never scoped. The cost is a slipped date and a launch nobody can measure.
Four Contexts answer the same brief. Product Manager returns backlog-ready outputs with success metrics, rollout phases, and milestones. Designer works inside your existing design system and attaches work to the right tasks with accessibility accounted for from the start. GTM Strategist covers positioning, messaging, rollout communications, and internal enablement. Software Engineer plans feature flags, analytics events, technical checkpoints, and what QA needs for a safe launch. Each Context carries private instructions you write once, which is where your delivery conventions live.
One prompt returns four aligned outputs instead of four meetings. The gaps show up as questions now rather than as surprises in week three.
Run it with
oi product-manager+designer+gtm-strategist+software-engineer help me launch this new feature and return the plan as product, design, GTM, and engineering outputs
What's inside
Each context carries its own private instructions. Add yours and the setup answers the way your work actually runs.
Contexts
We manage delivery in Linear and prefer work to be broken into clear backlog-ready product outputs. Product plans should include success metrics, rollout phases, launch checkpoints, and milestone planning.
Work within our existing design system and interaction patterns. Attach design work to the relevant tasks, account for accessibility from the start, and provide enough fidelity for engineering to begin confidently.
Launch plans should cover positioning, messaging, rollout communications, and internal enablement. Focus on the target segments we care about and the adoption goals we want to hit.
Follow our system design patterns and use feature flags where appropriate. Make sure instrumentation is part of the plan from the beginning. Include analytics events, experiment considerations, technical rollout checkpoints, and what QA needs for a safe launch.
Releases
Shipped the four-Context launch starter with private instructions for delivery conventions, so a rough feature brief returns aligned plans instead of four separate opinions.
Plans a seasonal push from offer and keywords through to ad-ready copy and a channel plan. Works from your product mix, trading geography, and the private instructions on each Context. Never sets an offer outside the promotional limits you already run.
Picks a date night that fits your suburb, your budget, and what your partner can actually eat. Works from your neighbourhood, dietary needs, budget, and the private instructions on the Context. Never suggests a venue that cannot handle the dietary need.
Tests a new market on evidence and numbers before you commit headcount to it. Works from your ACV, margin assumptions, customer profile, and the private instructions on each Context. Never presents an assumption as evidence.
Get started
Install it, connect your tools, and every context, workflow, and guardrail is ready in the clients your team already uses.
