Skip to content
Skills Library
Management & product · Writing

Spec

/Spec

Generate feature specifications from natural language descriptions with foundation-aware template selection and clarification cycles. USE WHEN spec, specification, feature spec, requirements, document feature, create spec, write spec, PRD, product requirements.

Licence
MIT
Last repository change
21.08.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Generate feature specifications from natural language descriptions with foundation-aware template selection and clarification cycles. USE WHEN spec, specification, feature spec, requirements, document feature, create spec, write spec, PRD, product requirements.

Original author description

Generate feature specifications from natural language descriptions with foundation-aware template selection and clarification cycles. USE WHEN spec, specification, feature spec, requirements, document feature, create spec, write spec, PRD, product requirements.

How it works

  1. Customization
  2. Prerequisites
  3. Workflow Routing
  4. Template Selection
  5. Output
  6. Examples
Original SKILL.md headings · 46 lines, 156 words
SKILL.md preview
---
name: Spec
description: Generate feature specifications from natural language descriptions with foundation-aware template selection and clarification cycles. USE WHEN spec, specification, feature spec, requirements, document feature, create spec, write spec, PRD, product requirements.
---

# Spec

Transform feature descriptions into formal specifications using foundation-aware templates.

## Customization

**Before executing, check for user customizations at:**
`~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Spec/`

If this directory exists, load and apply any PREFERENCES.md configurations. If not, proceed with defaults.

## Prerequisites

1. LifeOS must be installed. Check `~/.claude/LIFEOS/VERSION`.
2. Foundation must exist at `/directive/foundation.md`. If missing, inform user: "Run `/buddy:foundation` first."

## Workflow Routing

| Workflow | Trigger | File |
|----------|---------|------|
| **GenerateSpec** | Any invocation with feature description | `Workflows/GenerateSpec.md` |

## Template Selection

Based on foundation type extracted from `/directive/foundation.md`:
- **Default**: `Templates/DefaultSpec.md`
- **JHipster**: `Templates/JHipsterSpec.md`
- **MuleSoft**: `Templates/MuleSoftSpec.md`

## Output

Specifications are written to: `specs/[YYYYMMDD-slug]/spec.md`

## Examples

**Example 1: Generate specification**
```
User: "/buddy:spec user authentication with JWT tokens and password reset"
-> Loads foundation, detects type (default)
-> Loads DefaultSpec.md template
-> Generates specification with requirements, user stories, acceptance criteria
-> Marks unclear areas: [NEEDS CLARIFICATION: Which roles needed?]
-> Writes to specs/20260402-user-authentication/spec.md
```
Files in this package (3)
  • SKILL.md 2 KB
  • Templates/DefaultSpec.md 4 KB
  • Workflows/GenerateSpec.md 3 KB

Versions

RepositoryScoreLicence
This page · rsts-dev/claude-buddy-marketplace95MIT
renzrollon/interlock100MIT
CodaColaLight/nightmill100Apache-2.0
duronext/jig100MIT
optiflowic/keyturn100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
flavien-ia/hypervibe-craft100Apache-2.0

Database snapshot: 13.11.2026 · package version 16f26f595438 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100write-spec
    Write a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.
  • 90product-spec
    Write a product requirements document (PRD) or feature spec. Use when the user describes a feature or product idea and asks for a spec, PRD, requirements, user stories, "scope this", or something to hand to engineers or designers.
  • 100prd-generator
    Generate a full security-focused PRD (Product Requirements Document) from a plain-language feature description. Use this skill whenever someone wants to create a PRD, product spec, feature spec, requirements document, or says things like "write a PRD for", "create a spec for",…
  • 100spec-writer
    Generate Product Requirements Document with EARS syntax and structured ambiguity clarification. Use when: spec, PRD, feature, requirements, product requirements, write spec, new feature.
  • 100prd-template
    Product Requirements Document creation following proven PM template structure. Use when the user asks to create, write, draft, or help with a PRD, product requirements document, product spec, feature specification, or product documentation for a new feature or product.
  • 100spec-writer
    Create a comprehensive Product Requirements Document from conversation and repo context. Use when the user wants a PRD, product spec, feature requirements, or similar documentation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.