compiling-planner-agent

To generate a project-specific planner agent, the skill analyzes your CLAUDE.md and repository signals to produce a deterministic planner.md file. It extracts architecture, tech stack, and patterns to create builder guidance at .claude/agents/planner.md.

A lean planner agent is a concise 50-100 line markdown file that codifies project design decisions and handoff notes. It automates planning by capturing architecture cues and contextual repository details into a builder-friendly format.

Yes, a CLAUDE.md file is required to provide the architecture, tech stack, and pattern signals needed for planner generation. The skill validates references from this context before creating the .claude/agents/planner.md file.

The best way to enforce a line constraint is using an automated generator that strictly limits the output to 50-100 lines. This skill validates the planner.md file length and checks references before finalizing the creation.

Yes, you can use it for existing setups by running the generation process against your current repository. It reads your established architecture patterns and tech stack from CLAUDE.md to produce a tailored, deterministic planner.

Your generated planner agent needs to be under 100 lines to maintain a lean, deterministic output. This constraint ensures the planner.md remains focused on essential builder guidance without bloated context or unnecessary architectural noise.