omc-plan
Strategic planning with optional interview workflow
35
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/plan/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is far too vague to be useful for skill selection. It fails to specify concrete actions, lacks natural trigger terms, provides no 'when to use' guidance, and is generic enough to conflict with many other skills. It reads more like a category label than a functional skill description.
Suggestions
List specific concrete actions the skill performs, e.g., 'Creates strategic plans, conducts stakeholder interviews, generates SWOT analyses, and produces roadmap documents.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks for strategic planning, business strategy, roadmaps, stakeholder interviews, or organizational planning.'
Clarify what 'optional interview workflow' means concretely — describe the steps or outputs so Claude can distinguish this skill from general planning or project management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is extremely vague. 'Strategic planning' is abstract and does not list any concrete actions. 'Optional interview workflow' hints at a capability but doesn't describe what it actually does. | 1 / 3 |
Completeness | The description barely addresses 'what' (strategic planning with interviews) and completely omits 'when' — there is no 'Use when...' clause or any explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The terms 'strategic planning' and 'interview workflow' are generic and unlikely to match natural user queries. There are no specific trigger terms like file types, concrete tasks, or common user phrases. | 1 / 3 |
Distinctiveness Conflict Risk | 'Strategic planning' is extremely broad and could overlap with project management, business analysis, roadmap creation, or many other skills. There is nothing to distinguish this skill's niche. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured workflow skill with excellent sequential clarity, validation checkpoints, and concrete guidance for complex multi-mode planning operations. Its primary weakness is extreme verbosity — critical rules about state management, execution boundaries, and interactive/non-interactive branching are repeated 3-4 times across sections, significantly inflating token cost. The monolithic structure would benefit from splitting reference material into separate files.
Suggestions
Deduplicate repeated instructions: state lifecycle rules, the planning/execution boundary, and interactive vs non-interactive branching logic each appear 3-4 times — consolidate each into a single authoritative location and reference it elsewhere.
Extract the Advanced section (question classification table, review quality criteria, option presentation format) into separate bundle files and reference them from the main SKILL.md to reduce inline token cost.
Remove explanatory 'Why this exists' and 'Why good/bad' commentary — Claude doesn't need rationale for following instructions; the examples alone are sufficient.
Tighten the Tool_Usage section by removing items that duplicate Steps content verbatim (e.g., the consensus mode sequential constraint and state lifecycle rules are already fully specified in Steps).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines with significant repetition. The state lifecycle rules are explained in Steps, Tool_Usage, Escalation_And_Stop_Conditions, and Final_Checklist with near-identical wording. The consensus mode steps repeat interactive vs non-interactive branching multiple times. Many instructions (e.g., 'Do NOT implement directly', state management caveats) are restated 3-4 times across sections. | 1 / 3 |
Actionability | The skill provides highly specific, concrete guidance: exact CLI flags, specific subagent invocation syntax (Task(subagent_type=...)), precise quality thresholds (80%+ citations, 90%+ testable criteria), structured decision tables, explicit state management calls (state_write, state_clear with parameters), and detailed step-by-step sequences. The examples show concrete interaction patterns. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced with numbered steps, explicit validation checkpoints (Critic approval gates, max iteration limits), feedback loops (re-review loop with max 5 iterations), and clear error recovery paths. The consensus mode workflow has explicit sequential ordering constraints and state lifecycle management. Destructive operation guards are well-defined (planning/execution boundary). | 3 / 3 |
Progressive Disclosure | The content has reasonable section structure (Purpose, Steps, Tool_Usage, Examples, Advanced) but is monolithic — all content is inline in a single file with no references to supporting documents. The Advanced section contains material (question classification, review criteria, option presentation format) that could be split into separate reference files. No bundle files are provided to offload detail. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Yeachan-Heo/oh-my-claudecode
- Commit
679b418
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.