gk-init

Generate ARCHITECTURE.md, CODEBASE.md, and SPEC.md from existing codebases.

1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/gkganesh12/gk-stack --skill gk-init
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gk-init
Source: https://github.com/gkganesh12/gk-stack/tree/main/skills-library/gk-init
Command: npx skills add https://github.com/gkganesh12/gk-stack --skill gk-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the friction of adopting the GK-Stack in existing or legacy projects by automatically reverse-engineering the codebase to generate the necessary documentation and scaffolding.

Core Features & Use Cases

  • Automated Scaffolding: Generates the required gk/ directory, including ARCHITECTURE.md, CODEBASE.md, and SPEC.md, based on actual code analysis.
  • Contextual Documentation: Infers project structure, tech stack, and naming conventions by scanning source files, ensuring the generated docs are grounded in reality.
  • Use Case: You have a large, undocumented legacy project and want to start using AI-assisted development tools; run this skill to instantly create the foundational documentation needed to unblock all other GK-Stack skills.

Quick Start

Run the gk-init skill to onboard this project and generate the necessary documentation folder.

Frequently Asked Questions about gk-init

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

FAQPage Schema
How do I generate documentation for an undocumented legacy codebase?▼

To generate documentation for an undocumented legacy codebase, you can use automated reverse-engineering to scan source files and create foundational docs like ARCHITECTURE.md, CODEBASE.md, and SPEC.md based on actual code patterns.

What is the best way to onboard a legacy project into a new development stack?▼

The best way to onboard a legacy project into a new development stack is by reverse-engineering the existing codebase scaffold, analyzing directory structures to generate aligned documentation and required integration folders.

How do I scaffold a new framework directory structure from existing source files?▼

Scaffold a new framework directory structure from existing source files by scanning the codebase to infer the project structure, tech stack, and naming conventions, generating a grounded directory with required documentation.

Can I use automated scaffolding tools for large legacy codebases requiring AI-assisted development?▼

Yes, you can use automated scaffolding tools for large legacy codebases requiring AI-assisted development to instantly create the foundational documentation needed to unblock feature tracking and development workflows.

Does reverse-engineering codebase scaffolding work without existing project documentation?▼

Reverse-engineering codebase scaffolding works without existing project documentation by analyzing actual source files and directory structures to infer the tech stack and generate grounded architecture and specification files.

Why do I need to generate ARCHITECTURE.md and SPEC.md files for my existing codebase?▼

You need to generate ARCHITECTURE.md and SPEC.md files for your existing codebase to satisfy the requirement for grounded documentation, establishing the foundational context required to unblock AI-assisted feature development and bug tracking.