ce-strategy

Create or update STRATEGY.md. Use when starting a product, changing direction or roadmap, or when ce-ideate, ce-brainstorm, or ce-plan need upstream product grounding.

Quality

95%

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

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured instruction skill: concise, highly actionable, with a clear phased workflow and properly disclosed references. All dimensions land at the top of the scale.

Dimension	Reasoning	Score
Conciseness	Lean body that assumes Claude's competence; no padding explaining basic concepts, and the 'Learn More' pointer is purposeful and minimal. Every section earns its place.	3 / 3
Actionability	Concrete phases, named tool calls (ToolSearch, AskUserQuestion), real file paths, and explicit rules ('two rounds of pushback per section maximum'). Specific, executable guidance throughout.	3 / 3
Workflow Clarity	Phases 0-3 are clearly sequenced with explicit routing by file state, validation checkpoints (pushback rounds, present draft before writing, edit offer), and feedback for error recovery. Not a 2: checkpoints are explicit, not implicit.	3 / 3
Progressive Disclosure	SKILL.md is an overview with well-signaled, one-level-deep references (references/interview.md, references/strategy-template.md), both verified to exist. Content is appropriately split with easy navigation.	3 / 3
	Total	12 / 12 Passed

Description

90%Weight 40%Scale 1-3

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, concise description with explicit 'what' and 'when' triggers and a distinct niche. It names the artifact and concrete action but lists fewer specific sub-actions than the top specificity anchor, so specificity sits at 2 rather than 3.

Suggestions

Optionally name a couple more concrete actions (e.g., 'interview, push back on weak answers, and write STRATEGY.md') to lift specificity toward the 3-anchor.

Dimension	Reasoning	Score
Specificity	Quotes 'Create or update STRATEGY.md' name concrete actions and the domain, but only two actions are listed rather than the multiple specific sub-actions that anchor a 3. Not a 1: actions are concrete, not vague.	2 / 3
Completeness	Explicitly answers what ('Create or update STRATEGY.md') and when ('Use when starting a product, changing direction or roadmap...'). Both are clearly present with an explicit 'Use when' trigger.	3 / 3
Trigger Term Quality	Phrases like 'starting a product, changing direction or roadmap' are natural terms a user would actually say. Good coverage; not a 2 because common variations are present rather than missing.	3 / 3
Distinctiveness Conflict Risk	Clear niche as the upstream product-strategy anchor, explicitly distinguished from ce-ideate/ce-brainstorm/ce-plan. Unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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: EveryInc/compound-engineering-plugin
Path: skills/ce-strategy/SKILL.md
Commit: a9f6d53

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