ralplan

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

1.30x

Quality

—

Does it follow best practices?

Impact

99%

1.30x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with a clear, checkpointed workflow, but it carries some redundancy across its gate-example sections and keeps detail inline rather than splitting it into a reference file.

Suggestions

Consolidate the 'Good vs Bad Prompts', signal table, and end-to-end flow into a single table to cut redundancy.

Move the gate signal catalog and troubleshooting into a reference file (e.g. references/pre-execution-gate.md) and link to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and tight, but the signals table, 'Good vs Bad Prompts', end-to-end flow, and troubleshooting sections overlap in content and could be consolidated to respect the token budget.	2 / 3
Actionability	Concrete, executable guidance throughout: `/oh-my-claudecode:plan --consensus`, `Skill("oh-my-claudecode:team")`, specific flag semantics, and explicit config file paths make it copy-paste ready.	3 / 3
Workflow Clarity	Steps 0–8 are clearly sequenced with explicit checkpoints (await Architect before Critic, max-5 re-review loop, `pending approval` gate) and feedback loops for the destructive execution boundary.	3 / 3
Progressive Disclosure	Sections are well organized and there is one signaled external reference (`docs/company-context-interface.md`), but no bundle files exist and the large gate tables/troubleshooting content that could live in a reference remain inline.	2 / 3
	Total	10 / 12 Passed

Description

72%

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 distinctive and uses strong natural trigger terms, but it lacks an explicit "Use when..." clause and only names one concrete action, leaving completeness and specificity at the mid level.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a ralph/autopilot/team request is vague and needs scoping before execution.'

List a couple more concrete actions (e.g. 'drafts a PRD, runs Planner/Architect/Critic consensus, marks the plan pending approval') to lift specificity to 3.

Dimension	Reasoning	Score
Specificity	Names the domain ("Consensus planning entrypoint") and a concrete gating action ("auto-gates vague ralph/autopilot/team requests before execution"), but it does not enumerate multiple distinct concrete actions the way a score-3 anchor does.	2 / 3
Completeness	It states what the skill does, and the "when" is only implied through "vague ralph/autopilot/team requests" rather than an explicit "Use when..." clause, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	"ralph/autopilot/team" are exactly the natural trigger words users type, giving good coverage of real-world terms that would invoke this skill.	3 / 3
Distinctiveness Conflict Risk	The ralph/autopilot/team gating niche is highly specific to this ecosystem and unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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
Commit: 6c59219

Reviewed: about 7 hours 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.