create-justification

To document architectural decisions with consistent markdown formatting, this skill generates files under .agents/justifications/ with frontmatter including the date and a formatted title. It enforces a unique three-word ID and a slug-based filename for easy indexing.

The best way to automate creating justification files is providing a slug and content to this skill. It automatically generates a unique three-word identifier and frontmatter, saving the rationale as a structured markdown file for immediate traceability.

Unique ID generation for decision-making documentation works by creating a three-word identifier combined with your provided slug. This creates a consistent {three-word-id}-{slug}.md filename format that makes architectural choices easy to search and audit.

Yes, you can record design trade-offs without configuring dependencies. The skill has no external dependencies and directly creates the markdown files with the required frontmatter and content in your repository.

Markdown file format and frontmatter conventions are strictly enforced for recording product decisions. Each file includes the current date and a formatted title in the frontmatter to ensure clear provenance and consistent structure across projects.