context-init

Generate SPEC, API, CONTEXT, RULES, and CHANGELOG documentation from design intent.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DeathKnightH/context-skills --skill context-init-deathknighth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-init
Source: https://github.com/DeathKnightH/context-skills/tree/main/skills/context-init
Command: npx skills add https://github.com/DeathKnightH/context-skills --skill context-init-deathknighth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns informal design intent into a complete five-piece documentation set (SPEC / API / CONTEXT / RULES / CHANGELOG) and optionally scaffolds minimal source directories and starter files, eliminating manual doc drafting and inconsistent project onboarding.

Core Features & Use Cases

  • Template-driven doc generation: Populate root- or module-level SPEC, API, CONTEXT, RULES, and CHANGELOG from configurable templates.
  • Controlled scaffolding: Optionally create declared directories and minimal starter files only when explicitly requested by the user, with dry-run previews and overwrite safety checks.
  • Scope and cascade management: Determine and persist documentation scope (single, cascade-down, full-cascade) into AGENTS.md and update parent module CONTEXT/CHANGELOG when appropriate.
  • Use Case: Prepare a new microservice repository by providing architecture, tech stack, and module boundaries, then generate consistent docs and a minimal src layout for the team.

Quick Start

Use context-init to generate the five-piece document set for a new project by providing the project name, one-line description, tech stack, target directory, and whether to include directories or starter files.

Frequently Asked Questions about context-init

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

FAQPage Schema
How do I generate standardized project documentation from a design intent?

To generate standardized project documentation, provide your architecture, technology stack, and module boundaries to produce a complete five-piece document set including SPEC, API, CONTEXT, RULES, and CHANGELOG files.

Can I scaffold source directories and starter files when initializing new project docs?

Yes, you can scaffold minimal source directories and starter files during documentation initialization, but only when explicitly requested, with dry-run previews and overwrite safety checks to protect existing data.

What is the best way to maintain consistent module onboarding documentation across a microservice architecture?

The best way to maintain consistent module onboarding documentation is to apply template-driven document generation with scope management, persisting documentation scope into AGENTS.md and updating parent module CONTEXT and CHANGELOG files.

Does the documentation generation process overwrite existing files in the target directory?

No, the documentation generation process includes overwrite safety checks and dry-run previews, ensuring that existing files in your target directory are protected before any new documents or starter files are written.

How do I initialize a changelog and API docs for a new codebase module?

You initialize a changelog and API docs by providing your project name, one-line description, and tech stack, which populates standardized templates for immediate API documentation and historical change tracking.

When should I not use automated template scaffolding for project initialization?

You should avoid automated template scaffolding when your project requires custom directory structures outside standard templates, or when you need to manually control file creation without relying on dry-run previews and overwrite safety checks.