service-create

Generate standardized 10-section service documentation bundles to specs/docs/{svc}.md.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill service-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-create
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/service-create
Command: npx skills add https://github.com/oogDZ/2 --skill service-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new services often lacks consistent documentation. This Skill generates a complete per-service specifications/documentation bundle based on the standard template, reducing manual drafting.

Core Features & Use Cases

  • Standardized documentation: generates a full specs/docs/{svc}.md with 10 sections according to the project standard.
  • SSOT alignment: ensures new service docs follow the single source of truth template to keep specs in sync.
  • Onboarding & pre-work readiness: lightweight onboarding by producing ready-to-fill templates before work begins on a service.

Quick Start

Invoke the /service-create command with the service name to generate the per-service documentation bundle.

Frequently Asked Questions about service-create

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

FAQPage Schema
How do I create standardized service documentation for a new microservice?

To create standardized service documentation, you can generate a complete per-service specifications bundle that enforces a 10-section template. This produces a ready-to-fill markdown file for centralized knowledge alignment.

What is the best way to maintain a single source of truth for service docs?

Maintaining a single source of truth for service docs requires enforcing a standard 10-section template across all services. This ensures new service specifications stay in sync and output to a centralized directory.

How do I generate a 10-section template for missing service specifications?

You generate a 10-section template for missing service specifications by invoking a single creation command with the service name. This outputs a standardized markdown bundle to your project's specs/docs directory.

Can I use this standardized documentation approach for pre-work service onboarding?

Yes, you can use standardized documentation for pre-work service onboarding. It produces lightweight, ready-to-fill templates before development begins, ensuring consistent service specs are established immediately.

Why does my new service lack consistent documentation structure?

New service documentation lacks consistent structure when no standard template is enforced during creation. Generating a per-service specifications bundle with a 10-section format solves this by reducing manual drafting.