writing-plans

Breaking down complex software development tasks involves generating actionable implementation plans with explicit file paths, dependencies, and verification commands. This process creates small, self-contained subtasks suitable for multi-session execution and structured development workflows.

Managing dependencies in multi-session feature development requires explicitly defining task order and prerequisites within the implementation plan. This ensures each subtask executes sequentially, verifying completion through integrated commands before proceeding to dependent steps.

Verifying codebase changes during task decomposition involves ensuring each task includes a specific verification command. The planning process checks the codebase before defining definitive steps, guaranteeing that every actionable unit has a clear, executable validation method.

Generating implementation plans with explicit file paths for new authentication systems is fully supported. The plan creates sequentially linked tasks for database schemas, API endpoints, frontend forms, and tests, ensuring all components are correctly ordered and verifiable.

Avoiding conditional logic in task descriptions for workflow automation prevents ambiguous execution paths and ensures definitive steps. The planning mechanism strictly prohibits branching conditions, guaranteeing each subtask remains self-contained, trackable, and executable across multiple sessions.

Codebase verification before defining implementation steps is a core requirement of the writing-plans process. It ensures the generated plan is grounded in the actual state of the codebase, preventing inaccurate or unexecutable task definitions.