export-project

Synthesize a single-document project summary from canonical repo files.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill export-project-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: export-project
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/export-project
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill export-project-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synthesize a portable, single-document summary of the entire project from existing repo sources.

Core Features & Use Cases

  • Pull identity, tech stack, architecture, data model, current phase, recent work, in-flight tasks, and available skills from canonical repo files.
  • Produce a polished, standalone Markdown export suitable for sharing with contributors, stakeholders, or external readers.
  • Cite source files to preserve traceability and prevent misinterpretation.

Quick Start

Trigger the export with '/export-project' to generate the document at docs/exports/<YYYY-MM-DD>-claude-kit.md.

Frequently Asked Questions about export-project

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

FAQPage Schema
How do I generate a project summary export from markdown documentation?

To generate a project summary export, trigger the export-project command to synthesize existing markdown documentation into a single portable file saved at docs/exports/<YYYY-MM-DD>-claude-kit.md.

Does the project export process modify my original source files?

No, the project export process strictly reads from canonical source files like README.md and CLAUDE.md without modifying them, ensuring your original repository architecture and documentation remain untouched.

What files are pulled when creating a portable project architecture summary?

Creating a portable project architecture summary pulls content in strict order from README.md, CLAUDE.md, PHASES.md, ROADMAP.md, AUDIT.md, foundation.json, recent commits, and .claude/skills/*/SKILL.md.

Can I include tech stack and recent commits in a standalone markdown documentation export?

Yes, you can include tech stack and recent commits because the export synthesizes identity, architecture, data model, current phase, recent work, in-flight tasks, and available skills into one standalone markdown document.

How does the exported markdown document maintain traceability to the original repo sources?

The exported markdown document maintains traceability by including fixed structure citations that reference the canonical source files, preventing misinterpretation when sharing with contributors or external stakeholders.

What is the best way to share project documentation with stakeholders without giving full repo access?

The best way to share project documentation without full repo access is generating a polished standalone markdown export that synthesizes architecture, phases, and audits into a single portable file.