Strategy Connector
Help PMs map any work item (feature, experiment, initiative) to strategic goals and OKRs. Use before PRDs, backlog prioritization, or planning.
Install
$ agentstack add skill-hardiktiwari-pm-operating-os-strategy-connector ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hardiktiwari-pm-operating-os-strategy-connector) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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/_template/strategy.md(or your org's strategy doc) - 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/_template/strategy.md for strategic context structure.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.