plan-feature

To turn a product brief into an executable implementation plan, the skill analyzes your project structure and requirements to generate codebase-aware, phased execution steps with specific file references and success criteria for coding agents.

AI agents generate broken code and scope creep by building features from memory rather than codebase reconnaissance. This skill prevents architectural debt by enforcing strict UI audits, product-owner logic, and codebase-grounded planning before coding begins.

You generate phased engineering tasks by providing a brief or a brief file path. The skill breaks complex features into small, verifiable, agent-executable phases that ensure technical feasibility, risk mitigation, and clear handoff documentation.

Yes, architectural alignment requires existing project conventions. The skill automatically performs codebase reconnaissance during the planning phase to ensure the generated implementation plans are technically feasible and follow your current project structure.

The best way to scope complex engineering tasks for coding agents is to apply rigorous requirement coverage and phase-based handoff. This forces a clear definition of user achievement and prevents feature bloat through strict UI audits.

Yes, you can use this planning workflow without a predefined file by providing a direct brief text input. The skill processes the provided brief to perform codebase reconnaissance and generate the detailed implementation plan.