product-strategy

Persistent agent that continuously monitors user signals across support, NPS, and feature request channels. Synthesises into a weekly research digest. Surfaces emerging patterns before they become crises. Alerts the PM team when a signal crosses an escalation threshold.

Persistent agent that maintains coherence between the roadmap, the backlog, current specs, and the stated product strategy. Runs three weekly checks: backlog orphan detection, roadmap coverage check, and sprint alignment check. Surfaces drift before quarterly roadmap commitments silently fail.

Persistent agent that ensures the right people always have the right version of product status information. Generates three-version weekly updates (executive, engineering, customer-facing) with PM review gate. Triggers immediately when customer-committed features change status.

Activate for: product brief, discovery brief, problem brief, opportunity brief, problem statement, opportunity framing, how might we, design brief, research brief, discovery scope, kickoff brief, initiative framing, problem definition, hypothesis brief, PM brief, product hypothesis, frame the problem, scope a discovery sprint, initiative alignment. NOT for: feature specifications (use official /write-spec), competitive analysis (use official /competitive-brief), user research synthesis (use official /synthesize-research).

Activate for: user interview, interview guide, interview questions, discovery interview, research interview, customer interview, user research guide, interview script, how to interview users, what to ask users, interview protocol, research protocol, interview template, qualitative research, jobs to be done, JTBD, contextual inquiry, interview planning. NOT for: research synthesis from completed interviews (use official /synthesize-research), competitive analysis (use official /competitive-brief), survey design or quantitative research.

Activate for: PRD, product requirements document, product requirements, full requirements, initiative doc, initiative requirements, platform change, new product, product launch, major release, quarterly initiative, program brief, product vision doc, comprehensive requirements, cross-functional alignment doc, launch plan requirements, multi-team initiative. NOT for: single-feature specifications (use official /write-spec), roadmap planning (use official /roadmap-update), sprint planning (use official /sprint-planning).

Activate for: prioritise, prioritization, backlog prioritisation, backlog order, what to build first, RICE, ICE, MoSCoW, Kano, value vs effort, impact vs effort, backlog ranking, roadmap prioritisation, compare features, what is most important, which feature, product decision, build order, quarterly priorities, should we build this, feature value, rank backlog. NOT for: roadmap planning (use official /roadmap-update), sprint planning (use official /sprint-planning), metrics review (use official /metrics-review).

Activate for: retrospective, retro, post-mortem, post launch review, feature review, what went well, what didn't go well, lessons learned, sprint retrospective, product review, launch review, did it work, measure impact, feature retrospective, post-ship review, outcome review, product retro, evaluate feature success. NOT for: metrics dashboards (use official /metrics-review), stakeholder updates (use official /stakeholder-update), sprint planning (use official /sprint-planning).

Activate for: user stories, write user stories, story, as a user I want, user story map, story mapping, epic, story breakdown, story splitting, acceptance criteria for stories, BDD, given when then, story refinement, sprint stories, story writing, feature to stories, spec to stories, decompose requirements, break down PRD. NOT for: feature specifications (use official /write-spec), sprint planning (use official /sprint-planning), roadmap planning (use official /roadmap-update).