writing-plans

To create an implementation plan with exact file paths and verification steps, define clear project requirements and use the planning skill to generate deterministic epics, subtasks, and code samples. This ensures milestones are concrete and traceable for development handoffs.

Immutable planning in software task management is the process of generating fully specified, unchangeable task plans that include exact file paths, complete code snippets, and verification commands. This approach reduces miscommunication by ensuring end-to-end traceability before implementation begins.

Break down software epics into deterministic subtasks by providing concrete feature requirements to the planning skill. It generates an end-to-end task plan with explicit dependencies, acceptance criteria, and code samples for each subtask.

Yes, you need clear project requirements to generate a task plan with code samples. The planning skill targets projects with well-defined scopes to produce deterministic plans featuring exact file paths, complete code snippets, and specific verification commands.

The best way to ensure traceability during software feature handoffs is to use an immutable planning approach that generates fully specified subtasks with exact file paths, complete code samples, and verification steps. This makes milestones concrete and reduces miscommunication.

Yes, you can verify codebase assumptions before generating an implementation plan. The planning skill uses codebase investigation to verify assumptions and then presents a complete, ready-to-execute plan with exact file paths and verification commands.