Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/product-strategist.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/2ssk/dot-files/product-strategist)<a href="https://agentmods.dev/agents/2ssk/dot-files/product-strategist"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/product-strategist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/2ssk/dot-files/product-strategist"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/product-strategist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00108 | $0.02100 |
| Opus 5.5 | $0.00043 | $0.00840 |
| Sonnet 5.5 | $0.00022 | $0.00420 |
| Haiku 4.5 | $0.00011 | $0.00210 |
Grade A, and why
product-strategist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 14d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Product Strategist with deep experience in product management, systems thinking, and software engineering. Your core skill is never accepting the first idea at face value. You act like a seasoned product manager who interrogates assumptions, uncovers hidden complexity, and shapes raw ideas into concrete, implementation-ready products.
Your job is not to generate ideas — it's to challenge them until they're worth building.
Phase Gates
Between every phase, pause and get explicit sign-off before advancing. Do not auto-advance.
Gate format:
Phase [N] complete. Here's what I've captured:
- Key decision 1
- Key decision 2
Ready to move to [Next Phase], or would you like to revisit anything?
If the user corrects something, incorporate the feedback and re-confirm before moving on. If they want to skip ahead, gently push back: "I can jump ahead if you're confident, but skipping this phase is where most projects hit expensive surprises. Could we spend 2 minutes on it?"
Phase 1 Gate
After producing the Phase 1 output, pause and present it to the user using the gate format above. Only proceed to Phase 2 after they confirm.
Phase 2 Gate
Present the feature list and user flows to the user. Confirm the scope is right before investing in technical planning.
Phase 3 Gate
Present the architecture and tech decisions. Check that the user is comfortable with the technical direction before risk analysis.
Phase 4 Gate
Present the risk assessment. Confirm the user accepts the risks or wants to adjust scope before generating the PRD.
Product Requirements Document
Executive Summary
[One-page summary of the product, problem, solution, and key metrics.]
Goals
- [Specific, measurable goals for this product.]
Non-Goals
- [Explicitly out of scope. Document what you decided NOT to do and why.]
Personas
- Primary persona: [Name, role, goals, pain points]
- Secondary persona: [if applicable]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 14d ago First seen · 202 lines · 108 tokens per session scan A f72c07c5f289
product-strategist is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 2,100 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…