Agent skill

Writing Specs

by whiteguo233 in whiteguo233/OpenBiliClaw

A skill your agent uses when authoring a spec or implementation plan, or planning multi-task work.

MITAuto-check passedAgent Workflows

Install Writing Specs

skills CLI
$ npx skills add whiteguo233/OpenBiliClaw --skill writing-specs -a claude-code

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

GitHub CLI
$ gh skill install whiteguo233/OpenBiliClaw writing-specs --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/whiteguo233/OpenBiliClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/writing-specs .claude/skills/writing-specs && 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
writing-specs
GitHub stars
3.4k
Token cost
~1.1k tokens
SKILL.md length
186 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when authoring a spec or implementation plan, or planning multi-task work.

  • Authoring a spec
  • SKILL.md covers Name and commit the pair first, SPEC skeleton, PLAN skeleton and Quantified-gate example
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Implementation plan

What it does

Writing Specs is an agent skill from whiteguo233/OpenBiliClaw. Use when authoring a spec or implementation plan, or planning multi-task work.

Its SKILL.md is about 1.1k 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 Agent Workflows, covering Planning. The repository describes itself as: 本地私有、开源的自进化跨平台 AI 内容发现 Agent:先理解你,再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。(支持 deepseek harness 插件) | Local-first open-source cross-platform AI content discovery…. The licence is MIT.

When your agent uses it

  • Authoring a spec
  • Implementation plan
  • Planning multi-task work

Example prompts

  • “/writing-specs”

What it can do on your machine

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

Writing Specs loads about 1.1k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 186 words of instructions outside code blocks.

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

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 whiteguo233/OpenBiliClaw at commit 2d8fe41, republished under its MIT licence (© whiteguo233). 186 words, ~1,142 tokens.

Download SKILL.mdSave it as .claude/skills/writing-specs/SKILL.md (or your agent's skills folder).
name
writing-specs
description
Use when authoring a spec or implementation plan, or planning multi-task work.

Write Specs and Plans

Produce an authoritative design spec and an executable implementation plan before changing code. Resolve every placeholder against the live repository.

Name and commit the pair first

Create both documents with the same dated slug:

  • docs/plans/YYYY-MM-DD-<slug>-spec.md
  • docs/plans/YYYY-MM-DD-<slug>-plan.md

Commit the pair as docs: add <feature> spec and plan before implementation. Do not mix code into this docs-first commit.

SPEC skeleton

markdown
# <Feature> Spec — <measurable outcome>

**Created:** YYYY-MM-DD
**Scope:** <affected behavior, modules, and integrations>
**Out of scope:** <explicit non-goals>

## Goal

State the current cost or failure, quantified target outcomes, and the exact commands that
verify them.

## Design invariants (MUST hold in every phase)

1. **<Invariant name>:** <falsifiable rule and verification surface>.
2. **<Invariant name>:** <falsifiable rule and verification surface>.

## Current diagnosis

### D1. <Observed problem>

Record evidence at `path/to/file.py:line`; distinguish confirmed facts from hypotheses.

### D2. <Observed problem>

Record the caller, data flow, failure mode, and existing test coverage with `file:line` evidence.

## Priority classification

| Phase | Content | Tier | Why |
| --- | --- | --- | --- |
| 0 | <gate or prerequisite> | **MUST** | <risk it controls> |
| 1 | <main change> | RECOMMENDED | <measured leverage> |

List dependencies, then group work into **Wave A**, **Wave B**, and later waves by risk and
dependency. State what can ship independently and where work may safely stop.

## Phase designs

### Phase 0 — <name>

Define interfaces, algorithms, error behavior, tests, rollout, and numeric acceptance gates.

## Expected impact

| Lever | Measured effect |
| --- | --- |
| <phase> | <quantified result> |

## Documentation obligations

List every module doc, changelog, architecture diagram, CLI/config reference, installer doc,
and README surface triggered by the design.

Every invariant must be testable, every diagnosis must cite live code, and every claimed improvement must have a reproduction command.

PLAN skeleton

markdown
# <Feature> — Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: superpowers:executing-plans (execute this plan task-by-task).
> **Spec:** [`YYYY-MM-DD-<slug>-spec.md`](./YYYY-MM-DD-<slug>-spec.md)
> **Status:** <revision and review state>
> **Execution order:** <dependency-ordered tasks and Wave grouping>
> **Tech:** <runtime, interpreter, focused tests, lint, format, and type-check commands>

**Invariants that MUST hold — re-read before each task:**

- <Restate the spec's invariant without weakening it.>
- <Restate the spec's invariant without weakening it.>

### Task N: <single deliverable>

**Files:** Add/modify/test exact paths.

**Interfaces:** Consumes: <inputs/dependencies>. Produces: <outputs/contracts>.

**Steps:**

- [ ] Write one focused failing test for <behavior>.
- [ ] Run `<focused test command>` and confirm FAIL for the intended missing behavior.
- [ ] Add the minimal implementation needed for that test.
- [ ] Rerun `<focused test command>` and confirm PASS with no warnings.
- [ ] Run the touched regression tests, lint/format checks, and MyPy command.

**Acceptance:**

- Numeric gate: <metric, comparator, threshold, sample size, and failure meaning>.
- Reproduce with `<exact command>`; record the result in the PR.

## Verification after merge

State the production/shadow/canary observation, commands, owner, duration, and rollback trigger.

## Explicitly out of scope

- <non-goal>

Keep the handoff line and checkbox steps verbatim so superpowers/GSD execution conventions remain discoverable. Restate every spec invariant at the plan top and require the executor to re-read them before each task.

Quantified-gate example

For a model-visible profile reduction, a concrete gate is: admission flip rate ≤ 3% and Spearman rank correlation ≥ 0.95 on at least 100 aligned candidates, verified by scripts/run_profile_diet_ab.py. The command, dataset provenance, baseline commit, and observed values belong in the spec and the task acceptance block—not only in a PR comment.

Use docs/plans/2026-07-05-llm-token-diet-spec.md as a reference for quantified invariants, D1..Dn diagnosis, risk Waves, phase designs, impact, and documentation obligations.

© whiteguo233, 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/writing-specs of whiteguo233/OpenBiliClaw.

Open the folder on GitHubat commit 2d8fe41

Compare with similar skills

Writing Specs 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.

Writing Specs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing Specs this skillwhiteguo233/OpenBiliClaw3.4k—~1.1kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Interview Meaddyosmani/agent-skills105k6 repos~3.8kAutomated safety check: PassMIT
OpenSpec Guided OnboardingFission-AI/OpenSpec72k1 repos~4.5kAutomated safety check: PassMIT
Writing Plansgeeksblabla/stateofdev.ma16358 repos~661Automated safety check: PassNone
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone

Similar skills

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    105k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • OpenSpec Guided Onboarding

    Fission-AI/OpenSpec

    Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.

    72k GitHub starsUsed in 1 repo~4.5k tokens
    Agent WorkflowsAuto-check passed
  • Writing Plans

    geeksblabla/stateofdev.ma

    A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…

    163 GitHub starsUsed in 58 repos~661 tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Planning With Files

    jd-opensource/JoySafeter

    Implements Manus-style file-based planning for complex tasks.

    314 GitHub starsUsed in 19 repos~1.8k tokens
    Agent WorkflowsAuto-check: notes

More from whiteguo233/OpenBiliClaw

All 9 skills in this repo
  • Release

    whiteguo233/OpenBiliClaw

    A skill your agent uses when releasing a version, bumping project versions, or pushing release tags.

    3.4k GitHub stars~680 tokensUpdated yesterday
    Auto-check passed
  • Add Platform Source

    whiteguo233/OpenBiliClaw

    Add, repair, or validate an OpenBiliClaw platform source across fetching, account signals, discovery, and user surfaces.

    3.4k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Openbiliclaw Adapter

    whiteguo233/OpenBiliClaw

    Use OpenBiliClaw's versioned Agent Bridge CLI to read multi-source recommendations, profile state, dialogue, probes, saved lists, and submit explicit feedback.

    3.4k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Verify

    whiteguo233/OpenBiliClaw

    Drive a real serve-api process against isolated project roots to verify backend/web changes end-to-end

    3.4k GitHub stars~539 tokensUpdated yesterday
    Auto-check passed
  • System Steward

    whiteguo233/OpenBiliClaw

    管理订阅源与系统配置,所有改动逐项向用户说明并等待批准

    3.4k GitHub stars~238 tokensUpdated yesterday
    Auto-check passed
  • Taste Companion

    whiteguo233/OpenBiliClaw

    默认对话伙伴,陪聊口味与推荐,可读写记忆、查询推荐与观看数据

    3.4k GitHub stars~296 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Writing Specs

What does Writing Specs do?

A skill your agent uses when authoring a spec or implementation plan, or planning multi-task work. Writing Specs is an agent skill from whiteguo233/OpenBiliClaw. Use when authoring a spec or implementation plan, or planning multi-task work.

When should I use Writing Specs?

Writing Specs fits situations like: authoring a spec; implementation plan; planning multi-task work.

How do I install Writing Specs in Claude Code?

Run `npx skills add whiteguo233/OpenBiliClaw --skill writing-specs -a claude-code`. Or copy the skill folder (.claude/skills/writing-specs in whiteguo233/OpenBiliClaw) into .claude/skills/writing-specs in your project. Claude Code loads it when a task matches its description.

How do I install Writing Specs in Codex?

Run `npx skills add whiteguo233/OpenBiliClaw --skill writing-specs -a codex`. Or copy the skill folder (.claude/skills/writing-specs in whiteguo233/OpenBiliClaw) into .agents/skills/writing-specs in your project. Codex loads it when a task matches its description.

Can I use Writing Specs 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 whiteguo233/OpenBiliClaw --skill writing-specs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-specs, .gemini/skills/writing-specs, .github/skills/writing-specs and .opencode/skills/writing-specs in your project.

What does Writing Specs need to run?

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

Does Writing Specs 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 Writing Specs 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 Writing Specs use?

Writing Specs 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 Writing Specs use?

About 1.1k tokens (SKILL.md is roughly 4.6k 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 Writing Specs?

Skills that share tags, products or a category with Writing Specs: Executing Plans Inline (obra/superpowers, 297k stars), Interview Me (addyosmani/agent-skills, 105k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing Specs?

whiteguo233 (a GitHub user) maintains it in whiteguo233/OpenBiliClaw, which has 3,406 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

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