writing-plans

To turn a software specification into an actionable implementation plan, you orient on the target codebase area, define clear file boundaries, and outline concrete tasks with acceptance criteria and verification steps. This ensures every step contains actionable content without placeholders.

Writing implementation plans for async cross-team handoffs requires a full plan depth that enforces structure and traceable tasks. You map tasks to concrete code changes using repo tooling, establishing clear scope and boundaries to prevent ambiguity.

You map implementation tasks to concrete code changes by using codebase orientation tools like get_context, deep_dive, get_symbols, and fast_refs. This allows you to inspect files to be created or modified and assign clear responsibilities to each task.

Writing implementation plans works for both same-session development and async handoffs. You choose a light plan depth for same-session work or a full plan depth for async scenarios, scaling the detail level to match who is executing and when.

Implementation plans must avoid placeholders like TBD to ensure every step contains concrete content. Eliminating placeholders guarantees traceable tasks and clear scope, which is critical for accurate async or cross-team task execution.