writing-plans

To plan multi-step software implementations, you provide an approved design or requirements to generate a complete roadmap. This process produces structured task breakdowns, touched files lists, tests, and commit steps to reduce engineering rework and miscommunication before touching code.

Multi-perspective design review in software planning surfaces gaps across product, security, maintainability, UX, and architecture perspectives. It iteratively evaluates the implementation plan to ensure critical issues are resolved or escalated before any code is written.

Breaking down a design document into executable engineering tasks involves generating detailed implementation plans that specify touched files, tests, and documentation. It aligns task lists with the discovery log to preserve conversation history and ensure traceability throughout execution.

Yes, you can integrate TDD workflow steps into your implementation plan. The planning process generates structured task lists that include tests and commit records, ensuring test-driven development artifacts are produced and kept aligned with the design documentation.

Yes, this planning approach works for complex tasks requiring architecture and security reviews. It applies to engineering tasks that need thorough planning and structured breakdown across multiple perspectives, using an auto-fix loop to resolve critical issues before implementation begins.

A discovery log preserves conversation history and decisions for traceability during implementation planning. It ensures that generated artifacts like design documents, implementation plans, and commit records remain aligned with the original requirements and ongoing project decisions.