qsd-map-codebase

Name: qsd-map-codebase
Availability: InStock
Author: thecomputer07

Generate seven structured codebase documents under .planning/codebase/ using four parallel mapper agents.

Updated Apr 13, 2026

Search Tags:#planning #documentation #onboarding #codebase #agents #parallel #mapping

Ready to run

npx skills add https://github.com/thecomputer07/qsd --skill qsd-map-codebase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qsd-map-codebase
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-map-codebase
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-map-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases can be large and opaque; this Skill automates creating a reproducible, structured map of an existing codebase by running parallel mapper agents that write documents directly to .planning/codebase/.

Core Features & Use Cases

Spawns four parallel qsd-codebase-mapper agents to generate seven structured documents (e.g., STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, CONCERNS.md) under .planning/codebase/.
Supports brownfield onboarding, regular updates as code evolves, and onboarding to unfamiliar projects.
Outputs a commit-ready codebase map and provides a clear next-step path.

Quick Start

Run the map-codebase workflow to generate the seven codebase documents under .planning/codebase/.

Frequently Asked Questions about qsd-map-codebase

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

FAQPage Schema

How do I generate structured documentation for an unfamiliar codebase?▼

Mapping an unfamiliar codebase is done by running parallel mapper agents that analyze the repository and write seven structured documents, including STACK.md and ARCHITECTURE.md, directly to .planning/codebase/.

What is the best way to create a codebase map for brownfield onboarding?▼

Creating a codebase map for brownfield onboarding involves spawning four parallel mapper agents that generate seven structured documents covering architecture, conventions, and testing, resulting in a commit-ready map under .planning/codebase/.

Can I use parallel agents to document my existing project structure automatically?▼

Yes, you can use parallel agents to document an existing project structure automatically. The mapping pipeline enforces a four-agent parallel process that writes seven structured documents and verifies their presence before completing a commit-ready map.

What documents are generated when mapping a codebase?▼

Mapping a codebase generates seven structured documents: STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, and CONCERNS.md, all written directly to the .planning/codebase/ directory.

How do I audit and update codebase documentation after significant changes?▼

Auditing and updating codebase documentation after significant changes is handled by rerunning the map-codebase workflow, which overwrites the seven existing structured documents in .planning/codebase/ with fresh analysis from the parallel mapper agents.