CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-plan

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Quality

84%

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

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 exemplary orchestration skill body: it is a lean, phase-sequenced overview with explicit validation checkpoints, error-recovery feedback loops, verbatim prompts and tokens, and a verified, well-signaled reference structure that puts every detail one conditioned read away. Its only weakness is minor over-density — the completion-contract paragraph and a time-sensitive year line could be trimmed or reorganized for clarity.

DimensionReasoningScore

Conciseness

The body is dense rule-prose with no padding and no explanations of concepts Claude already knows, but the Mandatory Completion Contract paragraph restates per-branch done conditions in convoluted legalism that could be tightened, and the standalone time-sensitive line "The current year is 2026." sits outside any deprecated/old-patterns section, matching anchor 4 rather than the every-token-earns-its-place lean of anchor 5.

4 / 5

Actionability

It supplies concrete, executable directives — the verbatim user prompt ("Plan ready at `<absolute path to plan>`. What would you like to do next?"), the exact return token `settled-decision-invalidated`, exact blocked-state fields (`status: blocked`, `phase`, `blocker`, `recovery_path`), and exact reference paths with read-timing per phase — with only minor abstraction such as "resolve the choice at this boundary, and follow it", matching anchor 4 rather than the fully copy-paste-ready coverage of anchor 5.

4 / 5

Workflow Clarity

The phases run in a clear sequence (Phase 0 scoping/resume/output, Phases 1-4 research and compose, Phase 5 review/write/handoff) with explicit validation checkpoints (resume check, pre-write review, confidence path, mandatory non-interactive document review, the STOP directive), feedback loops for error recovery (blocked reporting with recovery path, the settled-decision-invalidated token), and a branch-by-branch completion checklist, matching anchor 5.

5 / 5

Progressive Disclosure

The 55-line body is a clear phase-anchored overview routing to 17 real reference files by exact path with explicit read-timing ("Read X before Y", the STOP directive for plan-handoff.md); every referenced path was verified to exist and every additional bundle file (rendering references, agents/, scripts) is reachable through signaled conditional routing rather than buried chains, matching anchor 5.

5 / 5

Total

18

/

20

Passed

Description

78%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 that explicitly covers both what the skill does and when to use it, with concrete trigger phrases and explicit routing guidance away from a sibling skill. Its main limitation is that the capability list collapses into essentially one action (planning) with variations, leaving it thinner on distinct concrete capabilities and natural synonyms than a top-scoring description.

Suggestions

Enumerate the distinct concrete capabilities as separate actions (e.g., 'Create implementation plans from requirements, decompose work into sequenced steps, enrich or deepen an existing plan, and produce non-software task plans') rather than variations of one planning action.

Add the natural synonyms users are likely to say as triggers — e.g., 'roadmap', 'task breakdown', 'implementation plan', 'plan of attack' — to the 'Use when...' clause.

State the boundary against ce-work (execution) alongside the existing ce-brainstorm boundary, e.g., 'use ce-work to execute a completed plan', to further reduce sibling-skill overlap.

DimensionReasoningScore

Specificity

The description names the domain ("Create structured plans for multi-step work, including software and non-software tasks") and 1-2 concrete actions (create plans, "deepen an existing plan"), but the remaining phrases ("plan from requirements", "break down implementation") are variations of that single action rather than several distinct capabilities, matching anchor 3 rather than 4.

3 / 5

Completeness

It clearly answers 'what' ("Create structured plans for multi-step work, including software and non-software tasks") and explicitly answers 'when' with concrete trigger phrases ("Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan"), exactly matching the anchor 5 pattern.

5 / 5

Trigger Term Quality

It includes natural phrases users would actually say ("asked to plan", "break down implementation", "plan from requirements", "deepen an existing plan"), but misses common variations such as "roadmap", "task breakdown", or "implementation plan", matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves a distinct planning niche and explicitly routes a neighboring use case elsewhere ("prefer ce-brainstorm for exploratory framing"), but "plan" is a very common trigger word and the sibling ce-work (execution) is not distinguished in the description, so minor overlap risk remains, matching anchor 4 rather than 5.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

EveryInc/compound-engineering-plugin

Path

skills/ce-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.