ln-112-project-core-creator

Create requirements, architecture, and tech stack documentation files for any project.

534|73|Updated Oct 24, 2025

Search Tags:#architecture #documentation #requirements #arc42 #C4

Ready to run

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-112-project-core-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ln-112-project-core-creator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-112-project-core-creator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-112-project-core-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill always creates three core project documents:

docs/project/requirements.md
docs/project/architecture.md
docs/project/tech_stack.md to anchor project understanding and governance.

Core Features & Use Cases

Auto-create FRs, architecture sections, and tech stack references
Self-validation against 16 core questions
Deep auto-discovery using project context data and legacy content
Migration path support from legacy content if provided

Quick Start

Run ln-112-project-core-creator to generate the three core docs for any project.

Frequently Asked Questions about ln-112-project-core-creator

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

FAQPage Schema

How do I create core project documentation automatically?▼

Create core project documentation by running ln-112-project-core-creator, which generates three essential files: requirements.md, architecture.md, and tech_stack.md. The Skill auto-discovers project context, applies templates, and produces documentation anchored to your actual project structure.

What should project requirements and architecture documentation include?▼

Project requirements documents capture functional requirements; architecture documents detail system design, C4 diagrams, and design decisions; tech stack files list dependencies and technologies. This Skill generates all three following arc42 and C4 standards for consistency across projects.

Can I migrate legacy project documentation into the new format?▼

Yes. The Skill supports LEGACY_CONTENT merges, consuming your existing documentation from the Context Store and migrating content into the three core documents while replacing placeholders and maintaining idempotency.

How does the Skill validate generated documentation?▼

Generated documentation self-validates against 16 core questions covering functional requirements, technical architecture, and tech stack completeness. Validation ensures docs satisfy both technical and governance standards before output.

Does this work across all project types?▼

Yes. The Skill applies across all project types by consuming the full Context Store from the coordinator, performing auto-discovery, and using template-driven generation to produce consistent core documentation regardless of your tech stack or domain.

What happens if I run the Skill multiple times?▼

The Skill is idempotent—running it multiple times produces the same output without duplication or conflicts. It safely regenerates docs/project/requirements.md, docs/project/architecture.md, and docs/project/tech_stack.md on each execution.