plan-agent

To generate an implementation plan from conversation context, this Skill reads your project's key files and codebase map, then outputs a concrete set of tasks and dependencies to a structured markdown file in your repository.

A development handoff transfers planning context to engineering teams. This Skill automatically creates handoffs by generating a markdown file with implementation rationale and references in a repository-conventional location.

Yes, you can create implementation tasks for an existing codebase. The Skill detects brownfield environments by checking for a codebase map and reading key files to tailor the generated plan to your current project structure.

To document project dependencies and task rationale, the Skill processes your conversational context and outputs a structured markdown plan that explicitly lists task dependencies alongside the reasoning for each implementation step.

Implementation plans should be stored in the thoughts/shared/plans/ directory, while handoff documents are output to the thoughts/handoffs/<session>/ directory, ensuring your repository follows consistent documentation conventions.

You do not need a codebase map to generate a project handoff, but having one allows the Skill to detect existing brownfield context and read key files to produce a more accurate and tailored implementation plan.