- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add kharmanskyi/open-steps --skill os-done-or-not -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add kharmanskyi/open-steps --skill os-done-or-not -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add kharmanskyi/open-steps --skill os-done-or-not -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add kharmanskyi/open-steps --skill os-done-or-not -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/kharmanskyi/open-steps/tree/HEAD/skills/os-done-or-not게시자 제공
One question, one screen: did the agent finish, and what actually happened, in words a reader who does not code will understand. Nothing happened (pure questions, no files touched) → one line saying so, no report.
The user's language in this session, detected from the conversation. Translate every template label. Code, files, commands stay English.
Fast checks only; never re-run the test suite - use results this session already produced. Not confirmable in seconds, or still running → "not checked", never "yes".
git status --porcelain # uncommitted?
git log --oneline -10 # what landed
git log HEAD --not --remotes --oneline 2>/dev/null | head -20 # unpushed? (no remote: say so)
gh pr view --json state,mergeStateStatus && gh pr checks # if a PR exists
Sessions end one of eight ways; pick the match before writing, or the report says "fully done: yes" and "safe to close: no" in the same breath.
Outcomes 5 and 6 are where reports start lying; "the approach failed and was rolled back" is a complete result.
<Lead: 1–2 sentences. What changed for the product. Best result first.>
| | |
|---|---|
| ✅ | <done, and what proves it> |
| ⚠️ | <surprise or bad news> |
| ⏳ | <deferred, and until when> |
**Verdict**
| | |
|---|---|
| Fully done? | Yes / No / Not checked |
| Anything needed from you?| No / <one concrete action> |
| New debt? | No / <how many, where recorded> / Not checked |
| Safe to close? | Yes / No - <reason in five words> |
Checkmark rows: two to five; drop an empty row, never a non-empty ⚠️. Verdict cells are one line each - detail lives in the checkmark rows, not the verdict.
Two conditional rows, only when the session makes them real - never "not applicable": Easy to undo? (Yes - how / Hard - why) and Security touched? only when yes - one line: exposed what, closed how. Deliberately no "live for users?" row: unmerged it repeats the action line; merged but not reaching users is a surprise - a ⚠️ row.
Write both, creating folders as needed. The paths are the same on every tool.
If the file tool refuses them as outside the workspace, use the shell. Save
nowhere else, and never in the user's project. <project> is the name of the
folder the session started in, or of its repository's top folder when it is
inside one (the name only, not the path):
~/.claude/open-steps/reports/<project>/latest.md (overwritten)~/.claude/open-steps/reports/<project>/history/<YYYY-MM-DD-HHMM>.mdHead the file with date, project, ticket. Two parts; only part one goes in the chat. Part one - the report above, for the person. Part two - for the next session, which reads it instead of re-exploring the repository; the only home for engineering identifiers.
---
## Technical detail - for the next session, not the reader above
- Branch / worktree / PR and their state; commits made this session
- Files changed, with paths; test and check results as measured
- Commands worth re-running; the first thing to look at next
Terse, factual, a handover note; nothing changed → omit part two.
The report describes one session. BIG-PICTURE.md holds the standing picture
of the product, and this is the moment it goes out of date. Use the
os-big-picture skill to update only the rows this session touched - a new
feature, a stage that moved, a deferred item joining the backlog.
Skip it in two cases only: outcome 8, or no BIG-PICTURE.md and the user has
never asked for one. A session that changed no row still runs it, because the
map's measured columns went stale while the session ran.
Examples of the move - apply it in the user's language. A ticket or PR number naming an action ("review PR #892") stays; elsewhere say what it changed.
>-
---name: os-done-or-notdescription: >----# skills/os-done-or-not/SKILL.mdFAQ
게시자에게서 skills/os-done-or-not/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/kharmanskyi/open-steps에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.