CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-workflow-spec

SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/moai-workflow-spec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is dense and largely actionable, with strong concrete commands, schemas, and a verification checklist, but the GEARS/EARS migration narrative is told redundantly and internal inconsistencies (EARS vs GEARS stage naming, 4-step vs 6-step clarification) undermine coherence. Bundle navigation is the weakest area: a third of the reference files are orphaned and one cited file is missing.

Suggestions

Collapse the GEARS-vs-EARS migration narrative (currently repeated in the Quick Reference, the pattern tables/callout, and the Implementation Guide) into a single canonical section, keeping the legacy EARS table as the one backward-compatibility reference.

Link examples.md and reference.md from the body (e.g., under a Resources or Examples heading) or remove them from the bundle, and fix the dangling `worktree-integration.md` citation in the Verification section.

Reconcile internal inconsistencies: rename workflow stage 3 from "EARS Pattern Application" to GEARS to match the canonical-notation claim, and align the "Four-step" vs 5-step/6-step (0, 0.5, 1-4) requirement clarification counts.

DimensionReasoningScore

Conciseness

Much of the body is token-efficient tables, commands, and checklists, but the GEARS-vs-EARS migration story is retold at least three times (Quick Reference bullets, the pattern tables and IF/THEN callout, then again in the Implementation Guide's GEARS/EARS Format sections), the worktree section pads with a "Benefits" list Claude could infer, and version stamps conflict (frontmatter 1.2.0 vs body "Version: 1.3.1"). Mostly efficient with sections that clearly could be tightened — anchor 3, not 2, since the bulk is dense operational content rather than explanation of known concepts.

3 / 5

Actionability

Provides copy-paste commands (`/moai plan "user authentication system"`), exact paths (`.moai/specs/SPEC-{ID}/spec.md`), concrete enums and formats (12 metadata fields, 8-value status enum, `[NEEDS CLARIFICATION: <topic>]` marker syntax), and a routing table. Falls short of anchor 5 because linchpin details are delegated to files outside the bundle (`.claude/rules/moai/workflow/spec-workflow.md` tier table, `spec-frontmatter-schema.md` full schema) and one cited file (`worktree-integration.md`) does not exist in the bundle.

4 / 5

Workflow Clarity

The six-stage SPEC workflow table, numbered clarification steps, NEEDS CLARIFICATION processing pipeline with an explicit human gate, and a verification checklist give a clear sequence with validation checkpoints. Minor coherence gaps keep it from anchor 5: stage 3 still reads "EARS Pattern Application" against the GEARS-canonical claim, and the clarification process is labeled "Four-step" in one place while listing six steps (0, 0.5, 1-4) in another.

4 / 5

Progressive Disclosure

Four reference files (ears-deep-dive, requirement-clarification, worktree-workflow, migration-guide) are well-signaled with link syntax and context, but scored against the actual bundle: two of six files (examples.md, 31KB; reference.md, 21KB) are never referenced from the body and are undiscoverable, the Verification section cites a non-existent `worktree-integration.md`, and worktree-workflow.md links out of the bundle to `../../moai-workflow-worktree/SKILL.md`. That is more than the minor organization gaps of anchor 4.

3 / 5

Total

14

/

20

Passed

Description

83%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: third-person, concise, domain-specific, and answering both what and when with concrete trigger phrases. Trigger coverage is good but omits synonyms (user stories, requirements gathering, feature planning) the skill body says it handles.

DimensionReasoningScore

Specificity

Names several concrete deliverables — "EARS format requirements, acceptance criteria, and Plan-Run-Sync integration" plus the actions "creating SPEC documents" and "defining acceptance criteria" — though "workflow orchestration" is abstract and coverage omits clarification and planning. Fits anchor 4 (several specific items, minor gaps) better than 3, which expects only 1-2 concrete actions.

4 / 5

Completeness

Explicitly answers both: what ("SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development") and when ("Use when creating SPEC documents or defining acceptance criteria") with two concrete trigger phrases. The when-clause is already explicit and specific, so the anchor-4 condition ("when could be more explicit") does not apply.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "SPEC documents", "acceptance criteria", "requirements" — in an explicit Use-when clause. Missing common variations like "user stories", "feature planning", or "requirements gathering" that the skill actually covers, so not anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — SPEC/requirements authoring for MoAI-ADK — with distinct triggers, but it overlaps with closely related sibling skills (moai-workflow-testing, moai-workflow-worktree) and generic terms like "acceptance criteria" could plausibly fire for testing workflows. Mostly distinct with minor overlap risk: anchor 4.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-workflow-spec/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.