Agent skill

Spec Workflow

by LeoYeAI in LeoYeAI/openclaw-master-skills

Standard software engineering workflow for requirement analysis, technical design, and task planning.

MITAuto-check passedFrontend & Design

Install Spec Workflow

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills spec-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cloudbase/references/spec-workflow .claude/skills/spec-workflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
spec-workflow
GitHub stars
2.2k
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
611 words
Files
1
Skills in repo
972
Repo updated
First seen
Licence
MIT

At a glance

Standard software engineering workflow for requirement analysis, technical design, and task planning.

  • Works in 4 steps: Requirements Document and Acceptance… → Technical Solution Design → Task Breakdown → …
  • Developing new features
  • SKILL.md covers When to use this skill, How to use this skill (for a…, Workflow Overview and Phase 1: Requirements Document…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Spec Workflow is an agent skill from LeoYeAI/openclaw-master-skills. Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UI design and Planning. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Developing new features
  • Complex architecture designs
  • Multi-module integrations
  • Projects involving database/UI design

Example prompts

  • “/spec-workflow”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Requirements Document and Acceptance Criteria Design
  2. Technical Solution Design
  3. Task Breakdown
  4. Task Execution

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Spec Workflow loads about 1.4k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 611 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 611 words, ~1,352 tokens.

Download SKILL.mdSave it as .claude/skills/spec-workflow/SKILL.md (or your agent's skills folder).
name
spec-workflow
description
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.
alwaysApply
false

When to use this skill

Use this skill for structured development workflow when you need to:

  • Develop new features from scratch
  • Design complex architecture
  • Integrate multiple modules
  • Work on projects involving database design
  • Work on projects involving UI design
  • Ensure high-quality requirement analysis and acceptance criteria

Do NOT use for:

  • Simple bug fixes
  • Documentation updates
  • Configuration changes
  • Code refactoring (unless explicitly requested)

How to use this skill (for a coding agent)

  1. Follow the workflow strictly

    • Each phase must be completed and confirmed by user before proceeding to next phase
    • Never skip phases or proceed without user confirmation
    • Use interactiveDialog tool when clarification is needed
  2. Apply EARS requirement syntax

    • Use EARS (Easy Approach to Requirements Syntax) for requirement descriptions
    • Format: While <optional precondition>, when <optional trigger>, the <system name> shall <system response>
  3. Reference UI design rules when needed

    • If requirements involve frontend pages, must strictly reference ui-design skill
    • Determine design style and color palette in requirements phase
    • Confirm design details with user before finalizing requirements
  4. Update task status

    • Keep task status updated in tasks.md file
    • Mark tasks as completed when finished
    • Work independently and efficiently while maintaining quality

Spec Workflow

Important: You must follow these rules. Each phase must be confirmed by the user before proceeding to the next phase.

Workflow Overview

  1. If you determine that the user's input is a new requirement, you can work independently following standard software engineering practices. Confirm with user when necessary, and can use interactiveDialog tool to collect information.

  2. Whenever the user inputs a new requirement, to standardize requirement quality and acceptance criteria, you must first understand the problem and requirements clearly. You must confirm with the user before proceeding to the next phase.

Phase 1: Requirements Document and Acceptance Criteria Design

First complete the requirements design using EARS (Easy Approach to Requirements Syntax) method. If you determine the requirements involve frontend pages, you must strictly reference ui-design skill. Determine design style and color palette in the requirements phase. You must confirm requirement details with the user. After final confirmation, the requirements are finalized, then proceed to the next phase.

Save to specs/spec_name/requirements.md. After confirming with the user, proceed to the next phase.

Reference format:

markdown
# Requirements Document

## Introduction

Requirement description

## Requirements

### Requirement 1 - Requirement Name

**User Story:** User story content

#### Acceptance Criteria

1. Use EARS syntax: While <optional precondition>, when <optional trigger>, the <system name> shall <system response>. For example: When "Mute" is selected, the laptop shall suppress all audio output.
2. ...
...
Show full SKILL.md (245 more words)Show less

Phase 2: Technical Solution Design

After completing the requirements design, based on the current technical architecture and the confirmed requirements above, design the technical solution. It should be concise but accurately describe the technical architecture (e.g., architecture, tech stack, technology selection, database/interface design, test strategy, security). Use mermaid diagrams when necessary.

Save to specs/spec_name/design.md. You must confirm with the user clearly, then proceed to the next phase.

Phase 3: Task Breakdown

After completing the technical solution design, based on the requirements document and technical solution, break down specific tasks. You must confirm with the user clearly, then save to specs/spec_name/tasks.md. After confirming with the user, proceed to the next phase and begin formal task execution. You need to update task status in a timely manner. When executing, work as independently and autonomously as possible to ensure efficiency and quality.

Task reference format:

markdown
# Implementation Plan

- [ ] 1. Task Information
  - Specific things to do
  - ...
  - _Requirement: Related requirement point number

Phase 4: Task Execution

  • Begin formal task execution
  • Update task status in tasks.md file in real-time
  • Work independently and autonomously
  • Ensure efficiency and quality
  • Mark tasks as completed when finished

Key Principles

  1. User Confirmation Required: Each phase must be confirmed by the user before proceeding
  2. EARS Syntax: Use EARS method for requirement descriptions
  3. UI Design Integration: When requirements involve frontend pages, must reference UI design rules and determine design style in requirements phase
  4. Technical Accuracy: Technical solutions should be concise but accurate
  5. Task Tracking: Keep task status updated throughout execution
  6. Independent Execution: Work autonomously while maintaining quality

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/cloudbase/references/spec-workflow of LeoYeAI/openclaw-master-skills.

Open the folder on GitHubat commit e5199b5

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in LeoYeAI/openclaw-master-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Spec Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Spec Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Workflow this skillLeoYeAI/openclaw-master-skills2.2k1 repos~1.4kAutomated safety check: PassMIT
Improve UI Audit and Plansibelick/ui-skills9.5k—~2kAutomated safety check: PassMIT
Design LabNeverSight/learn-skills.dev2161 repos~7.5kAutomated safety check: PassNone
UI Skills Routeribelick/ui-skills9.5k2 repos~362Automated safety check: PassMIT
Orca Chat Visualsstablyai/orca87k—~933Automated safety check: PassMIT
Videoohad6k/emulo2931 repos~8.3kAutomated safety check: PassMIT

Similar skills

  • Audits one product surface against its own design evidence and writes self-contained implementation plans for another agent, without touching product source.

    9.5k GitHub stars~2k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Design Lab

    NeverSight/learn-skills.dev

    Conduct design interviews, generate five distinct UI variations in a temporary design lab, collect feedback, and produce implementation plans.

    216 GitHub starsUsed in 1 repo~7.5k tokens
    Frontend & DesignAuto-check passed
  • UI Skills Router

    ibelick/ui-skills

    Routes UI tasks to the smallest useful set of UI Skills through the ui-skills CLI, picking a category and loading at most three skills before implementing.

    9.5k GitHub starsUsed in 2 repos~362 tokens
    Frontend & DesignAuto-check passed
  • Orca Chat Visuals

    stablyai/orca

    Show a chart, diagram, timeline, comparison or UI mockup inline in this Orca chat by writing one self-contained HTML file and adding a visual line to your reply.

    87k GitHub stars~933 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Video

    ohad6k/emulo

    A skill your agent uses when a brief has to become a film. An agent skill from ohad6k/emulo.

    293 GitHub starsUsed in 1 repo~8.3k tokens
    Frontend & DesignAuto-check passed
  • Product Design Workflow Bundle

    XiaomiMiMo/MiMo-Code

    Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.

    14k GitHub stars~721 tokensUpdated 5 days ago
    Frontend & DesignAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 972 skills in this repo
  • DevOps Pipeline Management

    LeoYeAI/openclaw-master-skills

    Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    LeoYeAI/openclaw-master-skills

    Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    LeoYeAI/openclaw-master-skills

    Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    LeoYeAI/openclaw-master-skills

    Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    LeoYeAI/openclaw-master-skills

    Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Spec Workflow

What does Spec Workflow do?

Standard software engineering workflow for requirement analysis, technical design, and task planning. Spec Workflow is an agent skill from LeoYeAI/openclaw-master-skills. Standard software engineering workflow for requirement analysis, technical design, and task planning.

When should I use Spec Workflow?

Spec Workflow fits situations like: developing new features; complex architecture designs; multi-module integrations; projects involving database/UI design.

How do I install Spec Workflow in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a claude-code`. Or copy the skill folder (skills/cloudbase/references/spec-workflow in LeoYeAI/openclaw-master-skills) into .claude/skills/spec-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Spec Workflow in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a codex`. Or copy the skill folder (skills/cloudbase/references/spec-workflow in LeoYeAI/openclaw-master-skills) into .agents/skills/spec-workflow in your project. Codex loads it when a task matches its description.

Can I use Spec Workflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill spec-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spec-workflow, .gemini/skills/spec-workflow, .github/skills/spec-workflow and .opencode/skills/spec-workflow in your project.

What does Spec Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Spec Workflow is instructions for the agent only.

Does Spec Workflow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Spec Workflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Spec Workflow use?

Spec Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Spec Workflow use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Spec Workflow?

Skills that share tags, products or a category with Spec Workflow: Improve UI Audit and Plans (ibelick/ui-skills, 9.5k stars), Design Lab (NeverSight/learn-skills.dev, 216 stars), UI Skills Router (ibelick/ui-skills, 9.5k stars) and Orca Chat Visuals (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Workflow?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,159 GitHub stars. The repository holds 972 skills in this directory. The repository was last updated on July 20, 2026.

Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.