メニュー
Initialize and use a specification-driven workflow with steering docs, reusable templates, and per-feature spec folders. Use when a project needs a structured path from product intent to requirements, design, and tasks before coding.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Open local review artifacts in Xiaoer Omia when users ask to open, preview, inspect, or review a file.
Run a measured improvement loop for a skill by defining a yes/no checklist, capturing a baseline, scoring candidate outputs, and logging each iteration's keep/revert decision. Use when a skill works inconsistently and you want evidence-driven iteration instead of random prompt edits.
Build a static HTML report site from CSV, JSON, Markdown, or HTML inputs. Use when the user wants to turn existing data into a human-readable site, generate a data showcase page, create a static report website, or optionally publish the built site.
Add offline multilingual support to static HTML, small web projects, or reports by extracting text into tokens, maintaining language dictionaries, applying translated outputs, and optionally embedding a local language switcher. Use when the user asks for bilingual support, tokenizing Chinese copy, offline language switching, or i18n for reports and lightweight sites.
Unified entrypoint for Obsidian note operations such as cleanup, merge, lint/fix, meeting archive, daily rollover, and docs sync. Use when the user wants one command surface over an existing notes-tools repo instead of calling many atomic scripts by hand.
Test, tune, and regression-check LLM system prompts with a golden dataset. Use when the user wants to optimize a prompt, run prompt regression tests, manage `cases.yaml`, compare expected vs actual outputs, or follow a TDD workflow for prompts.
SOC 職業分類に基づく
| name | spec-workflow |
| description | Initialize and use a specification-driven workflow with steering docs, reusable templates, and per-feature spec folders. Use when a project needs a structured path from product intent to requirements, design, and tasks before coding. |
| version | 1.0.0 |
| author | Vivi |
| tags | ["spec","workflow","planning","scaffolding"] |
| platforms | ["all"] |
| dependencies | ["python3"] |
Turn the hidden .spec-workflow pattern into a stable public skill. This skill gives projects a predictable place for product steering, technical steering, structure conventions, approvals, archive history, and per-feature specs.
.spec-workflow directories aroundcheck to confirm the bundled templates exist.init in a project root to create .spec-workflow and steering docs.new-spec to create a feature-level spec folder with requirements/design/tasks docs..spec-workflow/user-templates/.Check the bundle:
python3 main.py check
Initialize a workflow:
python3 main.py init --root /absolute/path/to/project --project-name "Energy OS" --author Developer_Lead
Create a new feature spec:
python3 main.py new-spec --root /absolute/path/to/project --name "dashboard sync" --author Developer_Lead
.spec-workflow tree plus generated steering docs and per-feature spec docsMinimum validation commands:
python3 main.py check
python3 -m py_compile main.py
Recommended end-to-end validation:
python3 main.py init --root /tmp/spec-demo --project-name "Spec Demo" --author Developer_Lead
python3 main.py new-spec --root /tmp/spec-demo --name "dashboard sync" --author Developer_Lead
new-spec expects the project to be initialized first