gds-dev-story

Invoke the skill with a phrase like "implement the next story in the sprint plan". It reads sprint-status.yaml, finds the first story marked ready-for-dev, loads its spec, and executes all tasks with tests until completion.

Each task follows a red-green-refactor cycle: write failing tests first, implement minimal code to pass them, then refactor while keeping tests green. The workflow halts if tests fail or regressions appear.

Yes. Provide the explicit story file path, for example by saying "dev this story" with the path. The workflow uses that file directly and skips sprint-based discovery.

The workflow detects a Senior Developer Review section in the story file, counts unchecked review follow-up tasks, and prioritizes resolving those items before continuing with remaining regular tasks.

It halts when tasks are ambiguous, required configuration is missing, new dependencies need approval, three consecutive implementation failures occur, or validation gates fail. Otherwise it runs continuously until all tasks are complete.

Only the YAML frontmatter baseline_commit, task checkboxes, Dev Agent Record, File List, Change Log, and Status sections. All other story content remains untouched to preserve the original specification.