Agent skill

Os Big Picture

by kharmanskyi in kharmanskyi/open-steps

ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…

MITAuto-check passedWriting & Content

Install Os Big Picture

skills CLI
$ npx skills add kharmanskyi/open-steps --skill os-big-picture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install kharmanskyi/open-steps os-big-picture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/kharmanskyi/open-steps.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/os-big-picture .claude/skills/os-big-picture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
os-big-picture
GitHub stars
1.3k
Token cost
~1.9k tokens
SKILL.md length
878 words
Files
4 (incl. scripts, references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…

  • Works in 6 steps: find the file, and never clobber it → the census, measured by the script → reading what it printed → …
  • Asks where the project as a whole stands - where are we
  • SKILL.md covers Step 1 - find the file, and…, Step 2 - the census, measured…, Step 3 - reading what it printed and Step 4 - the backlog, sourced…, plus 4 more sections
  • Runs Shell scripts from its folder; calls git and bash

What it does

Os Big Picture is an agent skill from kharmanskyi/open-steps. ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a session report has just been written. It keeps one file, BIG-PICTURE.md: what the product is, every feature with how far it got, which parts nobody has touched, and what is queued next. Age and wiring…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/01-quiet-is-not-dead.md`, `references/rationale.md` and `scripts/census.sh`).

It sits in Writing & Content. It works with Git. The repository describes itself as: Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow. MIT. The licence is MIT.

When your agent uses it

  • Asks where the project as a whole stands - where are we
  • Whats the big picture
  • What have we built
  • What is in this project

Example prompts

  • “where are we”
  • “s the big picture”
  • “what have we built”
  • “/os-big-picture”

Requirements

  • A Bash shell
  • Pre-approved tools (allowed-tools): Read(~/.claude/open-steps/**), Edit(BIG-PICTURE.md), Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *), Bash(git rev-parse --git-dir), Bash(gh repo view *), Bash(gh issue list *), Bash(gh issue create *)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. find the file, and never clobber it
  2. the census, measured by the script
  3. reading what it printed
  4. the backlog, sourced and never invented
  5. the tracker, if there is one
  6. plain words, before it is written

What it can do on your machine

Read from SKILL.md and the folder at commit 4fa744b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read(~/.claude/open-steps/**)
    • Edit(BIG-PICTURE.md)
    • Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *)
    • Bash(git rev-parse --git-dir)
    • Bash(gh repo view *)
    • Bash(gh issue list *)
    • Bash(gh issue create *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Os Big Picture loads about 1.9k tokens when it runs, and up to ~4.5k if it reads all its reference files. Until then it costs about 191 tokens; SKILL.md has 878 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~191
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from kharmanskyi/open-steps at commit 4fa744b, republished under its MIT licence (© kharmanskyi). 878 words, ~1,902 tokens.

Download SKILL.mdSave it as .claude/skills/os-big-picture/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
os-big-picture
description
ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a session report has just been written. It keeps one file, BIG-PICTURE.md: what the product is, every feature with how far it got, which parts nobody has touched, and what is queued next. Age and wiring are measured from git; how far a feature got comes from the reports or says "not checked". Where a tracker is connected it offers to open the queue as tickets, after a yes and never before. Never invents work, never deletes code.
allowed-tools
Read(~/.claude/open-steps/**), Edit(BIG-PICTURE.md), Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *), Bash(git rev-parse --git-dir), Bash(gh repo view *), Bash(gh issue list *), Bash(gh issue create *)

os-big-picture

One file, BIG-PICTURE.md, where os-whats-next already looks for a backlog. It answers "where are we now" - not a plan, nothing in it a promise. Write it in the user's language; paths stay English.

When to use it. The user asks where the project stands, or there is no BIG-PICTURE.md yet → the full pass: describe, census, signals, backlog. A session report was just written → the fold-in: only the rows that session touched. Both re-measure, because a session that moves no row is the one after which the dates go quietly stale.

Step 1 - find the file, and never clobber it

BIG-PICTURE.md in the project root, and it may already be somebody's own work. Everything this skill writes lives between <!-- open-steps:begin --> and <!-- open-steps:end -->; no markers → append at the end; no file → create it, and add it to this clone's ignore list, never to .gitignore:

bash
f=BIG-PICTURE.md; e="$(git rev-parse --git-dir)/info/exclude"
git check-ignore -q "$f" || git ls-files --error-unmatch "$f" >/dev/null 2>&1 \
  || grep -qxF "$f" "$e" 2>/dev/null || printf '%s\n' "$f" >> "$e"

Each of the three is a reason to leave it alone. Say in one line that you did it; git add -f BIG-PICTURE.md shares it instead. Never read Last worked on or Signal back out of the file - only Stage and the queue carry forward.

Step 2 - the census, measured by the script

bash
bash ${CLAUDE_SKILL_DIR}/scripts/census.sh .

Where your tool does not set ${CLAUDE_SKILL_DIR}, run it from the project root as bash <this skill's folder>/scripts/census.sh .. If it cannot run at all, say so and mark every measured column "not checked"; never estimate them.

An AGE line, then one measured PART row per part: path, last worked on, commits in six months, whether anything outside reaches it, the signal.

Step 3 - reading what it printed

SignalWhat it meansWhat to do
activeBeing worked onNothing
stableQuiet, and something still reaches itLeave it alone - finished and in use
unused - N monthsQuiet, and nothing reaches itThe only real retire candidate

When the AGE line says young, write one line directly above the table, with the day count and date from the AGE line: "This project is N days old. Nothing here can be quiet for six months yet, so the Signal column starts to mean something on DATE." Every active is then a fact about the calendar, not the code. On an ok line, write no such note.

Step 4 - the backlog, sourced and never invented

Three sources, each item naming its own: session reports in ~/.claude/open-steps/reports/<project>/ (⏳ deferred rows, "Anything needed from you", recorded debt); Step 3 (each unused part, one retire candidate); the user, by hand. Nothing else - a gap you noticed while reading the code is not a task, so say it in the chat and let the user decide.

Step 5 - the tracker, if there is one

An offer, never a quiet action, and only for the "What is next" rows.

  1. Find it, never install it. gh repo view --json hasIssuesEnabled -q .hasIssuesEnabled, then any tracker already connected. Nothing connected is a normal answer: say so under "What is next", then Step 6.
  2. Search before you propose: gh issue list --search '<a few words>' --state all --json number,title,state. A closed ticket is still a match; where the search did not run, say so.
  3. Ask, then create. Plain lines through os-ask-simple; on a yes create those and nothing else, and only where this pass measured what the item rests on. Write each number back into its row, same pass.
Show full SKILL.md (324 more words)Show less

Step 6 - plain words, before it is written

Put every sentence in the block through the os-say-simple rules first: one sentence one idea, active voice, one word for one thing. That covers the prose, the "What it does" column and the backlog items - never a measured cell.

The shape

<!-- open-steps:begin -->
_Measured <date>. Stages are dated where they stand; anything undated in this
file is not measured._

## What this is

<Three or four sentences. What the product does, who runs it, what it runs
on. No jargon - a reader who has never seen the code.>

## What is in it

| Feature | What it does | Stage | Last worked on | Signal |
|---|---|---|---|---|
| <plain name> | <one line> | live (1 Sep) | 1 Sep | active |
| <plain name> | <one line> | not checked | 28 May | stable |

## Worth retiring

<One line each: what it is, how long unused, what would break. Empty is a
result - write "nothing found" and keep the heading.>

## What is next

- <item> - <source>
- <item> - <source> - #<ticket number, once one exists>

_Age and wiring measured <date>, fresh this pass. Stage comes from session
reports and is only as current as the date beside it._
<!-- open-steps:end -->

Stage is one of building, built - not shipped, live, retired or not checked, and it carries the date it came from, always - live (12 Jul), never bare live, and not checked never dated. When the newest date in that column is months behind the newest commit, the reports have stopped: say so.

Hard rules - these rules are the skill

  1. Measured and assumed never mix. Last worked on and Signal are script output every time. Stage has no measurement.
  2. Enumerate, never guess. The parts come from the script.
  3. Quiet is not dead. No retire candidate on age alone: quiet plus wired in is stable, which is what stops the map recommending you delete a working product.
  4. Never invent work. Every backlog item names its source.
  5. Never clobber. Only between the markers. Their file stays theirs.
  6. Recommend, never act. No deleting code, moving files, opening a pull request. "Worth retiring" is a sentence, not an action.
  7. Plain words. A feature is named as the user says it, not as the folder.
  8. One screen per section. Twelve features is a wall - group and say so.
  9. A ticket only after an explicit yes. Rule 6 is the code, this is everyone else's inbox.
  10. The plain-words pass never touches a measured cell.
  11. Re-measure, never quote. A number read out of the file is a number about the past wearing today's date.
  12. Every claim carries its date or says it has none. A map that cannot go visibly stale will go invisibly stale.

Why the rules are there, the traps the script cannot catch, and a worked example: references/.

© kharmanskyi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in skills/os-big-picture of kharmanskyi/open-steps.

  • SKILL.md
  • references/01-quiet-is-not-dead.md
  • references/rationale.md
  • scripts/census.sh

Open the folder on GitHubat commit 4fa744b

Compare with similar skills

Os Big Picture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Os Big Picture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Os Big Picture this skillkharmanskyi/open-steps1.3k—~1.9kAutomated safety check: PassMIT
Korean Commit Message Polisherepoko77-ai/im-not-ai5.9k—~504Automated safety check: PassMIT
Translate Languagepancakeswap/pancake-document124—~1.9kAutomated safety check: PassNone
Copy Auditantoinecellerier/speaker-tuning-to-easyeffects145—~2.3kAutomated safety check: PassMIT
Aboutsecurity Content Ingestionwgpsec/AboutSecurity1.8k—~1.4kAutomated safety check: PassNone
Linkedin Postholtzy/dataviz-inspiration147—~1.1kAutomated safety check: PassNone

Similar skills

  • Korean Commit Message Polisher

    epoko77-ai/im-not-ai

    Rewrites Korean commit messages that read like office jargon or translation into natural wording, leaving the type, scope and meaning untouched.

    5.9k GitHub stars~504 tokensUpdated 15 days ago
    Writing & ContentAuto-check passed
  • Translate Language

    pancakeswap/pancake-document

    Translate the PancakeSwap GitBook docs into one supported language, using the en branch as the source of truth.

    124 GitHub stars~1.9k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Copy Audit

    antoinecellerier/speaker-tuning-to-easyeffects

    Audits the user-facing terminal copy changed over a git range for factual truth rather than readability, by fanning out reviewers partitioned by evidence source and triaging what survives.

    145 GitHub stars~2.3k tokensUpdated today
    Writing & ContentAuto-check passed
  • A skill your agent uses whenever the user asks to add, absorb, migrate, port, update, merge, compare, or extract security knowledge into the AboutSecurity repository from any external resource such…

    1.8k GitHub stars~1.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Linkedin Post

    holtzy/dataviz-inspiration

    Draft a LinkedIn post announcing the latest data-viz additions to dataviz-inspiration.com, and stage the highlighted projects' images in public/linkedin/.

    147 GitHub stars~1.1k tokensUpdated 4 days ago
    Writing & ContentAuto-check passed
  • Blog Draft Workflow

    luongnv89/claude-howto

    Walks through writing a blog post from an idea and source material: research, brainstorming, outline approval, versioned drafts and optional git commits.

    42k GitHub stars~1.1k tokensUpdated today
    Writing & ContentAuto-check passed

More from kharmanskyi/open-steps

  • Os Ask Simple

    kharmanskyi/open-steps

    ALWAYS invoke this skill before asking the user any technical question or offering options, and whenever they ask to be asked in plain words - "ask simple", "ask me simply", "ask me in plain words"…

    1.3k GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed
  • Os Check Work

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can…

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed
  • Os Whats Next

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language.

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed
  • Os Done Or Not

    kharmanskyi/open-steps

    ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a…

    1.3k GitHub stars~1.8k tokensUpdated 5 days ago
    Auto-check passed
  • Os Say Simple

    kharmanskyi/open-steps

    ALWAYS invoke this skill when the user asks for simpler or shorter about something said or written - "say it simply", "what does this mean", "I don't understand your answer", "too long", "wait…

    1.3k GitHub stars~1.3k tokensUpdated 5 days ago
    Auto-check passed
  • Os Step By Step

    kharmanskyi/open-steps

    ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step"…

    1.3k GitHub stars~1.9k tokensUpdated 5 days ago
    Auto-check passed

Works with

Questions about Os Big Picture

What does Os Big Picture do?

ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what…. Os Big Picture is an agent skill from kharmanskyi/open-steps. ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a session report has just been written.

When should I use Os Big Picture?

Os Big Picture fits situations like: asks where the project as a whole stands - where are we; whats the big picture; what have we built; what is in this project.

How do I install Os Big Picture in Claude Code?

Run `npx skills add kharmanskyi/open-steps --skill os-big-picture -a claude-code`. Or copy the skill folder (skills/os-big-picture in kharmanskyi/open-steps) into .claude/skills/os-big-picture in your project. Claude Code loads it when a task matches its description.

How do I install Os Big Picture in Codex?

Run `npx skills add kharmanskyi/open-steps --skill os-big-picture -a codex`. Or copy the skill folder (skills/os-big-picture in kharmanskyi/open-steps) into .agents/skills/os-big-picture in your project. Codex loads it when a task matches its description.

Can I use Os Big Picture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add kharmanskyi/open-steps --skill os-big-picture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/os-big-picture, .gemini/skills/os-big-picture, .github/skills/os-big-picture and .opencode/skills/os-big-picture in your project.

What does Os Big Picture need to run?

Going by SKILL.md and its folder, Os Big Picture needs a shell for the scripts in its folder and the command-line tools its instructions call (git and bash). Our summary lists: A Bash shell. Its frontmatter pre-approves these tools: Read(~/.claude/open-steps/**), Edit(BIG-PICTURE.md), Bash(bash ${CLAUDE_SKILL_DIR}/scripts/census.sh *), Bash(git rev-parse --git-dir), Bash(gh repo view *), Bash(gh issue list *), Bash(gh issue create *).

Does Os Big Picture access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Os Big Picture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Os Big Picture use?

Os Big Picture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Os Big Picture use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Os Big Picture?

Skills that share tags, products or a category with Os Big Picture: Korean Commit Message Polisher (epoko77-ai/im-not-ai, 5.9k stars), Translate Language (pancakeswap/pancake-document, 124 stars), Copy Audit (antoinecellerier/speaker-tuning-to-easyeffects, 145 stars) and Aboutsecurity Content Ingestion (wgpsec/AboutSecurity, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Os Big Picture?

kharmanskyi (a GitHub user) maintains it in kharmanskyi/open-steps, which has 1,279 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 5, 2026.

Source: kharmanskyi/open-steps on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.