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

79%

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 ./plugins/omo/components/ultrawork/skills/ulw-plan/SKILL.md

Quality

Content

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

A dense, well-structured planning skill body with concrete commands, clear sequencing, and well-signaled one-level-deep references to real bundle files. The main weakness is moderate verbosity from restated invariants rather than missing substance.

Suggestions

Deduplicate the approval/execution and no-implementation pledge, which appear in the opening announcement, universal invariants, and approval gate sections — consolidate into one canonical statement and reference it.

Add an explicit validate->fix->retry loop for the plan self-check (e.g. 'run structural self-check; if any row fails grammar, repair and re-check until clean') to reach a 5 on workflow clarity.

Tighten the INTENT ROUTING section by moving the worked examples and override rationale into references/full-workflow.md, keeping only the routing decision and verdict announcement in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and instruction-rich, but several passages repeat or over-explain already-stated invariants (e.g. the approval/execution distinction is restated across the opening, invariants, and approval gate), and could be tightened without losing clarity.	3 / 5
Actionability	Provides concrete executable commands (node scaffold-plan.mjs invocation, multi_agent_v1.spawn_agent syntax) and exact grammars (- [ ] N. <title>); mostly copy-paste ready with minor gaps around the slug/skill-root substitution placeholders.	4 / 5
Workflow Clarity	Clear sequence from mandatory opening through intent routing, script run, approval gate, and stop rules, with a structural self-check validation step; a fully explicit validate-fix-retry feedback loop for the plan artifact would lift it to 5.	4 / 5
Progressive Disclosure	Body is a focused overview with well-signaled one-level-deep references to real files (references/full-workflow.md, intent-clear.md, intent-unclear.md) and scripts/scaffold-plan.mjs; good organization, with minor inline density that could be split further.	4 / 5
	Total	15 / 20 Passed

Description

91%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, specific description that clearly states both capability and activation conditions with comprehensive trigger terms. Third-person voice is maintained throughout; it is dense but every clause earns its place.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('grounds in the codebase, asks only the forks exploration cannot resolve', 'researches them to best practice', 'waits for explicit approval, then writes ONE decision-complete work plan'), with only minor gaps in coverage; not quite the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicitly answers both 'what' (Explore-first planning consultant that grounds in the codebase...) and 'when' (ACTIVATES ONLY on an explicit user request...) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive coverage of natural trigger phrases users would actually say: 'ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode'.	5 / 5
Distinctiveness Conflict Risk	Clearly a distinct niche (the ulw-plan planning workflow) with specific triggers unlikely to fire for unrelated skills; minor overlap risk with general planning intents keeps it just below 5.	4 / 5
	Total	18 / 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
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
Commit: 10f9558

Reviewed: 10 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.