new-policy

Create English policy documents with corresponding Korean translations in Markdown.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/ywj3493/claude-skills --skill new-policy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: new-policy
Source: https://github.com/ywj3493/claude-skills/tree/main/skills/new-policy
Command: npx skills add https://github.com/ywj3493/claude-skills --skill new-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating new policy documents and their corresponding Korean translations, ensuring consistency and clarity in team guidelines.

Core Features & Use Cases

  • Standardized Policy Creation: Generates policy documents in a consistent format for both English and Korean.
  • Translation Synchronization: Automatically creates a Korean version alongside the English original.
  • Use Case: When your team decides on a new branching strategy, use this skill to quickly draft and document the policy, making it immediately accessible to everyone in both languages.

Quick Start

Create a new policy document for the 'code review process' with the purpose of ensuring code quality and the rules for peer feedback.

Frequently Asked Questions about new-policy

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

FAQPage Schema
How do I create policy documents with synchronized Korean translations?

You can create policy documents with synchronized Korean translations by using a skill that generates both English and Korean Markdown files simultaneously. This ensures working rules and standards are immediately accessible across languages.

What is the best way to formalize team working rules and standards in documentation?

Formalizing team working rules requires standardizing policy creation within your project's documentation structure. A dedicated skill can enforce predefined Markdown formats to maintain consistency for conventions like branching strategies.

Does generating bilingual policy documentation require a specific Markdown structure?

Generating bilingual policy documentation requires adherence to a predefined Markdown structure for both the English policy content and the Korean translation. This ensures format consistency and clarity across all team guidelines.

Can I use this approach to quickly draft branching strategy policies for my team?

You can quickly draft branching strategy policies for your team by providing the core rules and purpose. The skill formalizes these standards into structured Markdown documentation, making them immediately accessible.

What are the limitations when creating new policy documents across different languages?

Limitations include being restricted to English and Korean outputs while strictly adhering to the predefined Markdown structure. Policy creation cannot deviate from these formatting standards without breaking consistency.

Why do I need translation synchronization for project standards and conventions?

Translation synchronization is needed for project standards to ensure all team members understand working rules regardless of language. It automatically creates a Korean version alongside the English original to prevent misalignment.