strategic-clarity
Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define "what we own" vs "what we don't". Triggers include "strategic clarity", "team identity", "new role", "inherited ambiguity", "what does my team own", or "define our boundaries".
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill strategic-clarity --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Strategic Clarity Workflow ## Overview A 4-phase workflow for establishing team identity and strategic positioning. ``` +---------+ +---------+ +-----------+ +---------+ | ABSORB | -> | AUDIT | -> | ARTICULATE| -> | ALIGN | | | | | | | | | | Context | | Reality | | Identity | | Buy-in | +---------+ +---------+ +-----------+ +---------+ ``` **When to use:** Starting a new role, inherited ambiguity, team lacks clear identity **Output:** Team charter, value proposition, capability audit ### Advanced Patterns 1. **The inherited narrative trap** — When you inherit a team, everyone will tell you what the team does. Their descriptions will conflict. Don't average them — map the contradictions. Where people disagree about team scope is exactly where boundaries are unclear and where future conflicts will emerge. The contradictions are the diagnosis 2. **Capability vs. responsibility** — Teams often confuse what they *can* do with what they *should* do. A messaging team that *can* build email doesn't mean email is their responsibility. During the audit phase, separate capabilities (what the code does) from responsibilities (what stakeholders expect). Mismatches between these create the big
- Overview
- Advanced Patterns
- How This Skill Works
- Phase 1: ABSORB (Week 1)
- Goal
- Activities
- AI Assistance
- Phase 1 Checklist
- Phase 2: AUDIT (Week 2)
- Phase 2 Checklist
- Output: Capability Audit Template
- Phase 3: ARTICULATE (Week 3)
- Phase 3 Checklist
- Output: Team Charter Template
What does the strategic-clarity skill do?
Guided workflow for establishing team identity, boundaries, and strategic clarity. Use when starting a new role, inheriting ambiguity, when a team lacks clear identity, or when you need to define "what we own" vs "what we don't". Triggers include "strategic clarity", "team identity", "new role", "inherited ambiguity", "what does my team own", or "define our boundaries".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill strategic-clarity --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.