yecl-design

yecl-design is a command for Claude Code from yecllsl/trae-agent-skills. It costs 0 tokens per session (2,083 once invoked), scanned A, original, MIT.

A design command for the YECL software process that creates or refines system architecture and sprint plans from approved product requirements.

In plain words
What is it for?
Use it to create architecture documents, plan development sprints, refine either deliverable, or skip sprint planning when only architecture is needed.
Why use it?
It turns requirements into planned technical work and adds approval points before design documents are saved.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it to create architecture documents, plan development sprints, refine either deliverable, or skip sprint planning when only architecture is needed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yecllsl/trae-agent-skills/yecl-design
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/yecllsl/trae-agent-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for yecl-design

README.md
[![agentmods](https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-design/github.svg)](https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-design)
Your own site
<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-design"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-design/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for yecl-design

Your own site · 80×15
<a href="https://agentmods.dev/commands/yecllsl/trae-agent-skills/yecl-design"><img src="https://agentmods.dev/badge/commands/yecllsl/trae-agent-skills/yecl-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,083 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02083
Opus 5 $0.00000 $0.01042
Sonnet 5 $0.00000 $0.00417
Haiku 4.5 $0.00000 $0.00208

Measured 9d ago against content hash 9b501fa11591, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

yecl-design scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.trae/commands/yecl-design.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Usage

/YECL-design [OPTIONS]

Options

  • --feature <feature_name>: Specify the feature directory (required if not inferable from context)
  • --direct-dev: Skip Sprint planning, produce only the architecture document
  • --target <arch|plan|both>: Refine a single deliverable (default: both). Use arch to refine architecture only, plan to refine sprint plan only.

Context

  • Phase 2 (设计) of .trae/开发流程规范.md §4.2
  • Prerequisite: docs/specs/{feature_name}/01-product-requirements.md must exist (run /YECL-requirements first)
  • Spec outputs: 02-system-architecture.md and 03-sprint-plan.md
  • Re-runnable: if a target document already exists, treats this as a refinement run

Your Role

You are the YECL Coordinator executing Phase 2 (设计). You orchestrate YECL-architect (architecture) and perform Sprint planning to produce quality-scored design deliverables with user approval at each gate.

Primary responsibilities:

  1. Verify PRD prerequisite exists
  2. Mediate all user interactions; YECL-architect does not talk to the user directly
  3. Enforce "don't save until approved" rule for both deliverables (§4.0.2)
  4. Stop at each approval gate (two STOP POINTs)
  5. Achieve architecture quality score ≥ 90 before saving

Execution Flow

Step 0: Input Validation

  1. Parse options: --feature, --direct-dev, --target
  2. Determine feature_name from --feature option or context
  3. Verify prerequisite exists: docs/specs/{feature_name}/01-product-requirements.md
    • If missing, report error and recommend running /YECL-requirements first
  4. Determine target scope: both (default) / arch / plan
  5. If --direct-dev is set, force --target arch (skip sprint planning)

Step 1: Architecture Design (Interactive, via YECL-architect)

Skip if --target plan (plan-only refinement).

Use Task tool with YECL-architect agent (do not save yet):

PRD Path: docs/specs/{feature_name}/01-product-requirements.md
Repository Context: [00-repo-scan.md content or path]
Existing Architecture (if refinement): [content of 02-system-architecture.md if exists]
Feature Name: {feature_name}

Task: Analyze requirements and prepare initial architecture design
Instructions:
1. Read PRD and repository context
2. Create initial architecture (or refine existing one)
3. Calculate quality score
4. Identify technical decisions needing clarification
5. Generate targeted technical questions
6. Return draft architecture, quality score, and questions
7. DO NOT save any files yet

Read the full file on GitHub · 219 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 219 lines · 0 tokens per session scan A 9b501fa11591

Subscribe to this mod's changes

yecl-design is a command published in the GitHub repository yecllsl/trae-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,083 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.