CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

omc-plan

Strategic planning with optional interview workflow

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers highly actionable, well-sequenced workflow guidance with strong validation checkpoints and feedback loops, but it is a monolithic, heavily redundant document. Consolidating repeated rules and moving the consensus-mode protocol, state lifecycle, and examples into reference files would cut its size substantially without losing clarity.

Suggestions

State each rule once in its canonical location and cross-reference it (e.g., define the ralplan state lifecycle only in Steps and point to it from Tool_Usage, Escalation, and Final_Checklist) to remove the fourfold repetition.

Move the detailed consensus-mode protocol (RALPLAN-DR summary spec, provider overrides, state lifecycle) and the Examples section into references/ files, keeping SKILL.md as a mode-selection overview.

Show the exact invocation syntax for state_write/state_clear (CLI command or tool call) so the state-management guidance is copy-paste executable like the Task and Skill calls.

DimensionReasoningScore

Conciseness

The ~290-line body repeats the same rules many times: the ralplan state lifecycle appears in Execution_Policy, Steps, Tool_Usage, Escalation, and Final_Checklist; the parallel-vs-sequential Architect/Critic rule is stated four times; the planning/execution boundary twice. This is 'noticeably verbose; several unnecessary… padded sections', not 3, where redundancy would be incidental rather than systematic.

2 / 5

Actionability

Concrete executable guidance throughout — exact Task(subagent_type=...) calls, Skill(...) invocations with plan paths, AskUserQuestion option sets, example dialogue transcripts, and file locations. It falls short of 5 because state_write/state_clear are referenced with pseudo-call signatures but never shown as an actual runnable command or tool invocation.

4 / 5

Workflow Clarity

Each mode has an explicitly numbered sequence, the consensus loop has a bounded re-review feedback loop (max 5 iterations with rejection handling), and validation is explicit (Final_Checklist, Review Quality Criteria table, Escalation_And_Stop_Conditions) — matching 'Clear sequence with explicit validation steps; feedback loops for error recovery; checklists for complex processes'.

5 / 5

Progressive Disclosure

There are no bundle files at all (no references/, scripts/, assets/), and the entire ~290-line protocol — consensus-mode state lifecycle, RALPLAN-DR spec, examples, advanced tables — is inlined in SKILL.md. Section structure is clear, but content that clearly belongs in separate reference files is inline, matching anchor 3 rather than 2 (which requires no section structure).

3 / 5

Total

14

/

20

Passed

Description

28%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a short generic label: it names the planning domain and one feature but says nothing concrete about what the skill produces (work plans, consensus review, ADRs) or when to use it. It would rarely trigger correctly on natural user phrasing and risks confusion with other planning skills.

Suggestions

State the concrete outputs and actions, e.g. 'Creates comprehensive work plans through adaptive interviewing, direct planning, multi-perspective consensus review (Planner/Architect/Critic), and evaluation of existing plans.'

Add an explicit 'Use when' clause with natural trigger phrases such as 'plan this', 'requirements gathering', 'review this plan', 'consensus', or 'ralplan'.

Include distinctive keywords (RALPLAN-DR, ADR, Planner/Architect/Critic loop) so the description is distinguishable from generic strategic-planning or task-management skills.

DimensionReasoningScore

Specificity

"Strategic planning" names the domain but lists no concrete actions — creating work plans, consensus (Planner/Architect/Critic) review, or plan evaluation are never mentioned, matching the anchor 'Names the domain but actions are minimal or generic' rather than score 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The 'what' is vague (no mention of producing work plans or plan review) and there is no 'when'/'Use when' clause at all, matching anchor 2 'Has a vague what and no when'; it cannot reach 3 without a clear statement of what the skill does.

2 / 5

Trigger Term Quality

Only generic keywords ('strategic planning', 'interview') appear; the natural phrases users would actually say — 'plan this', 'requirements gathering', 'review this plan', 'consensus', 'ralplan' — are absent, fitting 'One or two generic keywords; missing the natural phrases users say' rather than 3, which requires relevant domain keywords.

2 / 5

Distinctiveness Conflict Risk

'optional interview workflow' adds some distinctiveness, but 'Strategic planning' is broad enough to overlap with many other planning or task-management skills, fitting 'Somewhat specific but could still overlap with similar skills'; not 4 because no concrete trigger phrase separates it from generic planning skills.

3 / 5

Total

9

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/plan/SKILL.md

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.