generate-spec-docs

Generate Japanese overview, architecture, and implementation docs from English spec files.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/teliha/dev-workflows --skill generate-spec-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-spec-docs
Source: https://github.com/teliha/dev-workflows/tree/main/skills/generate-spec-docs
Command: npx skills add https://github.com/teliha/dev-workflows --skill generate-spec-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates documentation gaps by automatically generating three specialized Japanese documents from each specification.

Core Features & Use Cases

  • Role-Based Documentation: Create PM overviews, architect designs, and implementation guides from English specs.

Quick Start

generate spec docs for specs/feature-name/spec.md spec docs create Japanese documentation PM documentation architect docs implementation guide

Frequently Asked Questions about generate-spec-docs

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

FAQPage Schema
How do I automatically generate Japanese documentation from English spec files?

This Skill automatically generates Japanese documentation by processing English spec files in the specs/ directory. It creates three role-based documents per feature—overview.ja.md for PMs, architecture.ja.md for architects, and implementation.ja.md for developers—preserving the English source and regenerating on every spec change.

Can I use this to create documentation in multiple languages besides Japanese?

This Skill is specifically designed for Japanese documentation generation from English specs. It produces Japanese-language output only and does not support other target languages.

What file structure and naming conventions do I need for spec files?

Place spec files under specs/ with the naming pattern specs/feature-name/spec.md. The Skill automatically excludes specs/**/docs/ directories to prevent regeneration loops, and outputs three .ja.md files alongside your source spec.

How does this Skill prevent documentation generation from running in loops?

The Skill deliberately excludes the docs/ subdirectory within specs/ from processing. This prevents it from re-triggering on its own generated output, ensuring stable, single-pass documentation generation on spec edits.

Does the original English spec get replaced or preserved?

The original English spec file is always preserved. Generated Japanese documentation is output as separate .ja.md files, leaving your source spec unchanged with a timestamp and source reference included.

When does documentation regenerate after I edit a spec file?

Documentation regenerates automatically after every spec file change. The Skill activates on spec edits and produces fresh Japanese documents each time, maintaining current alignment with your English specifications.

Related Skills