القائمة
Surface assumptions collaboratively before proceeding — beginner's mind, invoked depth
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review all pending changes against repo conventions before committing
Mark files as human-reviewed with specific validation types
Harvest and locally merge changes from a paude container session. Use when pulling agent work from paude, running paude harvest, merging session commits, importing submodule changes from a container, or fixing failed harvest/submodule fetch.
Start a paude container session for fire-and-forget agent work. Use when creating a paude session, delegating a task to paude, running work in an isolated container, setting up a paude worktree, or launching pi/claude/gemini in podman.
Write a task spec file for a paude container agent. Use when delegating work to paude, preparing a paude prompt-file, writing fire-and-forget agent tasks, or scoping submodule work for harvest.
Diagnose a running or stalled paude container session. Use when paude seems stuck, harvest returned empty, checking paude status, debugging 403 proxy blocks, or deciding wait vs harvest vs reset.
| name | shoshin |
| description | Surface assumptions collaboratively before proceeding — beginner's mind, invoked depth |
| argument-hint | [file path | topic | inline content from conversation] |
| allowed-tools | Read Grep Glob Shell SemanticSearch |
Read and follow submodules/zanshin-pi-extension/skills/shoshin/SKILL.md in full. That file is authoritative for the invoked workflow (collaborative assumption-surfacing, questions before building).
When gathering ground truth (Step 2 of the core process), check these in order of authority:
| Priority | Artifact | Role |
|---|---|---|
| 1 | ABOUT.md | Owner identity and priorities — precedes corpus inference |
| 2 | .planning/<project>/BRIEF.md | Authoritative scope (project = most recently modified BRIEF) |
| 3 | BACKLOG.md | Current work state (> State: line) |
| 4 | .planning/<project>/whats-next.md | Session handoff — verify against brief, don't inherit blindly |
| 5 | STYLE.md / .planning/<project>/STYLE.md | Writing conventions when content is involved |
| 6 | Recent git log | When handoff may be stale or work evolved since last session |
If brief and handoff conflict, surface the conflict and ask which framing to use.
When the target is a plan, epic, brief, or design doc, also ask:
Is this asking the right question — or a well-written answer to the wrong one?
Audience and purpose (TAGRI): Who reads this? What decision does it enable? If unclear, ask before expanding.
Signals that warrant frame-check (from ambient AGENTS.md):
Name the ceiling honestly: shoshin verifies framing against documents; if the document embeds the wrong frame, user pushback or explicit reframing is the exit.
Apply shoshin before spar when the problem may be mis-stated. Apply spar after shoshin when framing holds but the solution needs challenge.
