write-book

Generate README, features, and business rules documentation from domain inputs.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ureca-corp/claude --skill write-book
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-book
Source: https://github.com/ureca-corp/claude/tree/main/plugins/domain-book-builder/skills/5-write-book
Command: npx skills add https://github.com/ureca-corp/claude --skill write-book

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of essential documentation for a domain, ensuring completeness and consistency across README, features, and business rules.

Core Features & Use Cases

  • Automated Document Generation: Creates README.md, features.md, and business-rules.md based on provided domain inputs.
  • Consistency Enforcement: Ensures technical terms are avoided and Korean messages are used where appropriate.
  • Use Case: After defining your domain model and API specifications, use this skill to automatically generate the comprehensive documentation required for your project, saving significant manual writing time.

Quick Start

Use the write-book skill to generate the README, features, and business rules for the 'users' domain.

Frequently Asked Questions about write-book

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

FAQPage Schema
How do I automatically generate a README and business rules documentation from a domain model?

Automated domain documentation generation works by integrating your domain model and API specifications to produce README.md, features.md, and business-rules.md artifacts. This mechanism ensures comprehensive documentation completeness while enforcing technical term avoidance and Korean message usage for clarity.

When do I need to generate domain documentation for my project?

You need domain documentation generation after defining your domain model and API specifications, when you require comprehensive README, features, and business rules artifacts. This process ensures consistency and completeness across your project documentation while saving significant manual writing time.

Can I generate technical documentation that enforces non-technical language and Korean messages?

Yes, you can enforce non-technical language and Korean message usage in technical documentation by using automated domain documentation generation. It ensures technical terms are avoided and Korean messages are used where appropriate, making the generated README and business rules clear and accessible.

What is the best way to create a domain book with features and business rules?

The best way to create a domain book with features and business rules is to automate generation of README.md, features.md, and business-rules.md files. By integrating domain model and API specifications, this approach ensures consistency and completeness while avoiding technical terms and using Korean messages for clarity.

Does automated domain documentation generation work with existing API specifications?

Yes, automated domain documentation generation works with existing API specifications by integrating them with your domain model. It uses these inputs to automatically generate the comprehensive documentation required for your project, including README, features, and business rules files, saving significant manual writing time.