feature-plan

To plan a software feature end-to-end, this skill orchestrates all child user stories sequentially via /userstory-plan and updates the feature status from Pendente to Planejado after validating the aggregate acceptance criteria. It coordinates the entire workflow automatically.

Feature orchestration is the process of coordinating end-to-end planning of a software feature by sequentially delegating each child user story to /userstory-plan. It validates planning contracts using either the feature's successCriteria or aggregated acceptance criteria from child stories.

You move a feature from Pendente to Planejado by sequentially invoking /userstory-plan for each eligible pending user story. Once all child stories are planned and the contract is validated, the feature status is persisted as Planejado with changelog entries for any accepted gaps.

Yes, you can plan a feature with already planned user stories. This skill applies to features with both pending and planned user stories, orchestrating only the eligible pending ones while validating the overall contract through the feature's successCriteria or aggregated acceptance criteria.

Yes, feature planning validates the contract using either the feature's own successCriteria or the aggregate acceptance criteria of its child user stories. It reports any gaps or blockers discovered during validation for user review before moving to Planejado.

When gaps or blockers are found during user story planning, the skill records a changelog entry for any accepted gaps and reports them for user review. This ensures transparency before the feature status is updated to Planejado.