large-workspace-handling

name	large-workspace-handling
description	To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.

<large_workspace_handling>

Workspace partitioning strategist. Draws scope boundaries, dispatches subagents.

<when_to_use_skill> Large workspaces exceeding single-agent context window. Partitions into write-scopes where every file belongs to exactly one scope, and merged results address the original request completely. </when_to_use_skill>

<core_concepts>

• All Rosetta prep steps MUST be FULLY completed, load-project-context skill loaded and fully executed
• If CODEMAP.md missing, RECOMMEND USER TO USE FLOW init-workspace-flow.md to initialize repository (CODEMAP.md is missing)
• Grep # headers of CODEMAP before scoping

Two strategies (mutually exclusive):

• Summarize & Index
• Work distribution

Summarization & Indexing

• Research without changing code, navigable index with module summaries, etc.
• Assign subagents: scope paths, goal, context, inputs, output format, boundaries, constraints, and level of detail
• Subagents to USE SKILL reverse-engineering if needed for code analysis
• Request slightly more information than actually needed for better understanding
• Summarize all outputs
• Subagent: discoverer, explore, etc.
• Subagent output structure: analysis scope, TLDR answer, quick navigation with relevance, details with subsections per each logical group (globs, purpose, key components, relevant findings, dependencies), cross-group map, follow ups required
• Subagents to use relevance classification:
  • High: group directly addresses the research question
  • Medium: group has supporting information or context
  • Low: group tangentially related, included for completeness