document-project

Generate a brownfield baseline and architecture map for an existing codebase.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/GDSDN/kord-aios --skill document-project-gdsdn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-project
Source: https://github.com/GDSDN/kord-aios/tree/main/src/features/builtin-skills/kord-aios/documentation/document-project
Command: npx skills add https://github.com/GDSDN/kord-aios --skill document-project-gdsdn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a reality-based baseline and architecture map for existing codebases, providing essential context for safe modifications and onboarding.

Core Features & Use Cases

  • Brownfield Baseline: Captures the current state of a codebase, including build/test commands, actual conventions, and integration points.
  • Architecture Mapping: Identifies entry points, core flows, and technical debt.
  • Risk Assessment: Documents constraints, workarounds, and rollback options.
  • Use Case: Before making significant changes to a legacy system, use this Skill to generate documentation that details the current architecture and potential risks, ensuring developers understand the existing system's intricacies.

Quick Start

Use the document-project skill to create a brownfield baseline for the current codebase.

Frequently Asked Questions about document-project

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

FAQPage Schema
How do I map an existing codebase architecture before making changes?

To map an existing codebase architecture, you can generate a brownfield baseline that captures build commands, identifies entry points, and documents core flows to provide context for safe modifications.

What is a brownfield baseline and when do I need it for a legacy codebase?

A brownfield baseline captures the current state of a legacy codebase, including actual conventions and integration points, needed before making significant modifications to ensure developers understand existing intricacies.

How do I document technical debt and workarounds in a codebase?

Documenting technical debt and workarounds involves assessing risks and constraints within the codebase, then outputting artifacts that detail these limitations alongside the identified architecture map.

Can I identify entry points and core flows for a codebase without prior documentation?

Yes, architecture mapping identifies entry points and core flows for an undocumented codebase by analyzing the current state and generating baseline artifacts to establish missing context.

What is the best way to generate onboarding documentation for a complex codebase?

Generating onboarding documentation is best achieved by creating a reality-based baseline and architecture map that captures actual build commands, integration points, and technical debt.

Where are the generated architecture map and baseline artifacts outputted?

The generated architecture map and brownfield baseline artifacts are outputted to the `docs/kord/drafts/` and `docs/kord/notepads/` directories in your codebase.