skills.rest
DIO0550
DIO0550COMMUNITY
Explore all skills by this author →
GitHub

feature-spec

Generate domain-split feature specifications and PRDs as {domain}-spec.md files.

1|Updated Dec 21, 2025
Search Tags:#templates#frontend#specification#backend#prd#generate#domain-splitting
One-click install
npx skills add https://github.com/DIO0550/d-market --skill feature-spec-dio0550
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/DIO0550/d-market/tree/main/plugins/doc-gen-plugin/skills/feature-spec
Command: npx skills add https://github.com/DIO0550/d-market --skill feature-spec-dio0550

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting feature specifications and PRDs across multiple domains is time-consuming and error-prone; this skill automates that process by generating domain-specific specs from a single prompt, ensuring consistent structure and coverage.

Core Features & Use Cases

  • Domain-based spec generation: outputs one {domain}-spec.md per domain (frontend, backend, data models) plus an index linking all specs.
  • Template-driven documentation: uses frontend/backend/table templates to tailor content for each domain.
  • Use Case: when planning a new feature, generate a complete set of specs (index + domain specs) in minutes to align teams.

Quick Start

Provide a feature name and domains; the tool will generate domain-specific {domain}-spec.md files and an index.

Frequently Asked Questions about feature-spec

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

FAQPage Schema
How do I automatically generate multi-domain feature specifications and PRDs?▼

You can generate domain-split feature specifications by providing a feature name and target domains, which produces domain-specific {domain}-spec.md files for frontend, backend, and data models alongside a linking index.

What is domain splitting in product requirement documents?▼

Domain splitting in PRDs separates specifications into distinct {domain}-spec.md files for frontend, backend, and data models, ensuring consistent structure and comprehensive documentation coverage across different technical areas.

How do I create separate frontend and backend spec files from a single prompt?▼

You create separate frontend and backend spec files from a single prompt by using template-driven generation, which automatically outputs one {domain}-spec.md per requested domain plus a central index linking all generated documentation.

Can I generate data model specifications alongside frontend and backend PRDs?▼

Yes, you can generate data model specifications alongside frontend and backend PRDs, as the template-driven generation applies a domain-based file structure to output tailored {domain}-spec.md files for each specified technical domain.

Does template-driven spec generation work for aligning multiple teams on a new feature?▼

Template-driven spec generation works for aligning multiple teams on a new feature by producing a complete set of domain-specific specs and a linking index in minutes, ensuring consistent structure across frontend, backend, and data model documentation.

Related Skills

Explore More Product & Management Skills→
peterquielpeterquiel
4

domain-model

Document domain models with entities, relationships, and business rules.

Community
Intermediate
LiorCohenLiorCohen
39

domain-population

Populates domain specifications from SPEC.md content using a CLI workflow.

Community
Advanced
ThiagoVitaleThiagoVitale

gsd-complete-milestone

Archive completed milestones and update project documentation for the next version.

Community
Advanced
tgmarinhotgmarinho

to-prd

Convert conversation content into a Product Requirements Document and publish it to an issue tracker.

Community
Advanced