strategy-connector
Skill3 starsChanged 19 days agoMITView on GitHub
Help PMs map any work item (feature, experiment, initiative) to strategic goals and OKRs. Use before PRDs, backlog prioritization, or planning.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ianklassen/ai-pm-systemedited, first seen Apr 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- ianklassen/ai-pm-system★ 193% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- company-product-signalsSkill
- company-researcherSkill
- company-strategySkill
- pm-os-onboardingSkill
- brainstormingSkill
- continual-learningSkill
- decision-loggerSkill
- eval-briefSkill
- exec-communicatorSkill
- experiment-designerSkill
- experiment-writeupSkill
- knowledge-updaterSkill
- launch-postSkill
- launch-readinessSkill
- meeting-to-actionsSkill
- one-pagerSkill
- pptx-creatorSkill
- prd-writerSkill
- stakeholder-updateSkill
- what-ifSkill
- working-backwardsSkill
- writing-clearlySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before writing a PRD
- Distinctive: line 16
When asked "how does this tie to strategy?"
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strategy Connector
Help PMs map work items to strategic goals and OKRs. Ensures features, experiments, and initiatives are explicitly tied to organizational strategy and measurable outcomes.
When to Use
- Before writing a PRD
- Backlog prioritization
- Quarterly or annual planning
- Leadership presentations
- When asked "how does this tie to strategy?"
- Justifying resource allocation
Process / Template
1. Understand the Work Item
- What is it? (feature, experiment, initiative)
- Who is it for?
- What problem does it solve?
- What's the expected outcome?
2. Reference Strategic Context
- Pull from
knowledge/products/<product>/brief.mdandstrategy.md, then orgknowledge/_template/strategy.mdif needed - Identify: strategic pillars, OKRs, key metrics, target segments
- Note: what is the organization optimizing for?
3. Map the Connection
For the work item, articulate:
Strategic Pillar
- Which pillar or theme does this support?
- How does it advance that pillar?
OKR / Goal
- Which objective or key result does this contribute to?
- What's the causal path? (this work → metric movement → OKR)
Segment / Persona
- Which customer segment or persona does this serve?
- Is this segment a strategic priority?
Metric Impact
- What metric(s) will this move?
- Direction and rough magnitude (if known)
4. Validate the Link
- Is the connection explicit and defensible?
- Could someone challenge it? How would you respond?
- Are there stronger or weaker links to call out?
5. Document the Mapping
Strategy Mapping
| Work Item | Strategic Pillar | OKR/Goal | Segment | Metric Impact |
| [Feature/Experiment] | [Pillar] | [OKR] | [Segment] | [Metric + direction] |
Narrative
- 2–3 sentences: how this work advances strategy
Output
A Strategy Mapping that:
- Explicitly connects the work item to strategy
- Identifies the OKR or goal it supports
- Clarifies segment and metric impact
- Provides a defensible narrative for prioritization and planning
Reference: knowledge/products/<product>/strategy.md and knowledge/_template/strategy.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.