skills.rest
wendeus0
wendeus0COMMUNITY
Explore all skills by this author →
GitHub

spec-editor

Convert user requests into testable SPEC.md files with YAML front matter.

Updated Aug 27, 2026
Search Tags:#documentation#spec#feature-spec#front-matter#spec-format#spec-editor
One-click install
npx skills add https://github.com/wendeus0/AI-dotfiles --skill spec-editor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-editor
Source: https://github.com/wendeus0/AI-dotfiles/tree/main/core/skills/spec-editor
Command: npx skills add https://github.com/wendeus0/AI-dotfiles --skill spec-editor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform user requests into small, well-scoped SPECs for software features, enabling clear boundaries, faster validation, and easier handoff to implementation.

Core Features & Use Cases

  • SPEC generation: Produces a valid SPEC.md with canonical YAML front matter and a well-structured body aligned to docs/architecture/SPEC_FORMAT.md.
  • Scope management: Enforces scope that fits 1-3 days of work and reduces oversized or ambiguous requests to the smallest viable slice.
  • Feature review: Supports revising existing features/*/SPEC.md or docs/architecture/SPEC_FORMAT.md for consistency and clarity.
  • Guided clarity: Highlights unresolved questions and explicit acceptance criteria to drive testable outcomes.

Quick Start

Para começar, forneça um pedido de usuário para uma feature; a skill gerará um rascunho de SPEC.md.

Frequently Asked Questions about spec-editor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a feature request into a testable spec?▼

To convert a feature request into a testable spec, provide the prompt to generate a SPEC.md with canonical YAML front matter and structured acceptance criteria aligned to your architecture's spec format.

What is the best way to scope an ambiguous feature request?▼

Scoping an ambiguous feature request involves reducing oversized requirements to the smallest viable slice that fits 1-3 days of work, producing a well-defined SPEC.md with explicit and testable acceptance criteria.

How do I write SPEC.md front matter for a new feature?▼

Writing SPEC.md front matter requires including specific metadata fields: feature, title, status, and created. These canonical YAML fields ensure the generated feature spec remains valid and testable.

Can I use a spec generator to revise an existing feature SPEC.md?▼

Yes, you can use a spec generator to revise existing features/*/SPEC.md or docs/architecture/SPEC_FORMAT.md files. It highlights unresolved questions and updates boundaries for consistency and clarity.

When do I need to generate a feature SPEC instead of coding directly?▼

You need to generate a feature SPEC when a feature lacks a SPEC.md or its scope is ambiguous and too large. It establishes clear boundaries, enables faster validation, and creates easier handoff to implementation.

Related Skills

Explore More Software Engineering Skills→
anam-organam-org
118

docs-page-frontmatter

Generate YAML front matter with title and description fields for documentation pages.

Official
Basic
notquenotque
415

spec-writer

Create a SPEC.md with user stories, acceptance criteria, and risks.

Community
Advanced
aws-samplesaws-samples
21

test-case-generator

Generate structured test cases from spec.md acceptance criteria with 1:1 traceability.

Official
Intermediate
nesihaver-ILnesihaver-IL

create-issue

Create structured issues in GitHub Issues, Linear, or Jira.

Community
Intermediate