crocoder-dev/opencode-sce-plan-review
Review Shared Context Engineering plans and identify the next ready task.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes natural trigger phrases users would actually say, explicitly addresses both what and when, and carves out a clear niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'identify the next unchecked task', 'surface blockers or ambiguous acceptance criteria', and 'produce an explicit readiness verdict'. Clear domain (SCE plan files in Markdown) and specific file location mentioned. | 3 / 3 |
Completeness | Clearly answers both what (reviews plan files, identifies next task, surfaces blockers, produces readiness verdict) AND when (explicit 'Use when...' clause with multiple trigger scenarios and example phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'continue the plan', 'what's next?', 'resume work on the plan', 'review my plan and prepare the next task'. These are exactly what users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific niche: SCE plan files, Markdown checklists in 'context/plans/', readiness verdicts before implementation. The trigger phrases are specific to plan continuation/review, unlikely to conflict with general task or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently communicates a clear workflow for plan continuation. It provides concrete examples of both the input format (plan markdown) and expected output (readiness summary), with explicit validation gates and decision points. The structure is logical and the content respects Claude's intelligence while providing all necessary specifics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable guidance with specific file paths, exact markdown format examples, and clear decision trees for edge cases like missing context directories or multiple plans. | 3 / 3 |
Workflow Clarity | Clear multi-step sequence with explicit validation checkpoints: resolve plan target → collect task info → identify blockers → prompt for resolution → confirm scope → produce readiness verdict. The feedback loop (block implementation until decisions aligned) is explicit. | 3 / 3 |
Progressive Disclosure | Well-organized sections with clear headers. Content is appropriately contained in a single file given its scope. Related skills are referenced at the end for navigation without deep nesting. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents