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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is an operationally dense, highly actionable orchestration contract with excellent progressive disclosure into the references/ and scripts/ bundle. Its main weakness is redundancy: the approval/no-implementation pledge and several delegation mechanics are repeated across sections, and some routing detail duplicates what full-workflow.md already owns.

Suggestions

State the no-implementation/approval pledge once in the opening announcement contract and reference it elsewhere ('per the opening pledge') instead of restating it in the intro, universal invariants, approval gate, and stop rules — this would remove roughly 10 lines of repetition.

Move the detailed convergence contract for review modifiers ('convergence-bounded rounds... evidence-backed blocker eligibility, and approval-with-notes counting as approval') into references/full-workflow.md, keeping only the routing-relevant fact (modifier sets review_required: true) in the body, since the body already defers full review mechanics to that file.

Trim the delegation section's prose spawn/wait/fallback discipline to the syntax snippets and the pointer to full-workflow.md ('Full spawn/wait/fallback discipline is in references/full-workflow.md'), cutting the duplicated wait/timeout/fallback paragraphs the reference already owns.

DimensionReasoningScore

Conciseness

The core no-implementation/approval pledge is restated roughly seven times ("You never start implementation", the announcement contract and its example, "Approval is not execution", "Approval authorizes plan creation only", "Never begin execution yourself"), and the INTENT ROUTING review-modifier paragraph restates convergence mechanics that belong in references/full-workflow.md. The content is otherwise operational with no known-concept padding, so this sits at 'mostly efficient but could be tightened' rather than 2, but the repetition exceeds the 'minor' threshold of 4.

3 / 5

Actionability

Fully executable guidance throughout: the copy-paste scaffold command ("node \"<skill-root>/scripts/scaffold-plan.mjs\" <slug> [--clear|--unclear] --draft-only [--review-required]"), exact spawn JSON with concrete v1-to-v2 rewrite rules ("add \"task_name\":... replace \"fork_context\":false with \"fork_turns\":\"none\""), the exact task-row grammar ("- [ ] N. <title>", "- [ ] F<number>. <title>"), and worked routing examples ("add a 5/min-per-IP rate-limit to /login = CLEAR"). This matches 'copy-paste ready; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The announcement contract gives an explicit ordered preview ("(1) parallel read-only exploration... (6) the plan is written after your okay"), and there are real validation checkpoints: the structural self-check with a repair loop ("repair the plan before handoff if any check fails"), the approval gate, and terminal stop rules. It falls short of 5 because the phase-by-phase sequence and final verification wave checkpoints are delegated to references/full-workflow.md rather than stated in the body, leaving some checkpoints implicit here.

4 / 5

Progressive Disclosure

Each bundle file is signaled at its exact decision point ("Read references/intent-clear.md" for the CLEAR route, "Both intent paths ALSO read references/full-workflow.md for the shared mechanics - the plan template, the final verification wave, the APPEND protocol"), and every referenced path (full-workflow.md, intent-clear.md, intent-unclear.md, scripts/scaffold-plan.mjs) exists in the bundle. References are one level deep with the body as a genuine overview, matching the top anchor.

5 / 5

Total

17

/

20

Passed

Description

95%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 strong description: it states the full planning pipeline concretely, gives comprehensive natural trigger phrases, and answers both what and when explicitly. Its only weakness is that a large share of the text is activation/negative-scoping rules rather than capability description, which slightly dilutes specificity.

DimensionReasoningScore

Specificity

Lists several concrete workflow actions — "grounds in the codebase", "asks only the forks exploration cannot resolve", "waits for explicit approval, then writes ONE decision-complete work plan" — but roughly half the text is activation gating rather than capability description, and the actions stay at workflow level without naming concrete outputs. Fits 'several specific actions; minor gaps' rather than 5 (not comprehensive capability coverage) or 3 (multiple distinct concrete actions are present).

4 / 5

Completeness

Explicitly answers both questions: what ("Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve... waits for explicit approval, then writes ONE decision-complete work plan") and when ("ACTIVATES ONLY on an explicit user request for the ulw-plan workflow" plus the concrete trigger list). This matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'.

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" covers natural user phrasing comprehensively, including synonyms ("make a plan"/"break this down"), a slash-command form, and "interview me" for the override path. Nothing common is missing, so it matches the top anchor rather than 4.

5 / 5

Distinctiveness Conflict Risk

The unique 'ulw-plan' trigger names plus explicit negative scoping ("NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request") give it a clear niche with minimal risk of firing for the wrong skill. Third-person voice is used throughout, so no voice penalty applies.

5 / 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/lazycodex

Path

plugins/omo/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.