ln-112-project-core-creator

Generate four standardized project documentation files from a Context Store.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-112-project-core-creator-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-112-project-core-creator
Source: https://github.com/0xtaoist/taogate/tree/main/ln-112-project-core-creator
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-112-project-core-creator-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The L3 Worker for project core documentation creates four essential project documents (requirements, architecture, tech_stack, and patterns_catalog) automatically, ensuring consistent documentation across projects and saving time during project initialization.

Core Features & Use Cases

  • Automates the generation of four core docs for any new project based on the provided Context Store.
  • Applies legacy content when available, while preserving auto-discovered data and adding ADR links and architecture diagrams.
  • Validates structure and ensures idempotent creation so existing documents are not overwritten.

Quick Start

Provide the complete Context Store to the ln-110/ln-112 coordination flow to generate the four core project documents.

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 auto-generate project documentation from existing architecture data?

Project documentation generation validates structure against provided questions and templates while ensuring idempotence. It does not overwrite existing documents, preserving current data while generating ADR references and C4 diagrams for architecture conformance.

How do I create ADR references and C4 diagrams for my project architecture?

Create ADR references and C4 diagrams automatically by processing your Context Store through the documentation generation flow. The system transforms input data into standardized architecture files tailored to your project's specific conformance requirements.

Can I use legacy project documentation content when generating new architecture files?

Legacy project documentation content is applied with priority over auto-discovered data during generation. This ensures your existing architecture definitions and requirements are preserved while standardizing the output across the four core documentation files.

What's the best way to standardize requirements and tech_stack documents across multiple projects?

Standardize requirements and tech_stack documents by using a coordinated generation flow that validates structure against provided templates. This approach ensures architecture conformance and consistent formatting across multiple projects without overwriting existing files.

Why does project documentation generation not overwrite my existing architecture files?

Project documentation generation ensures idempotence by validating structure and explicitly not overwriting existing architecture files. This prevents data loss when applying legacy content alongside auto-discovered data from your Context Store.