القائمة
Surfaces hidden assumptions before complex tasks using Johari Window methodology. Trigger: "clarify", "what am I missing", or tasks involving 3+ files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Monitors analysis-doc lifecycle in all three lanes — EMERGING→PRODUCTION promotion, PRODUCTION→RETIRING/RETIRED retirement (replacement-readiness as robust community/vendor elements mature), and follow-lane upkeep (followed canons' advance triggers + liveness, per ABSORPTION-MAP.md)
Validates new analysis documents against project quality standards. Trigger when user adds an analysis doc or says "review analysis".
Ensures SOURCES.md stays synchronized when adding new analysis documents or sources. Trigger when user adds a new analysis doc, says "update sources", "add source", or after pattern-reviewer identifies missing source entries. Enforces evidence tier classification and proper citation format.
Analyze recent git commits in a target project to surface patterns, identify improvement opportunities, and generate recommendations weighted by source authority and recency. Trigger when user says "analyze commits", "review my recent work", "what patterns do you see", or when evaluating a project for best-practice alignment.
Updates analysis documents with new version requirements and dependencies when Claude Code releases new features
Apply comprehensive quality review when user prepares content for publication (blog posts, articles, documentation, presentations). Trigger when user mentions "publish", "post", "article", "review this", "draft complete", "ready to share". Enforce evidence-based claims, intellectual honesty, professional voice, and balanced perspective.
| name | johari-clarifier |
| description | Surfaces hidden assumptions before complex tasks using Johari Window methodology. Trigger: "clarify", "what am I missing", or tasks involving 3+ files. |
| allowed-tools | Read, Grep, Glob, AskUserQuestion |
Surface assumptions before implementation to prevent "we don't know what we don't know" problems.
Skip when: Simple bug fix, single-file change, user says "just do it"
| Quadrant | Description | Action |
|---|---|---|
| Arena | Known to both | State your understanding |
| Hidden | User knows, you don't | Ask about conventions, prior decisions |
| Blind Spot | You know, user doesn't | Share security/perf considerations |
| Unknown | Neither knows | Flag for investigation |
## Clarification: [Task]
**Arena**: [Shared understanding]
**Hidden**: [What user revealed]
**Blind Spots**: [Technical considerations I shared]
**Unknowns**: [To investigate, with assumptions]
Ready to proceed? [Yes/conditions]