omc-plan

Strategic planning with optional interview workflow

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/plan/SKILL.md

Quality

Content

70%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 content is a thorough, actionable, and well-sequenced planning workflow with strong validation gates and feedback loops. Its main weaknesses are notable cross-section repetition of the same guardrails and a monolithic structure with no progressive disclosure into bundle files.

Suggestions

Consolidate the repeated state-lifecycle and Architect/Critic-independence rules into a single authoritative section and reference it elsewhere to reduce token cost.

Move the detailed RALPLAN-DR deliberation rules and ADR/pre-mortem templates into a reference file (e.g. references/ralplan-dr.md) and link to it from the body.

Extract the Advanced section's option-presentation and question-classification tables into a references file, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but key rules (state lifecycle handling, 'do not pass Architect output to Critic', execution-approval boundaries) are restated across Execution_Policy, Steps, Tool_Usage, and Final_Checklist, adding noticeable repetition that could be tightened.	3 / 5
Actionability	Guidance is highly concrete with exact Task(subagent_type=...), Skill(...), state_write(...)/state_clear(...) signatures and flag usage, matching 'mostly executable guidance with minor gaps'; a few procedural statements remain abstract.	4 / 5
Workflow Clarity	Each mode has an explicitly sequenced multi-step workflow with validation checkpoints, a bounded re-review feedback loop (max 5 iterations), ADR/checklist requirements, and clear escalation/stop conditions, matching the 'clear sequence with explicit validation steps and feedback loops' anchor.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and all detail is inlined in SKILL.md; internal repo paths are referenced but no skill-bundle references are signaled, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

25%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 too terse and generic: it names the planning domain without concrete actions, omits natural trigger phrases, and lacks any explicit 'use when' guidance. It underutilizes the rich trigger vocabulary that the body actually documents.

Suggestions

Add concrete actions, e.g. 'Creates actionable work plans, gathers requirements via interviews, and reviews existing plans'.

Include explicit trigger guidance, e.g. 'Use when the user wants to plan before implementing (\"plan this\"), review an existing plan, or get multi-perspective consensus on a plan'.

Surface the distinct modes (interview/direct/consensus/review) so the description is distinguishable from generic planning or execution skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Strategic planning' names the domain but lists no concrete actions (e.g. creating plans, gathering requirements, reviewing), matching the 'Names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It offers a vague 'what' ('Strategic planning with optional interview workflow') and no explicit 'when'/'Use when' clause, matching the 'vague what and no when' anchor; the missing trigger guidance also caps completeness at 3, and this is below that.	2 / 5
Trigger Term Quality	Only generic terms ('planning', 'interview') appear; the natural user phrases the body itself uses ('plan this', 'review this plan') are absent, matching 'one or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	'Strategic planning' is very broad and would overlap with many planning or coding skills, matching 'very broad; high overlap risk with many similar skills'.	2 / 5
	Total	8 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 5aa678c

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.