One team, one thread.
Tag Paco and bring the PM, engineers, and the idea into one conversation. Assumptions stay visible; the team thinks together before work fractures into parallel AI threads.
Shape with Paco
Shape with Paco.
Discuss the work before you commit to it.
Shaping sessions are collaborative threads where your team and Paco turn a rough idea into a spec before anyone writes code. Start one by tagging Paco with the idea. He arrives having read the repo, the customer calls, the usage data and the decisions your team already made.
Paco asks the questions nobody got around to, traces each assumption through the code before anyone commits to a date, and flags it when the approach and the codebase disagree. Anyone on the team can weigh in while the decision is still open so the reasoning survives the decision.
How It Works
Main features
Context becomes a decision.
Paco turns the discussion into a usable record: options, tradeoffs, risks, acceptance criteria, and who made each call—so the ticket carries the why, not just the ask.
Reality before the estimate.
He traces the team’s assumptions through the repo and existing decisions before anyone promises a date. The result is a PRD your product and codebase can actually support.