plan-feature

To generate a feature implementation plan, deep codebase analysis is performed to identify project patterns and dependencies, followed by external documentation research to structure a step-by-step execution guide with validation commands.

The best way to plan software development tasks is transforming feature requests into strategic plans by assessing risks, gathering best practices, and generating step-by-step tasks with necessary code snippets for execution agents.

Yes, automated planning handles complex codebases by thoroughly analyzing project structures, testing strategies, and dependencies, then researching external documentation to ensure comprehensive feature implementation and one-pass execution success.

User stories and validation commands are included in task generation by structuring the implementation plan around context references, ensuring clarity on execution phases and providing specific validation commands for the resulting software.

Before feature implementation, you need to research relevant external documentation and best practices, analyze existing codebase patterns, and assess design risks to formulate a detailed pre-implementation strategy.

Yes, generating a feature plan addresses software development risks by assessing potential issues during the strategic planning phase, ensuring design decisions are validated and implementation steps are clearly structured before coding begins.