[ PACK LIBRARY / BUSINESS OPERATIONS ]
REQUIRES
Strategy that gets decided in a meeting and never costed or executed is the default failure mode of quarterly planning. This chain hands the quarter down a line: Chief sets objectives, Wags turns them into a costed sprint plan in Linear, and Milton reconciles the plan against budget. Each handoff has a defined artifact, so the quarter is executable and affordable before anyone starts building.
claude plugin install pm-execution@pm-skills (Product Compass pm-skills marketplace — third party)claude plugin install core@b-open-io (provides linear-planning and cost-tracking)claude mcp add --transport http linear-server https://mcp.linear.app/mcp, then /mcp to authenticatebo-cost-report){{COMPANY_STRATEGY}} # 2-4 sentences: this quarter's strategic priority
{{TEAM}} # the team the OKRs and sprints are for
{{QUARTER}} # e.g. "Q3 2026"
{{LINEAR_TEAM}} # Linear team name/id to create issues in
{{QUARTER_BUDGET}} # the budget envelope this quarter's work must fit inside
Run a three-link quarterly planning chain for {{TEAM}}, {{QUARTER}}. Each link
produces a named artifact the next link consumes. Do not skip a handoff.
LINK 1: Chief (paperclip:ceo) sets direction.
Load pm-execution:brainstorm-okrs. Using {{COMPANY_STRATEGY}}, generate three
candidate OKR sets for {{TEAM}}, each with one objective and exactly three
measurable key results at 60-70% confidence. Chief picks ONE set and states why.
Handoff artifact: the chosen OKRs (objective + 3 measurable KRs + rationale).
"Done" means: KRs are outcome metrics, not output counts, and each is independently
measurable.
LINK 2: Wags (core:project-manager) turns OKRs into a costed sprint plan.
Receive Chief's OKRs. Load pm-execution:sprint-plan to shape the first sprint toward
the KRs (capacity, story selection, dependencies, risks). Then load
core:linear-planning: decompose into an epic + stories with acceptance
criteria, present the full issue tree, and STOP at the approval gate. Only create
Linear issues in {{LINEAR_TEAM}} after explicit approval.
Handoff artifact: the approved Linear epic + issues, plus a rough effort estimate
per story. "Done" means: every issue has a testable acceptance criterion and links
back to a specific KR.
LINK 3: Milton (paperclip:cfo) reconciles against budget.
Receive the sprint plan. Load dev-ops:cost-tracking. Estimate the AI/infra cost
of executing the planned work (agent-hours by model tier, expected Vercel/Railway
load) and compare it against {{QUARTER_BUDGET}}. If the plan exceeds budget, name
the specific stories to cut or defer and hand that back to Wags to re-scope.
Handoff artifact: a budget verdict; fits / does-not-fit; with the delta and, if
over, a concrete cut list.
Negative prompts: do not create Linear issues before the approval gate. Do not invent
budget figures; Milton uses real cost-tracking data and states assumptions. Do not
let a link proceed on a vague artifact; if the OKRs are not measurable or the issues
lack acceptance criteria, send them back one link.A chosen OKR set, an approved Linear epic with costed, acceptance-criteria-backed issues in your team, and a budget verdict that either green-lights the quarter or returns a specific cut list. The quarter is decided, tracked, and affordable in one pass.
bo-linear-sprint-cadence — Set up a Linear-native sprint cadence with automatic retro capturebo-cost-investor-chain — Milton to Chief to Tina: cost anomaly to reprioritization to investor notebo-quarter-in-a-box — Run a full quarterly planning cycle: OKRs to roadmap to sprint to retro