gds-dev-story

Automating development story execution involves orchestrating discovery, context loading, task execution, and DoD validation. This Skill coordinates the full workflow, enforcing red-green-refactor cycles, tests, and artifact updates like File List and Change Logs for consistency.

Sprint management integrates by loading the next ready story from a sprint-status.yaml file, while also supporting direct standalone story files. This dual approach allows teams to execute tasks in order and satisfy DoD criteria regardless of the project management format.

Yes, dev-workflow automation enforces the red-green-refactor cycle, runs tests, and updates documentation artifacts. It validates Definition of Done criteria while integrating with project context and Dev Notes to ensure comprehensive traceability and quality control.

The best way to manage context loading is through automated orchestration that extracts project context and Dev Notes during story activation. This ensures tasks execute with comprehensive guidance, maintaining status management and validating DoD requirements end-to-end.

No, a sprint-status.yaml file is not strictly required. While the workflow supports sprint-based discovery via this file, you can also specify direct story files to activate and execute tasks, making it flexible for standalone development stories.