CtrlK
BlogDocsLog inGet started
Tessl Logo

crocoder-dev/sce-plan-authoring

Author structured Shared Context Engineering implementation plans.

100

Quality

100%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

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 a strong skill description that excels across all dimensions. It clearly specifies concrete actions (creating structured plans with atomic tasks), provides excellent trigger term coverage with natural language users would actually say, includes an explicit 'Use when' clause with multiple scenarios, and carves out a distinct niche that won't conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Creates or updates structured SCE implementation plans', 'Breaks a change request into scoped, atomic tasks', and specifies outputs include 'clear goals, boundaries, acceptance criteria, and verification steps'. Also specifies the exact output location.

3 / 3

Completeness

Clearly answers both what (creates/updates implementation plans with atomic tasks, goals, criteria) AND when with explicit 'Use when' clause covering three distinct trigger scenarios: planning features/refactors, needing task breakdowns, or describing changes requiring structured planning.

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'plan a new feature', 'refactor', 'integration', 'project plan', 'task breakdown', 'implementation roadmap', 'work plan', 'structured planning'. Good coverage of variations users might naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with specific niche: SCE implementation plans in a specific directory path, atomic task breakdown with acceptance criteria. The combination of structured planning output format and specific use cases makes it unlikely to conflict with generic coding or documentation 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 an excellent skill that demonstrates strong planning methodology with clear gates, concrete examples, and actionable output contracts. The atomic task slicing contract is particularly well-defined with both compliant skeleton and filled-in examples. The workflow is explicit about blocking conditions and validation requirements.

DimensionReasoningScore

Conciseness

The skill is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose and the content assumes Claude's competence in understanding planning concepts.

3 / 3

Actionability

Provides highly concrete guidance with specific task format requirements, example clarification questions, a filled-in task example, exact file paths, and a canonical next command. The checkbox syntax and verification commands are copy-paste ready.

3 / 3

Workflow Clarity

Clear multi-step workflow with explicit gates: intake trigger → clarification gate (blocking) → plan format → task slicing → output contract. The clarification gate explicitly blocks progress until resolved, and the final task mandates validation.

3 / 3

Progressive Disclosure

Well-structured with clear sections and appropriate reference to external file (`context/plans/PLAN_EXAMPLE.md`) for the full annotated example. The skill itself stays focused on the overview while pointing to detailed reference material.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents