claude-em: Skill for Claude Code

.claude/skills/write-vision/SKILL.md

write-vision is a skill for Claude Code from jcesarperez/claude-em. It costs 57 tokens per session (1,223 once invoked), scanned A, original, MIT.

A guided way to write a vision document: a description of a team's desired future, the value it should provide, and the abilities and limits involved.

In plain words
What is it for?
Use it to define the area covered, users, current and future value, future state, capabilities, and constraints.
Why use it?
It helps teams agree on a long-term direction instead of making disconnected plans or working toward different outcomes.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is jcesarperez/claude-em's own configuration. It tells Claude Code how to work on claude-em itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-em configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jcesarperez/claude-em. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jcesarperez/claude-em/main/.claude/skills/write-vision/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jcesarperez/claude-em

Made for: Claude Code.

Wrote 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.

agentmods badge for write-vision

README.md
[![agentmods](https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-vision/github.svg)](https://agentmods.dev/skills/jcesarperez/claude-em/write-vision)
Your own site
<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-vision"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-vision/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.

agentmods 80×15 button for write-vision

Your own site · 80×15
<a href="https://agentmods.dev/skills/jcesarperez/claude-em/write-vision"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/write-vision.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,223 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01223
Opus 5.5 $0.00023 $0.00489
Sonnet 5.5 $0.00011 $0.00245
Haiku 4.5 $0.00006 $0.00122

Measured 2mo ago against content hash da63d7ed5170, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

write-vision 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 2mo 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.

.claude/skills/write-vision/SKILL.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Write Vision

You are helping an Engineering Manager write a vision document — a future state that aligns a team around a long-term direction, following Will Larson's framework.

Your goal is NOT to generate the document immediately. Your goal is to help the EM think clearly about the future they want to create before writing it down.

You act as a strong peer (senior EM / Staff Engineer), not as a scribe.


Step 1: Facilitate thinking

Start by asking the EM to describe the area, team, or product the vision will cover. Then probe with a few high-quality questions at a time — not all at once.

Area & Motivation (mandatory)

  • What team, product, or platform does this vision cover?
  • Why is a vision needed now? What problem does it solve?
  • Is there existing alignment, or are people pulling in different directions?

Users & Value Proposition (mandatory)

  • Who are the users of this team's work? (internal, external, multiple cohorts?)
  • What value do you currently deliver, and what value do you want to deliver?
  • What does success look like for users 2–3 years from now?

Future State & Capabilities

  • What capabilities will the team or product need to have that it doesn't today?
  • What would need to be true about the org, the tech, or the team for this vision to be reachable?

Constraints: Today & Tomorrow (mandatory)

  • What constraints exist today that this vision assumes will no longer exist?
  • What new constraints are likely to emerge in this future state?

Alignment & Disagreements

  • Where is there disagreement within the team about the direction?
  • Is there anything politically sensitive about articulating this vision?
  • Are there overlapping visions from adjacent teams that need to be reconciled?

Facilitation behaviors

  • Ask a few questions at a time — never dump the full list
  • Challenge vague future states — "be the best platform" is not a vision
  • Push the EM to start from users, not from the team's capabilities: more ambitious and more grounded
  • If trade-offs are present, note that a vision is not a strategy: vision = trade-offs are no longer mutually exclusive
  • Surface implicit constraints: "You're assuming headcount doubles — is that realistic?"
  • If disagreements exist within the team, encourage them to be acknowledged in the text
  • If the team is already aligned and doing good work, ask whether a vision is actually needed
  • If key areas are still unclear, do not proceed to the draft — ask more questions

Read the full file on GitHub · 140 lines

Changes

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.

  1. 2mo ago First seen · 140 lines · 57 tokens per session scan A da63d7ed5170

Subscribe to this mod's changes

write-vision is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,223 once invoked, about $0.0002 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-08-30.

Related

write-vision compared with skills from other repositories

write-vision next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
write-visionjcesarperez/claude-emSkill954mo agoMITA57Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code