CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aet-req-design

Requirements design skill - transforms requirements analysis specifications into implementable system design specifications through architecture design, module change planning, interface design, and DFx strategy. Use when: (1) you have completed requirements analysis and need to produce a requirements design specification, (2) you need to clarify how requirements integrate into the existing system, (3) you need module-level change planning with frozen zones and interface contracts, (4) you need to produce a SDD-style design document, or any requirements design and architecture design tasks.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./jiuwenclaw/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 presents a well-sequenced, gated four-stage workflow with genuinely concrete confirmation prompts and tool calls, but its progressive disclosure is broken: every core stage depends on workflow SOP files whose paths are never given, and the existing references/ and scripts/ files are orphaned. Repetition of error-handling and precedence rules across three sections also costs conciseness.

Suggestions

Add the missing 'Skill File Index' section listing the absolute paths of workflows/sop-exploration.md, sop-design.md, sop-verification.md, sop-load-template.md, and sop-generation.md — or ship those files in the bundle — so the per-stage 'read_file' instructions are executable.

Reference the existing bundle files from the body (e.g., point the A4 review stage at references/deliverable-review.md and A2.1 verification at references/feasibility-checklist.md) so they are discoverable.

De-duplicate <condition>: the identical 'Execution precedence' line appears twice, and the abort/missing-file messaging in <guideline>, [A1.1], and <condition> should be consolidated to a single canonical wording.

DimensionReasoningScore

Conciseness

The body is operational throughout — structured prompts, tool calls, hard limits — with no explanation of concepts Claude already knows. It falls short of a 5 because of verbatim duplication (the 'Execution precedence: Mandatory prechecks → Stage sequence (A1→A2→A3→A4)' line appears twice in <condition>) and abort/error messaging repeated with divergent wording across <guideline>, [A1.1], and <condition>.

4 / 5

Actionability

The confirmation gates are copy-paste ready (exact JSON query/options blocks, 'Call `sdd_advance` tool with `stage=design_review`', the 3000-char chunked-write rule), but the core work of stages A1.2–A3.2 is delegated to 'workflows/sop-*.md' files whose paths are never provided — the promised 'Skill File Index' section does not exist in the document. Some concrete but incomplete guidance with missing key details fits the 3 anchor, not the 4 anchor's 'minor gaps'.

3 / 5

Workflow Clarity

The A1→A2→A3→A4 sequence is explicit with per-stage completion criteria, structured user confirmation gates, effort-based exceptions, and precise skip semantics ('Do NOT enter the review stage in order to skip it'). It is not a 5 because verification and per-stage execution details live in the inaccessible SOP files rather than explicit validation steps in this document.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all five references to 'workflows/sop-exploration.md', 'sop-design.md', 'sop-verification.md', 'sop-load-template.md', 'sop-generation.md' point to a nonexistent directory via a 'Skill File Index' section that is absent, while existing bundle files (references/deliverable-review.md, references/feasibility-checklist.md, scripts/assemble-checklist.mjs, scripts/assemble-template.mjs) are never referenced from the body. Navigation to the detail layer is broken, fitting the 2 anchor ('references are buried' / minimal effective structure); not 1 because there is no multi-level nesting and the body itself is well-sectioned.

2 / 5

Total

13

/

20

Passed

Description

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

The description is strong: it states concrete capabilities and provides four explicit 'Use when' triggers that clearly answer both what the skill does and when to invoke it. Its only weaknesses are jargon-heavy terminology and a broad catch-all tail that slightly raises conflict risk with adjacent design skills.

DimensionReasoningScore

Specificity

Lists four concrete actions — 'architecture design, module change planning, interface design, and DFx strategy' — comprehensively covering the transform from 'requirements analysis specifications' to 'implementable system design specifications'. This matches the anchor for multiple specific concrete actions with comprehensive coverage, and exceeds the 4-anchor's 'minor gaps in coverage'.

5 / 5

Completeness

Explicitly answers both: what ('transforms requirements analysis specifications into implementable system design specifications through architecture design, module change planning, interface design, and DFx strategy') and when (four numbered 'Use when' triggers). This is a direct match for the anchor requiring both what AND when with concrete trigger phrases, exceeding the 4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

Includes natural phrases a user of this pipeline would say ('requirements analysis', 'produce a requirements design specification', 'SDD-style design document'), but leans on internal jargon ('DFx strategy', 'frozen zones', 'interface contracts') and lacks common synonyms such as 'system design' or 'technical design'. Good coverage with a few natural terms missing fits the 4 anchor, not the 5 anchor's synonym-and-extension completeness.

4 / 5

Distinctiveness Conflict Risk

The numbered triggers pin it to a distinct pipeline stage, but the trailing catch-all 'or any requirements design and architecture design tasks' widens overlap with general architecture-design skills. Mostly distinct with minor overlap risk fits the 4 anchor; it is not the 5 anchor's 'minimal conflict risk' because of that open-ended clause, and not the 3 anchor since the core triggers are stage-specific.

4 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

XiaoLuoLYG/GOD

Path

jiuwenclaw/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-design/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.