plan-feature

This skill generates structured requirements, design, and task lists for a software feature by processing your feature name and optional input files, producing comprehensive planning documents ready for stakeholder approval.

Detecting ambiguities in feature specifications is handled automatically through built-in quality assurance checkpoints that scan planning documents for incomplete definitions, reducing miscommunication and rework before stakeholder confirmation.

Yes, you can use generated feature planning documents to ensure alignment with project standards by building detailed designs and requirements that incorporate review checkpoints for accurate, complete documentation.

Stakeholder approval is required before finalizing software feature design and task lists, as the planning workflow incorporates review checkpoints to confirm scope definition and reduce miscommunication before implementation begins.

Feature planning workflows suffer from miscommunication and rework due to ambiguous specifications and a lack of structured review checkpoints, which automatic formatting detection and comprehensive requirement generation aim to resolve.

You need detailed planning documents for software development workflows when defining the scope of a new feature, requiring structured requirements and stakeholder confirmation to ensure accurate documentation before implementation.