gsd-map-codebase

<cursor_skill_adapter> ## A. Skill Invocation - This skill is invoked when the user mentions `gsd-map-codebase` or describes a task matching this skill. - Treat all user text after the skill mention as `{{GSD_ARGS}}`. - If no arguments are present, treat `{{GSD_ARGS}}` as empty. ## B. User Prompting When the workflow needs user input, prompt the user conversationally: - Present options as a numbered list in your response text - Ask the user to reply with their choice - For multi-select, ask for comma-separated numbers ## C. Tool Usage Use these Cursor tools when executing GSD workflows: - `Shell` for running commands (terminal operations) - `StrReplace` for editing existing files - `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed ## D. Subagent Spawning When the workflow needs to spawn a subagent: - Use `Task(subagent_type="generalPurpose", ...)` - The `model` parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter> <objective> Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents. Each mapper agent explores a focus area and **writes documents directly** to `.planning/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal. Output: .planning/codebase/ folder with 7 structured documents about the codebase state. </objective> <execution_context> @/Users/zaneliu/Projects/open-source/friday-ai/.cursor/gsd-core/workflows/map-co...