create-justification

Name: create-justification
Availability: InStock
Author: LKPioniere

Create markdown justification files with unique three-word identifiers and frontmatter.

Updated Aug 23, 2026

Search Tags:#automation #documentation #markdown #decision-making #filename #justification

Ready to run

npx skills add https://github.com/LKPioniere/lohnlab-esign --skill create-justification-lkpioniere

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-justification
Source: https://github.com/LKPioniere/lohnlab-esign/tree/main/.agents/skills/create-justification
Command: npx skills add https://github.com/LKPioniere/lohnlab-esign --skill create-justification-lkpioniere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of standardized justification notes by generating a new markdown file in .agents/justifications/ with a unique three-word identifier, frontmatter, and a formatted title, ensuring consistent documentation of decisions.

Core Features & Use Cases

Generates a new justification file named with a unique three-word id and a slug, e.g., swift-emerald-river-decision-name.md, ensuring no filename conflicts.
Adds frontmatter containing the current date and a properly formatted title to support organization and retrieval.
Use Case: teams document architectural decisions, policy rationales, and design trade-offs with traceable justification records.

Quick Start

Provide a decision name and content to generate a new justification file in .agents/justifications with a unique three-word ID.

Frequently Asked Questions about create-justification

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

FAQPage Schema

How do I automate documentation for decision-making records in markdown?▼

Automating decision-making documentation involves generating a markdown justification file with a unique three-word ID, frontmatter date, and formatted title. This ensures standardized, traceable records of architectural decisions and design trade-offs without manual file setup.

What is the best way to prevent filename conflicts when creating justification files?▼

To prevent filename conflicts when creating justification files, the system uses a unique three-word identifier combined with a slug. This naming convention guarantees that each generated markdown file remains distinct within the justifications directory.

How do I generate a markdown file with frontmatter for policy rationales?▼

Generating a markdown file with frontmatter for policy rationales requires providing a decision name and content. The system automatically adds current date frontmatter and a formatted title, producing a uniquely named file for organizational retrieval.

Does the generated justification markdown file include metadata for organization?▼

The generated justification markdown file includes frontmatter containing the current date and a properly formatted title. This metadata supports organization and retrieval of decision records within your documentation directory.

What format is used for the filename when automating justification notes?▼

The filename format used for automating justification notes is {three-word-id}-{slug}.md. This structure ensures every file has a unique identifier, preventing naming conflicts and maintaining consistent documentation practices.