- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-big-picture -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-big-picture -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-big-picture -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add kharmanskyi/open-steps --skill os-big-picture -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/kharmanskyi/open-steps/tree/HEAD/skills/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.
BIG-PICTURE.md in the project root, and it may already be somebody's own
work. Everything this skill writes lives between and; no markers → append at the end; no file → create
it, and add it to this clone's ignore list, never to .gitignore:
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.
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.
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.
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.
An offer, never a quiet action, and only for the "What is next" rows.
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.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.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.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.
_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._
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.
Last worked on and Signal are
script output every time. Stage has no measurement.stable, which is what stops the map recommending you delete a
working product.Why the rules are there, the traps the script cannot catch, and a worked
example: references/.
>-
---name: os-big-picturedescription: >----# skills/os-big-picture/SKILL.md常見問題
從發布者下載 skills/os-big-picture/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/kharmanskyi/open-steps。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。