ac-plan

To generate an implementation plan, provide task details and constraints as input arguments. The skill reads context, uses subagents for focused research, and compiles a deterministic plan outline persisted to .claude/plan/*.md for review.

Cross-team planning for multi-module projects is handled by using subagents for read-only analysis and compiling the findings into structured plan files. This ensures clear handoffs and traceability without modifying product code.

Yes, subagents enforce read-only analysis during the planning process. They gather focused research while the main thread compiles the final plan, ensuring your product code remains completely unmodified.

Actionable implementation plans are saved by writing them directly to the .claude/plan directory as markdown files. This persistence enables structured review, iterative updates, and clear handoffs across teams.

No external dependencies or components are required to run this planning workflow. It operates independently to turn ambiguous requirements into executable plan outlines using internal subagent research.

You should avoid using an automated implementation plan generator for tasks requiring direct code modification or single-module updates. It is specifically designed for multi-module project coordination and read-only contextual research.