New: 97,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

Spec Writer

by MageByte-Zero in MageByte-Zero/spec-superflow

Create or refine spec-superflow planning artifacts. An agent skill from MageByte-Zero/spec-superflow.

MITAuto-check passedFrontend & Design

Install Spec Writer

skills CLI
$ npx skills add MageByte-Zero/spec-superflow --skill spec-writer -a claude-code

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

GitHub CLI
$ gh skill install MageByte-Zero/spec-superflow spec-writer --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/MageByte-Zero/spec-superflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spec-writer .claude/skills/spec-writer && 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-writer
GitHub stars
839
Used in
1 other repo
Token cost
~1.6k tokens
SKILL.md length
780 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Create or refine spec-superflow planning artifacts. An agent skill from MageByte-Zero/spec-superflow.

  • Tasks that involve Design tokens
  • SKILL.md covers Bundled runtime, New planned changes, Required Inputs and Config Check, plus 7 more sections
  • Calls node

What it does

Spec Writer is an agent skill from MageByte-Zero/spec-superflow. Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.

Its SKILL.md is about 1.6k 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 Design tokens. The repository describes itself as: 源码级融合 OpenSpec 规划引擎 + Superpowers 执行纪律的 AI 编程工作流插件。17 平台支持，9 skills，Spec-first，契约驱动。 The licence is MIT.

When your agent uses it

  • Tasks that involve Design tokens

Example prompts

  • “/spec-writer”

What it can do on your machine

Read from SKILL.md and the folder at commit 25d9b0c. 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

    Shell commands in SKILL.md call:

    • node

    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 Writer loads about 1.6k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 780 words of instructions outside code blocks.

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

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 MageByte-Zero/spec-superflow at commit 25d9b0c, republished under its MIT licence (© MageByte-Zero). 780 words, ~1,603 tokens.

Download SKILL.mdSave it as .claude/skills/spec-writer/SKILL.md (or your agent's skills folder).
name
spec-writer
description
Create or refine spec-superflow planning artifacts. Invoke when the change is understood well enough to write proposal.md, specs/, design.md, and tasks.md.

Spec Writer

Bundled runtime

Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.

Create or refine planning artifacts when the change has moved beyond exploration.

New planned changes

For a new request (no state or workflow auto), or workflow_variant planned, write proposal.md and tasks.md together without pausing between individual artifacts. Proposal holds the goal, in/out scope, acceptance and risks; tasks holds ordered deliverables and proof commands. Add specs only for behavior needing durable scenarios and design only for unresolved architectural decisions. Do not create execution-contract.md or duplicate the task list in another plan.

Check shared interfaces against the real source once, then self-check the problem, scope, dependencies and proof. Present one approval request only if this concrete plan lacks approval. After approval run SSF workflow start <dir> --path planned --confirm --reason "<user decision>" and continue implementation. No intermediate planning/bridging transitions or independent reader agent. A semantic revision uses the same command after approval; a nonsemantic correction uses execution resync and retains failed-review history. The remaining sections apply only to existing legacy changes.

Required Inputs

Read .spec-superflow.yaml (especially dp_0_decisions, dp_0_confirmed) and any existing planning artifacts. If dp_0_confirmed is not true, stop and route back to workflow-start for DP-0.

Config Check

Run: SSF runtime config --get artifacts.order — generate in configured order (default: proposal → specs → design → tasks). Run with artifacts.skip — skip any listed artifacts.

Artifact Roles

  • proposal.md: why and scope
  • specs/: required behavior (testable)
  • design.md: architecture decisions and trade-offs (not line-by-line)
  • tasks.md: dependency-aware implementation steps

Working Rules

Honor DP-0: Read dp_0_decisions, respect confirmed constraints, don't silently expand scope. Pause on unconfirmed decisions.

proposal.md

Must state: observed problem, what changes, in/out scope, impact areas, and proof of completion. Prefer concrete facts over empty adjectives such as “better”, “robust”, or “efficient”.

specs/

Every requirement must be testable. Use SHALL or MUST. Every requirement must have at least one #### Scenario: with WHEN/THEN. Group under ADDED/MODIFIED/REMOVED Requirements headers.

design.md

Must have: relevant facts and constraints, goals and non-goals, decisions (Choice + Rationale + Alternatives + Consequences), and risks with verification evidence. Do not invent stakeholders, migration steps, or open questions when they do not affect the decision.

tasks.md

Must include a delivery/proof map and dependency-aware tasks. Each task names the affected path or bounded area, the observable outcome, and the evidence command. Keep RED/GREEN details, review receipts, and dispatch mechanics in the execution contract/task brief; do not inflate reader-facing tasks into five ritual substeps.

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

Artifact Generation

Enter specifying before creating or editing planning artifacts: run SSF state transition <change-dir> specifying only if not already there. On resume, continue incomplete artifacts; do not self-transition. Full planning may omit specs only for explicitly unchanged behavior, and may omit design by configuration. Full cannot skip tasks: correct this configuration before generating the pack.

When DP-0 has made the scope clear, generate the configured planning pack (proposal, delta specs from templates/spec.md, design, and tasks) in order without pausing between individual artifacts. Validate the pack, then request one DP-2 review. Pause earlier only when the missing decision can change user-visible behavior, compatibility, security, delivery scope, or the selected design; or when artifacts state incompatible scope.

Validation Checklist

proposal.md
  • ## Why > 50 chars, ## What Changes, ## Scope (In/Out), ## Impact, no TBD/TODO; claims name an observed problem and a completion proof
specs/
  • SHALL/MUST for required behavior, #### Scenario: with WHEN/THEN per requirement, grouped under delta headers, no contradictions
design.md
  • facts/constraints, goals/non-goals, ## Decisions (≥1, with Choice+Rationale+Alternatives+Consequences), risks and verification
tasks.md
  • delivery/proof map, numbered tasks, affected paths or bounded areas, observable outcomes, no placeholders, every requirement mapped, explicit dependencies
  • Must use the template checkbox format (one - [ ] per task on its own line); the guard enforces this format when entering execution

If any artifact fails validation, fix before handing off to contract-builder.

DP-2: Artifact Review Gate

Present a concise summary of the configured artifacts. Self-check five questions once: problem, command boundary, invalidation boundary, continuation boundary, and document flow. Do not dispatch a blind-reader subagent unless the user explicitly requested delegation. Reuse approval already covering these artifacts; ask one consolidated question only for a new material decision or missing artifact approval. Do not add a separate continuation question. After approval:

bash
SSF state set <change-dir> dp_2_result "approved: <summary>"
SSF state set <change-dir> dp_2_timestamp now

After DP-2 is recorded, remain in specifying and continue to contract-builder.

Handoff Rule

Do not start implementation after writing planning artifacts. Once stable, validated, and DP-2 is recorded, hand off to contract-builder.

Exception Handling

  • Parse failures: Report specific file/error; don't generate from corrupted templates
  • Missing templates: Fall back to artifact structure defined in this skill
  • User interruption: Artifacts on disk are the recovery checkpoint; resume from first missing/incomplete one
  • Validation failure: Fix before handoff — do not hand off broken artifacts

© MageByte-Zero, 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/spec-writer of MageByte-Zero/spec-superflow.

Open the folder on GitHubat commit 25d9b0c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in MageByte-Zero/spec-superflow, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Spec Writer 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 Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Spec Writer this skillMageByte-Zero/spec-superflow8391 repos~1.6kAutomated safety check: PassMIT
Refactoring UIs0xDk/refactoring-ui-skill584—~3.5kAutomated safety check: PassMIT
Kaizen UINVIDIA/Personal-AI-Router1.6k—~4.7kAutomated safety check: PassApache-2.0
UX Create Manifesth0x91b/dev-3.0307—~2.7kAutomated safety check: PassApache-2.0
Extract Designdanielvm-git/bigpowers256—~1kAutomated safety check: PassMIT
Build Screentsubotax/melta-ui201—~1.3kAutomated safety check: PassMIT

Similar skills

  • Refactoring UI

    s0xDk/refactoring-ui-skill

    Design and improve user interfaces using the concrete rules from Refactoring UI (Wathan & Schoger) — constrained spacing/type/color/shadow scales, visual hierarchy through weight and color rather…

    584 GitHub stars~3.5k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed

  • Kaizen UI

    NVIDIA/Personal-AI-Router

    Official

    Kaizen UI (KUI) component library and design-pattern advisor for NVIDIA applications.

    1.6k GitHub stars~4.7k tokensUpdated today
    Frontend & DesignAuto-check passed

  • UX Create Manifest

    h0x91b/dev-3.0

    Create the initial Product UX Bible for an existing web or full-screen web app by deeply auditing the repository, using sub-agents when available, and generating docs/ux manifests, schemas, budgets…

    307 GitHub stars~2.7k tokensUpdated yesterday
    Frontend & DesignAuto-check passed

  • Extract Design

    danielvm-git/bigpowers

    Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose.

    256 GitHub stars~1k tokensUpdated 16 days ago
    Frontend & DesignAuto-check passed

  • Build Screen

    tsubotax/melta-ui

    melta DS の契約から画面 1 枚（ページ / スクリーン）を生成し、checkhtml で自己検証して coverage と評価不可まで報告する。トリガー: 「画面を作って」「〜ページを生成」「画面生成」「ダッシュボードを作って」「設定画面を作って」「build screen」「generate a page」。AGENTS.md のタスクベース読み込みガイドで契約を引き当て、最大 3…

    201 GitHub stars~1.3k tokensUpdated 10 days ago
    Frontend & DesignAuto-check passed

  • Init

    DeL-TaiseiOzaki/claude-code-orchestra

    Analyze project structure, populate .claude/docs/DESIGN.md, and write the thin Repository Identity section in .claude/STATE.md.

    199 GitHub stars~1.8k tokensUpdated 17 days ago
    Frontend & DesignAuto-check passed

More from MageByte-Zero/spec-superflow

All 9 skills in this repo

  • Bug Investigator

    MageByte-Zero/spec-superflow

    A skill your agent uses when encountering any bug, test failure, or unexpected behavior during spec-superflow execution, before proposing fixes.

    839 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Need Explorer

    MageByte-Zero/spec-superflow

    Clarify intent, scope, constraints, and success criteria before artifact creation.

    839 GitHub starsUsed in 1 repo~805 tokens
    Auto-check passed

  • Build Executor

    MageByte-Zero/spec-superflow

    Execute an active direct request or approved planned change.

    839 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Contract Builder

    MageByte-Zero/spec-superflow

    Maintain an execution contract only for an existing legacy change that requires one.

    839 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Release Archivist

    MageByte-Zero/spec-superflow

    Close out a spec-superflow change with verification, summary, and archive readiness.

    839 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

  • Workflow Start

    MageByte-Zero/spec-superflow

    Primary entry point for the spec-superflow state-machine workflow.

    839 GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

Categories

Questions about Spec Writer

What does Spec Writer do?

Create or refine spec-superflow planning artifacts. An agent skill from MageByte-Zero/spec-superflow. Spec Writer is an agent skill from MageByte-Zero/spec-superflow. Create or refine spec-superflow planning artifacts.

When should I use Spec Writer?

Spec Writer fits situations like: tasks that involve Design tokens.

How do I install Spec Writer in Claude Code?

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

How do I install Spec Writer in Codex?

Run `npx skills add MageByte-Zero/spec-superflow --skill spec-writer -a codex`. Or copy the skill folder (skills/spec-writer in MageByte-Zero/spec-superflow) into .agents/skills/spec-writer in your project. Codex loads it when a task matches its description.

Can I use Spec Writer 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 MageByte-Zero/spec-superflow --skill spec-writer -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-writer, .gemini/skills/spec-writer, .github/skills/spec-writer and .opencode/skills/spec-writer in your project.

What does Spec Writer need to run?

Going by SKILL.md and its folder, Spec Writer needs the command-line tools its instructions call (node).

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

Spec Writer 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 Writer use?

About 1.6k tokens (SKILL.md is roughly 6.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 Writer?

Skills that share tags, products or a category with Spec Writer: Refactoring UI (s0xDk/refactoring-ui-skill, 584 stars), Kaizen UI (NVIDIA/Personal-AI-Router, 1.6k stars), UX Create Manifest (h0x91b/dev-3.0, 307 stars) and Extract Design (danielvm-git/bigpowers, 256 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Spec Writer?

MageByte-Zero (a GitHub user) maintains it in MageByte-Zero/spec-superflow, which has 839 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.

Source: MageByte-Zero/spec-superflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.