CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ulw-plan

ACTIVATES ONLY on an explicit user request for the ulw-plan workflow: the user themselves saying ulw-plan, ulw plan, /skill:ulw-plan, or asking in their own words for a work plan before coding. NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request, and the plan-gated reviewers (metis/momus) stay locked without a user request plus a written .omo/plans plan file. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode.

Quality

91%

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

The canonical home for this skill is ulw-plan in code-yeongyu/lazycodex

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

An impressively actionable and well-structured skill body with copy-paste commands, exact grammars, explicit validation loops, and a clean one-level-deep reference bundle. The main cost is token efficiency: deliberate redundancy of the core pledge and inlined contracts from full-workflow.md make it longer than the guidance requires.

Suggestions

State the no-implementation/approval-authorizes-plan-only pledge once in the opening contract and reference it elsewhere with a short tag (e.g. 'per the no-implementation pledge'); it is currently repeated in six places across the body.

Replace the 100+ word review-modifier sentence in INTENT ROUTING with two or three shorter sentences and defer the convergence-contract details (bounded rounds, blocker eligibility, approval-with-notes) to full-workflow.md, which already documents them.

Consolidate the repeated pointers to references/full-workflow.md into a single 'shared mechanics' note in the routing section, keeping only the per-path load instruction.

DimensionReasoningScore

Conciseness

The body is dense and free of concept over-explanation, but it is noticeably repetitive: the no-implementation/approval-authorizes-plan-only pledge is restated roughly six times (persona intro, sticky plan mode, opening contract, example announcement, "Approval is not execution" invariant, approval gate, stop rules), pointers to references/full-workflow.md appear four times, and the review-modifier paragraph is a single 100+ word sentence packing an entire convergence contract that already lives in the reference file. It is not a 2 because nothing is padded with knowledge Claude already has, and not a 4 because the redundancy goes beyond minor trimmable instances.

3 / 5

Actionability

Guidance is fully executable: a copy-paste scaffold command with all flags ("node \"<skill-root>/scripts/scaffold-plan.mjs\" <slug> [--clear|--unclear] --draft-only [--review-required]"), a literal spawn JSON payload plus an explicit v1-to-v2 rewrite rule, exact task-row grammar ("- [ ] N. <title>" / "- [ ] F<number>. <title>"), and the exact mandatory first line. Not a 4 because the commands and grammars are copy-paste ready and cover the common cases.

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (the opening contract's numbered 1-6 preview, intent routing with an on-the-fence tie-break, then scaffold, gate, review, stop) and validation is explicit with a feedback loop: "Before handoff, run a structural self-check over the plan: verify that every implementation row and final-verifier row is column-zero... and repair the plan before handoff if any check fails", plus agent fallback rules ("Fallback only when the child is completed without the deliverable... or no longer running") and explicit terminal stop rules. Not a 4 because checkpoints are explicit and checklisted rather than merely present.

5 / 5

Progressive Disclosure

The 111-line body is an overview that defers deep mechanics to a verified bundle: three reference files (full-workflow.md, intent-clear.md, intent-unclear.md) each signaled with explicit load conditions ("Read **`references/intent-clear.md`**" on the CLEAR route, "Read the phase you are in" for shared mechanics), and two real scripts referenced by exact invocation path. References are one level deep — the reference files point only to each other and back to SKILL.md, with no nested chains. Not a 4 because the split and navigation are clean with no organization gaps.

5 / 5

Total

18

/

20

Passed

Description

96%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.

A highly specific, trigger-rich description that explicitly separates activation from non-activation and answers both 'what' and 'when' with concrete phrases. The only weakness is that a few generic trigger terms create minor overlap risk with other planning skills and with the built-in plan-mode feature.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions covering the full workflow — "grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan" — which is comprehensive coverage of the skill's capability space, matching the anchor for multiple specific concrete actions rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both questions: what ("Explore-first planning consultant (Prometheus) that grounds in the codebase... writes ONE decision-complete work plan") and when ("ACTIVATES ONLY on an explicit user request for the ulw-plan workflow" plus the explicit Triggers list with concrete phrases). The 'when' clause is present and concrete with trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

"Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode" gives comprehensive coverage of natural user phrasings including skill-name variants, and users would naturally say each of these when they need this skill. It is not a 4 because no common synonym family for requesting a plan is missing.

5 / 5

Distinctiveness Conflict Risk

The explicit gating ("ACTIVATES ONLY on an explicit user request... NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request") strongly bounds false activation, giving a mostly distinct niche. It is not a 5 because several listed triggers ("make a plan", "plan this", and especially "plan mode", which collides with Claude Code's built-in plan mode) are generic enough to overlap with other planning-related skills.

4 / 5

Total

19

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

code-yeongyu/oh-my-openagent

Path

packages/omo-codex/plugin/components/ultrawork/skills/ulw-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.