New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Wf Spec Create

by changkun in changkun/wallfacer

Write a new spec from scratch when none exists for the idea yet.

MITAuto-check passedDevelopment

Install Wf Spec Create

skills CLI
$ npx skills add changkun/wallfacer --skill wf-spec-create -a claude-code

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

GitHub CLI
$ gh skill install changkun/wallfacer wf-spec-create --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/changkun/wallfacer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/wf-spec-create .claude/skills/wf-spec-create && 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
wf-spec-create
GitHub stars
112
Token cost
~2.3k tokens
SKILL.md length
1,013 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Write a new spec from scratch when none exists for the idea yet.

  • Works in 8 steps: Parse arguments → Read context → Explore the codebase → …
  • The user says create a spec
  • SKILL.md covers Step 0: Parse arguments, Step 1: Read context, Step 2: Explore the codebase and Step 3: Identify dependencies, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Wf Spec Create is an agent skill from changkun/wallfacer. Write a new spec from scratch when none exists for the idea yet. Gathers context, explores the codebase, fills the frontmatter, and indexes it in specs/README.md. Use when the user says "create a spec", "write a spec", or "new spec". When a spec already exists but is out of date, use refine instead.

Its SKILL.md is about 2.3k 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 Development, covering Technical documentation. The repository describes itself as: Chat, specs, tasks, and code. An autonomous engineering platform. Full autonomy when you trust it. Full control when you don't. The licence is MIT.

When your agent uses it

  • The user says create a spec
  • Tasks that involve Technical documentation

Example prompts

  • “create a spec”
  • “write a spec”
  • “new spec”
  • “/wf-spec-create”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Edit, Write, Agent, Bash(ls *), Bash(mkdir *), Bash(git log *), Bash(git diff *)

Workflow steps

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

  1. Parse arguments
  2. Read context
  3. Explore the codebase
  4. Identify dependencies
  5. Write the spec
  6. Update specs/README.md
  7. Commit
  8. Summary

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Edit
    • Write
    • Agent
    • Bash(ls *)
    • Bash(mkdir *)
    • Bash(git log *)
    • Bash(git diff *)

    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

Wf Spec Create loads about 2.3k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,013 words of instructions outside code blocks.

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

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 changkun/wallfacer at commit 5b3cea1, republished under its MIT licence (© changkun). 1,013 words, ~2,349 tokens.

Download SKILL.mdSave it as .claude/skills/wf-spec-create/SKILL.md (or your agent's skills folder).
name
wf-spec-create
description
Write a new spec from scratch when none exists for the idea yet. Gathers context, explores the codebase, fills the frontmatter, and indexes it in specs/README.md. Use when the user says "create a spec", "write a spec", or "new spec". When a spec already exists but is out of date, use refine instead.
allowed-tools
Read, Grep, Glob, Edit, Write, Agent, Bash(ls *), Bash(mkdir *), Bash(git log *), Bash(git diff *)
argument-hint
<track/name> [one-line description...]
user-invocable
true

Create a Design Spec

Create a new design spec in specs/ following the spec document model.

Step 0: Parse arguments

$ARGUMENTS has the form: <track/name> [description...]

  • The first token is the spec location: <track>/<name> where <track> is one of the tracks this repo actually uses and <name> is the kebab-case spec name without .md. Example: local/live-serve.
  • Never assume a fixed track list — tracks come and go. Read the live set from the directories under specs/, plus any track: frontmatter values in use where specs sit directly in a directory that holds no sub-tracks. Take each track's meaning from its section heading and intro in specs/README.md.
  • If only a name is given without a track, list the live tracks with those one-line meanings and ask the user which one it belongs to.
  • Everything after the first token is a description — a short explanation of what the spec should cover. If no description is provided, ask the user what the spec should address.

Derive the output file path by answering two independent questions from how the tree is actually laid out. They compose: specs/local/003-live-serve.md is a perfectly ordinary path.

If specs/ does not exist yet, bootstrap a flat tree: create specs/, put the first spec directly inside it with the requested track in track: frontmatter, and create specs/README.md in Step 5. Do not force a directory scheme before the project has chosen one.

  1. Which directory? If specs/ has track directories, the spec goes in the one it belongs to: specs/<track>/<name>.md. If specs sit directly under specs/, it goes there and the track is recorded as a track: frontmatter field instead.
  2. Numbered or not? If the sibling specs in that same directory carry an NNN- prefix, give the new one the next number in that directory — usually its current max + 1, zero-padded to three digits. If they do not, use the bare name. Numbering is a per-directory reading-order convention, not a property of the repo, and a repo may number one directory and not another.

The number is a local ordering hint only. Dependency order lives in depends_on, which resolves repo-root-relative and forms one DAG across the whole tree regardless of how any directory is grouped or numbered.

Step 1: Read context

  1. Read specs/README.md to understand the track organization, dependency graph, and what already exists. For a new tree where it is absent, record that Step 5 must create a minimal index.
  2. Review the frontmatter schema and spec conventions. Where they are written down varies by repo — look for a document-model spec under specs/, or an internals doc describing how specs are parsed. If neither exists, infer the schema from the most recently updated spec in the tree.
  3. Grep spec files for any existing specs that overlap with the proposed topic — check by name and by affects paths. If a closely related spec exists, warn the user and ask whether to proceed, merge, or abort.

Step 2: Explore the codebase

Based on the description, identify which parts of the codebase are relevant:

  1. Determine which packages, files, and interfaces the spec will affect.
  2. Use Grep and Glob to find existing code, types, and patterns in those areas.
  3. Launch Agent subagents (Explore type) for up to 3 independent areas in parallel if the spec spans multiple subsystems.
  4. Note existing patterns, interfaces, and constraints that the spec must account for.

The goal is to ground the spec in reality — reference actual file paths, function names, and existing patterns rather than hypothetical code.

Show full SKILL.md (433 more words)Show less

Step 3: Identify dependencies

Determine which existing specs this new spec depends on:

  1. Check specs/README.md for specs that produce interfaces, types, or infrastructure this spec needs.
  2. Check the affects lists of existing specs for overlapping code paths.
  3. Only add depends_on entries for specs whose deliverables are prerequisites — not merely related specs.

Also identify which existing specs might depend on this new one (reverse impact). Flag these to the user but do NOT modify them.

Step 4: Write the spec

Create the spec file at the path derived in Step 0 with this structure (add a track: <track> line under status: only when the spec's directory does not already name its track):

markdown
---
title: <Human-readable title>
status: drafted
depends_on:
  - <spec paths, or empty list>
affects:
  - <code paths and packages this spec will modify>
effort: <small | medium | large | xlarge>
created: <today's date, YYYY-MM-DD>
updated: <today's date, YYYY-MM-DD>
author: your-name
dispatched_task_id: null
---

# <Title>

## Overview

<2-4 sentences: what this spec delivers and why it matters. State the problem,
the user need, or the architectural gap it fills.>

## Current State

<Brief description of what exists today in the codebase that is relevant.
Reference actual file paths, types, and functions. This grounds the spec in
reality and helps readers understand the starting point.>

## Architecture

<How the solution fits into the existing system. Describe the key components,
their relationships, and where they live in the codebase. Use a diagram
(Mermaid) if the relationships are non-trivial.>

## Components

<For each major component or change:>

### <Component Name>

<What it does, where it lives, key design decisions. Reference existing
patterns in the codebase where relevant. Include:>
- File paths (existing files to modify, new files to create)
- Key types and interfaces
- Integration points with existing code

## Data Flow

<How data moves through the system for the primary use cases. Describe the
request/response path, state transitions, or processing pipeline. Skip this
section if the spec doesn't involve data flow.>

## API Surface

<New or modified API routes, CLI flags, env variables, or configuration
options. Follow the repository's existing reference format. Skip this section
if no external surface changes.>

## Error Handling

<How errors are detected, reported, and recovered from. What failure modes
exist and how the system degrades. Skip this section if error handling is
trivial.>

## Testing Strategy

<What to test and how. Reference existing test patterns in the affected
packages. Identify:>
- Unit tests (per-function, per-method)
- Integration tests (cross-package, end-to-end)
- Edge cases and failure scenarios

Writing guidelines:

  • Focus on system design, not inline code. Use references to actual files instead of code blocks where possible.
  • Keep sections proportional to complexity — a simple spec doesn't need all sections. Delete sections marked "skip if..." when they don't apply.
  • Reference existing patterns with a concrete path from the repository instead of re-explaining the pattern.
  • Be specific about file paths and function names. Vague specs produce vague implementations.
  • Size the spec appropriately:
    • Small/medium effort: one file, all sections concise. Can be implemented directly.
    • Large/xlarge effort: may be a parent spec that will be broken down via /wf-spec-breakdown. Focus on architecture and component boundaries rather than implementation details.

Step 5: Update specs/README.md

  1. Read specs/README.md. If it does not exist, create a minimal index with a title, a short explanation of the track recorded in frontmatter, and the spec table below.
  2. Add the new spec to the appropriate track table, maintaining the table's existing order — alphabetical, or by number where the directory is numbered. The link path is whatever Step 0 derived, relative to specs/:
    | [<name>.md](<track>/<name>.md) | Not started | <one-line deliverable> |
  3. If the index keeps a status overview (e.g., a tree of ○/◐/✅ markers), add the spec there as not started (○).
  4. If the spec has dependencies, note them in the dependency graph section if one exists.

Step 6: Commit

Stage the new spec file and the updated specs/README.md. Commit with: specs: add <name> spec for <one-line purpose>

Do NOT push unless the user explicitly asks.

Step 7: Summary

Report to the user:

  • The spec file path and a one-line summary
  • Dependencies identified (both upstream and downstream impact)
  • Effort estimate and rationale
  • Suggested next steps:
    • If large/xlarge: "Run /wf-spec-breakdown <spec-path> design to decompose into sub-design problems"
    • If small/medium: "Run /wf-spec-breakdown <spec-path> tasks to create implementable tasks, or /wf-spec-implement <spec-path> to implement directly"
    • If dependencies are incomplete: "Blocked by <spec>; implement that first or run /wf-spec-impact <spec-path> for full analysis"

© changkun, 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 .claude/skills/wf-spec-create of changkun/wallfacer.

Open the folder on GitHubat commit 5b3cea1

Compare with similar skills

Wf Spec Create 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.

Wf Spec Create compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Wf Spec Create this skillchangkun/wallfacer112—~2.3kAutomated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design47k1 repos~7.5kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Mailspring App ScreenshotsFoundry376/Mailspring18k—~1.5kAutomated safety check: PassGPL-3.0
Draw.io Diagram StudioAgents365-ai/drawio-skill10k—~2.4kAutomated safety check: NotesMIT

Similar skills

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    47k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed

  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed

  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Mailspring App Screenshots

    Foundry376/Mailspring

    Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.

    18k GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 7 days ago
    DevelopmentAuto-check: notes

  • Dark Architecture Diagram Builder

    Cocoon-AI/architecture-diagram-generator

    Creates dark-themed system, cloud, security and network architecture diagrams as self-contained HTML files with inline SVG and CSS.

    7.4k GitHub starsUsed in 1 repo~2.1k tokens
    DevelopmentAuto-check passed

More from changkun/wallfacer

All 14 skills in this repo

  • Wf Spec Breakdown

    changkun/wallfacer

    Split one spec into children — sub-design specs when questions are still open, or implementation-ready leaves when the plan is clear.

    112 GitHub stars~2.6k tokensUpdated 5 days ago
    Auto-check passed

  • Wf Spec Dispatch

    changkun/wallfacer

    Mark a validated spec ready to build and resolve its dependency wiring; where a task board with a transition API is present, create the linked task atomically.

    112 GitHub stars~1.6k tokensUpdated 5 days ago
    Auto-check passed

  • Wf Spec Drive

    changkun/wallfacer

    Run the whole lifecycle for one spec, calling the other skills in order and advancing one legal transition at a time until it reaches a target state (default complete), stopping to ask at…

    112 GitHub stars~2.3k tokensUpdated 5 days ago
    Auto-check passed

  • Wf Spec Report

    changkun/wallfacer

    Survey the whole spec tree: what is complete, in progress, blocked, and actionable next.

    112 GitHub stars~1.6k tokensUpdated 5 days ago
    Auto-check passed

  • Wf Spec Review Impl

    changkun/wallfacer

    Read-only verdict on whether an implementation meets its spec: each acceptance criterion classified, unintended changes flagged, test coverage checked.

    112 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed

  • Wf Spec Validate

    changkun/wallfacer

    Structural lint over the spec tree — required frontmatter fields, valid status and effort values, track location, DAG acyclicity, dispatch consistency, orphans, status consistency.

    112 GitHub stars~2.2k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Wf Spec Create

What does Wf Spec Create do?

Write a new spec from scratch when none exists for the idea yet. Wf Spec Create is an agent skill from changkun/wallfacer. Write a new spec from scratch when none exists for the idea yet.

When should I use Wf Spec Create?

Wf Spec Create fits situations like: the user says create a spec; tasks that involve Technical documentation.

How do I install Wf Spec Create in Claude Code?

Run `npx skills add changkun/wallfacer --skill wf-spec-create -a claude-code`. Or copy the skill folder (.claude/skills/wf-spec-create in changkun/wallfacer) into .claude/skills/wf-spec-create in your project. Claude Code loads it when a task matches its description.

How do I install Wf Spec Create in Codex?

Run `npx skills add changkun/wallfacer --skill wf-spec-create -a codex`. Or copy the skill folder (.claude/skills/wf-spec-create in changkun/wallfacer) into .agents/skills/wf-spec-create in your project. Codex loads it when a task matches its description.

Can I use Wf Spec Create 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 changkun/wallfacer --skill wf-spec-create -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wf-spec-create, .gemini/skills/wf-spec-create, .github/skills/wf-spec-create and .opencode/skills/wf-spec-create in your project.

What does Wf Spec Create need to run?

SKILL.md names no scripts, command-line tools or credentials: Wf Spec Create is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Edit, Write, Agent, Bash(ls *), Bash(mkdir *), Bash(git log *), Bash(git diff *).

Does Wf Spec Create 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 Wf Spec Create 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 Wf Spec Create use?

Wf Spec Create 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 Wf Spec Create use?

About 2.3k tokens (SKILL.md is roughly 9.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 Wf Spec Create?

Skills that share tags, products or a category with Wf Spec Create: Diagram Design (cathrynlavery/diagram-design, 47k stars), Simple English (moeru-ai/airi, 50k stars), Doc Sync (JetBrains/ideavim, 10k stars) and Mailspring App Screenshots (Foundry376/Mailspring, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Wf Spec Create?

changkun (a GitHub user) maintains it in changkun/wallfacer, which has 112 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 4, 2026.

Source: changkun/wallfacer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.